All directories
SkillOperationsProduct

Internal Comms

Templates and tone guidance for announcements, status updates, incident comms, and exec summaries so Slack/email writing matches org voice.

Open on GitHubBrowse more skills
01

Overview

Internal Comms is a Claude skill catalogued in LimeDock Directories for teams working across operations, product, other. It is tagged for saas, agency, other contexts. Templates and tone guidance for announcements, status updates, incident comms, and exec summaries so Slack/email writing matches org voice. Use this page as the operational brief: install path, how to invoke it, copy-paste prompts, prerequisites, and concrete use cases so your team can adopt it without re-reading every roundup article.

SaaSAgencyOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Skills show what's possible. LimeDock builds and runs the owned marketing, sales, and ops automations around them.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

Book a workflow call
02

Link

https://github.com/anthropics/skills/tree/main/skills/internal-comms
03

Installation guide

Claude Code / CLI

npx skills add https://github.com/anthropics/skills/tree/main/skills/internal-comms
# or copy into ~/.claude/skills/<skill-name>/

Plugin marketplace

/plugin marketplace add <org/repo>
/plugin install <skill>@<marketplace>

**Claude.ai** Customize → Skills → Upload `.zip` or `SKILL.md` → enable the skill.

Audit `SKILL.md` and any scripts before install.

04

How to use it

Describe the audience and message type (incident, launch, status); skill shapes concise, org-appropriate drafts.

**Suggested workflow** 1. Install and enable the skill. 2. Open the target project (or Claude.ai chat) with enough product context. 3. Invoke with a clear goal, constraints, and success criteria. 4. Review the first output against your standards; refine with follow-ups. 5. Save winning prompts / outputs into your team playbook.

If Claude does not auto-select it, mention the skill by name: “Use the Internal Comms skill…”

05

Example prompts

  • “Use the Internal Comms skill for this task: Incident status update for Slack”
  • “Walk me through how Internal Comms would approach this step by step, then execute.”
  • “Review my current draft/plan and improve it using Internal Comms. Call out assumptions.”
  • “Produce a checklist I can reuse whenever we run Internal Comms on similar work.”
06

Use cases and examples

  • Incident status update for Slack
  • Exec weekly summary
  • Launch announcement
  • Postmortem-friendly status note
  • First-week trial of Internal Comms on a real operations workflow
  • Document a reusable prompt template for Internal Comms for your team
07

Prerequisites

  • Claude Code, Claude.ai (Skills enabled), or an Agent Skills–compatible host
  • Network access if the skill fetches guidelines or calls external tools
  • Project or brand context (CLAUDE.md / product notes) for better outputs
  • Permission to install third-party skills — audit SKILL.md and scripts first
08

Tips

  • Keep descriptions/triggers tight so Internal Comms fires only when relevant (avoids context tax).
  • Prefer one sharp job over a mega-skill that tries to do everything.
  • Pair with verification (tests, review, screenshots) before shipping outputs.
  • Re-audit installed skills monthly — unused skills still cost context every turn.
09

Sources