
Internal Comms
✓ Official★ 158,000by Anthropic · part of anthropics/skills
A set of resources to help me write all kinds of internal communications, using the formats that my 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
A set of resources to help me write all kinds of internal communications, using the formats that my 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
Inspect the full instructions your agent will receiveExpandCollapse
This is the exact playbook injected into your agent when the skill activates — shown here so you can audit it before installing. You don't need to read it to use the skill.
by Anthropic
A set of resources to help me write all kinds of internal communications, using the formats that my 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
npx skills add https://github.com/anthropics/skills --skill internal-comms
Download ZIPGitHub158k
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
Keywords
3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms
npx skills add https://github.com/anthropics/skills --skill Internal CommsRun this in your project — your agent picks the skill up automatically.
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.
No common issues documented yet. If you hit a problem, the repository's GitHub Issues page is the best place to look.