Internal Communications
Write the company update — in the company’s voice.
Internal comms eat hours, and every team writes them slightly differently. This skill carries your company’s preferred format for each kind of message, so a status report comes out looking like your status reports — not a generic draft you then have to reshape by hand.
Anthropic3P updatesnewslettersFAQsincident reportsHow it works
Identify the comms type → Load the matching guideline → Follow its formatThe skill reads the request, picks the comms type, and loads the one guideline file that defines tone, structure, and what context to gather for that type.
The four guidelines
| File | For |
|---|---|
examples/3p-updates.md | Progress / Plans / Problems team updates |
examples/company-newsletter.md | Company-wide newsletters |
examples/faq-answers.md | Answering frequently-asked questions |
examples/general-comms.md | Anything that doesn’t match the above |
Worked example — “write a 3P update for my team”
The skill recognises the 3P type, loads 3p-updates.md, and structures the draft as Progress (what shipped), Plans (what’s next), Problems (what’s blocked) — gathering the specifics that guideline asks for before writing a word.
Under the hood
Make it your own house style
The guideline files are the configuration. Drop a new Markdown file into examples/ describing a format your company uses — a board update, a release note — and point the routing step at it. The skill follows whatever tone and structure you write there; nothing is hard-coded into the model.
Triggering
The skill is meant to fire on any internal-comms request, even when the user doesn’t name a format: 3P updates, company newsletter, company comms, weekly update, FAQs, common questions, status report, leadership update, incident report. When the type is genuinely unclear, it asks rather than guessing.