anthropics/skills · skills/internal-comms/SKILL.md
internal-comms
“A tidy 26-line router for internal memos. The real templates live in example files this review can't see.”
What it does
Helps the agent write internal communications such as 3P updates, newsletters, FAQs and status reports. It picks the type, loads a matching guideline from examples/, and follows that file's format and tone.
- When the agent uses it
- When asked to write internal comms: status reports, leadership or project updates, 3P updates, newsletters, FAQs or incident reports.
- Who it is for
- Teams that want house-style internal memos and will edit the example files to fit. Skip it if you only need a one-off email; the agent can do that without help.
- What it costs
- 26 lines, about 408 tokens once the agent loads it.
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.).
What it tells the agent to do
- Identify the communication type from the request.
- Load the matching guideline file from examples/ (3p-updates, company-newsletter, faq-answers).
- Use examples/general-comms.md for anything that doesn't match the others.
- Follow that file's instructions for formatting, tone and content gathering.
- If no guideline fits, ask for clarification or more context about the format.
Lines worth reading
Straight from the file, with why each one matters.
line 3using the formats that my company likes to use
First person, in a shared skill. Whose company? Yours only once you rewrite the example files.
line 93P updates (Progress, Plans, Problems)
Explains the house jargon right where the agent needs it. Without this, '3P' means nothing.
line 26For anything else that doesn't explicitly match one of the above
A catch-all fallback, but line 29 says to ask for clarification when nothing matches. The two rules disagree.
line 31## Keywords
Keywords placed after loading. The agent only sees the description when deciding, so this list never helps it trigger.
Watch out for
Nothing risky that Kin could see in SKILL.md. Scripts beside it were not read.
The scorecard
- TriggerSays when to use it7/10
Lists real request words, but opens with vague 'a set of resources to help me'.
- FocusOne clear job7/10
One family of tasks, though it spans seven formats under one roof.
- LeanLight to load9/10
26 lines that route to detail files. This is how loading only what's needed should work.
- ConcreteSteps you can follow5/10
Clear routing steps, but every format rule is in unseen files. Several types have no file.
- SafeSafe to run9/10
Only reads local markdown. No commands, no network calls, no secrets.
What it does well
- Short SKILL.md that loads per-type guidance only when needed, which is the intended pattern.
- The description names concrete request types (3P updates, incident reports, newsletters) the agent can match on.
How it could be better
Rewrite the description and fold in the keywords
Only the description is seen before loading. Lead with what it does, in third person, and move the Keywords list into it.
Adddescription: Writes internal company communications in house formats: 3P updates (Progress, Plans, Problems), status reports, leadership updates, project updates, incident reports, company newsletters and FAQ answers. Use when asked to draft a weekly update, team update, newsletter, incident write-up or internal announcement.
Settle the fallback rule
Line 26 sends unmatched types to general-comms.md, but line 29 says to ask instead. The agent can't follow both.
AddIf the type matches none of the files above, use examples/general-comms.md. Ask the user for format details only if general-comms.md does not cover the request.
Map every listed type to a file
Status reports, leadership updates and incident reports are named as triggers but have no guideline file listed.
Add- `examples/<incident-reports>.md` - For incident reports and postmortems - `examples/<status-reports>.md` - For status, project and leadership updatesSay what done looks like
There is no check before handing the draft back, so format drift goes unnoticed.
Add4. Before replying, check the draft against the guideline's required sections and length, and list any facts you had to assume as <placeholders> for the user to fill.
Kin reviews against Anthropic’s Extend Claude with skills and agentskills.io’s the Agent Skills standard. It reads SKILL.md only, so a script beside it can still do things the file does not say.