Skills

Skill 10 of 19

Internal Comms

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use.

1 minute · 131 words · 3 sections

Install

$ npx skills add anthropics/skills --skill internal-comms

$ npx skills add anthropics/skills

» /plugin marketplace add anthropics/skills

The first command installs just this skill, by the name in its SKILL.md; the second installs the whole repository.

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.

Keywords

3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms

About this skill

Trigger

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.).

The verbatim description from this skill’s front matter — the string an agent matches on to decide whether to load it.

Licence: Complete terms in LICENSE.txt
Source: skills/internal-comms/SKILL.md

Colophon for this issue

Colophon

How this issue was made

Source

github.com/anthropics/skills, branch main, last pushed 22 September 2026.

Licence

Discovery

19 skills found by walking the repository tree for SKILL.md, not by matching a directory convention. One layout observed: skills/*/SKILL.md.

Issue colours

Resolved from the awesome-design-md registry — hue 39°, chroma 0.113. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.

Typefaces

Display: Copernicus is not available to us; set in Newsreader.

We never load a typeface at request time from a third-party origin, so a brand face we do not already self-host is substituted rather than fetched.

Heading repairs

None needed in this skill: the outline was already valid.

Spec compliance

1 editorial note across 1 of 19 skills. They are printed in the margin of each skill rather than as errors here.

Claude API — 1 note

Images

Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.

Marketplace

A plugin manifest is published at .claude-plugin/marketplace.json by Keith Lazuka, declaring 5 plugins. It is read for editorial metadata only — never as the skill index, which is always the repository tree.

Signal

Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.

Agent surfaces

The whole issue is available as one markdown document at /anthropics/skills.md, and each skill at its own .md URL.

Publication

Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.

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.

Internal Comms

When to use this skill

How to use this skill

Keywords

About this skill

Trigger

Colophon

Internal Comms

When to use this skill

How to use this skill

Keywords

Appendix 10.1–10.5

Also bundled5 files

About this skill

Trigger

Colophon

Appendix 10.1–10.5

Also bundled5 files