| name | internal-comms |
| description | A set of resources to help write all kinds of internal communications, using the formats that your company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.). |
| license | Complete terms in LICENSE.txt |
Model routing: Sonnet for implementation; Haiku for verification/scoring; Opus only for explicit architectural decisions.
When to use this skill
To write internal communications, use this skill for:
- 3P updates (Progress, Plans, Problems)
- Company newsletters
- FAQ responses
- Status reports
- Leadership updates
- Project updates
- Incident reports
How to use this skill
To write any internal communication:
- Identify the communication type from the request
- Load the appropriate guideline file from the
examples/ directory:
examples/3p-updates.md - For Progress/Plans/Problems team updates
examples/company-newsletter.md - For company-wide newsletters
examples/faq-answers.md - For answering frequently asked questions
examples/general-comms.md - For anything else that doesn't explicitly match one of the above
- Follow the specific instructions in that file for formatting, tone, and content gathering
If the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.
If the examples/ directory is missing or the type doesn't match, fall back to examples/general-comms.md or ask the user for their preferred format.