Internal Comms

Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.

Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.

Routing

Identify the communication type from the user's request, then read the matching reference file before writing anything:

If the type is ambiguous, ask one clarifying question — don't guess.

Workflow

1. Read the reference file for the matched type. Follow its formatting exactly.
2. Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
3. Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
4. Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
5. Present the draft and ask if anything needs to be added, removed, or reworded.

Tone & Style (applies to all types)

• Use "we" — you are part of the company.
• Active voice, present tense for progress, future tense for plans.
• Concise. Every sentence should carry information. Cut filler.
• Include metrics and links wherever possible.
• Professional but approachable — not corporate-speak.
• Put the most important information first.

When tools are unavailable

If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.

Anti-Patterns

Related Skills