Source: anthropics/skills · Maintainer: Anthropic · License: Apache 2.0 · Checked: 24 October 2026
What is the internal comms skill?
The internal comms skill gives Claude a fixed format for each common kind of internal message, so a weekly team update, a company newsletter or an FAQ roundup comes out in the same shape every time. It is a small, instructions-only skill from Anthropic's anthropics/skills repo, useful for anyone who writes recurring updates for leadership or the whole company.
The description in its SKILL.md reads: "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 "my company" wording is a clue to how it is meant to be used: it shows the pattern of a company's house style written down as a skill. Anthropic's README says the repo's skills are "provided for demonstration and educational purposes only," so treat the formats as a starting point you adapt. Its skills.sh page listed 79.9K installs (snapshot, 24 October 2026).
What does the internal comms skill do?
The skill is model-invoked: Claude can load it on its own when you ask for a status report, a newsletter or a similar message. The SKILL.md tells Claude to do three things:
- Identify the communication type from the request.
- Load the matching guide from the
examples/folder. - Follow that guide's instructions for format, tone and gathering content.
If the request matches none of the guides, Claude is told to ask for clarification or more context about the format you want.
What is in the folder?
SKILL.md: the routing instructions and a keyword list (3P updates, company newsletter, weekly update, FAQs and similar).examples/3p-updates.md: Progress, Plans, Problems team updates.examples/company-newsletter.md: company-wide newsletters.examples/faq-answers.md: summaries of questions people across the company are asking.examples/general-comms.md: the fallback for anything else.LICENSE.txt: Apache License 2.0.
There are no scripts, so nothing runs on your machine.
What does each format look like?
3P updates. Written for executives and teammates with some context, readable in 30 to 60 seconds, and usually covering one week. The format is strict: a header line with an emoji, the team name and the dates, then Progress:, Plans: and Problems:, each one to three sentences, with metrics where possible. Claude is told to confirm the team name before writing.
Company newsletter. Around 20 to 25 bullets, each about one or two sentences, written in the "we" voice and meant for Slack and email. The guide suggests grouping bullets into sections and gives example headings such as company announcements, progress on priorities, leadership updates and social updates. It favors company-wide news and says to leave granular team news to 3Ps.
FAQ answers. Claude looks for the questions that confuse the most people and writes each as a one-sentence question and a one or two sentence answer. The guide says to base answers on official communications, flag uncertainty and flag questions that need an executive response.
General comms. Before writing, Claude asks about the audience, the purpose, the tone and any formatting rules, then writes with the most important information first.
Incident reports and project updates are named in the description but have no guide of their own, so they go through the general guide.
How do you install the internal comms skill?
Claude Code plugin. The repo README registers the repo as a plugin marketplace. In a Claude Code session:
/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills
The example-skills plugin bundles internal-comms with Anthropic's other example skills, including algorithmic-art, slack-gif-creator, frontend-design, mcp-builder and skill-creator. Plugin skills are namespaced as /plugin-name:skill-name, according to the Claude Code skills docs, so you can call it as /example-skills:internal-comms.
Just this skill. The command on skills.sh:
npx skills add https://github.com/anthropics/skills --skill internal-comms
It installs into the current project by default; add -g to make it available in all projects. For Claude Code, a personal copy lives at ~/.claude/skills/internal-comms/ and a project copy at .claude/skills/internal-comms/. Codex and Cursor read the same SKILL.md format; see Codex skills and Cursor skills.
Claude.ai. The README says the example skills are already available on paid Claude.ai plans. If you want your own edited copy instead, zip the folder and upload it under Customize > Skills, as described in Use skills in Claude. That article notes that skills need code execution turned on.
How do you use it?
Name the format, the team and the period, and either connect your sources or paste the raw notes. Claude only formats what it can see.
Example prompts (suggestions, not from the repo):
Write a 3P update for the Payments team for 13 to 17 October. Notes: shipped refunds API, p95 latency down 18%, hiring blocked on one backend role.Turn these bullet points from leadership into this month's company newsletter. Group them into sections.Go through the questions in #ask-hr from this week and write an FAQ with short answers. Flag anything that needs an exec to answer.Draft an internal note announcing the office move. Ask me about audience and tone first.
What do you need?
Nothing to install beyond the skill itself. The 3P, newsletter and FAQ guides tell Claude to gather context from Slack, Google Drive, email and calendar when it has access to them, so connectors make it more useful. Without them, the guides tell Claude to ask you what to cover, and the job becomes mostly formatting.
Tips and limits
- The formats are Anthropic's examples. The newsletter guide assumes a company of "1000+ people," and the newsletter headings use Slack emoji codes such as
:megaphone:. Edit the guides if your company is smaller or posts somewhere else. - 3Ps are deliberately rigid. The guide says never to use any other formatting. If you want headers or longer sections, change
3p-updates.mdrather than arguing with it in each prompt. - Check every number. The guides ask for data and metrics. Claude can only use figures that appear in your notes or connected sources, so review anything that will reach leadership.
- Audit note. On 24 October 2026, skills.sh showed Pass from Gen Agent Trust Hub and Socket and Warn from Snyk. Snyk's report, dated 15 September 2026, flags medium risk W011, "Third-party content exposure detected (indirect prompt injection risk)," because the guides have Claude read Slack posts, emails and Drive docs written by other people. That is inherent to summarizing a workplace, so review drafts built from channels you don't control.
- License. Apache 2.0: you can copy, modify and redistribute it if you keep the license and mark your changes.
Save it in your Kipt library
The best version of this skill is your own: the 3P, newsletter and FAQ formats your company actually uses. In Kipt, open Skills and paste the folder link https://github.com/anthropics/skills/tree/main/skills/internal-comms into the import box, then edit the guides in your library. Kipt keeps skills as Markdown in a private GitHub repo you own and installs them all into Claude Code or Codex with one command:
npx skills add https://github.com/<you>/<repo>.git --all -g
Kipt is not affiliated with Anthropic.
Similar skills
- docx skill: when the update needs to ship as a Word document rather than a Slack post.
- pptx skill: turn the same quarterly update into slides.
- Skill creator: build your own company comms skill from scratch.
- Claude skills examples: more instruction-only skills you can adapt.