internal-comms is one of the example skills in Anthropic’s public skills repository. It triggers when Claude is asked to write internal communications such as status reports, leadership updates, 3P (Progress, Plans, Problems) updates, company newsletters, FAQs, incident reports and project updates. The SKILL.md has Claude identify which kind of communication is being asked for, load the matching guideline file from its examples folder, and follow that file’s instructions for format, tone and gathering content.
Four guideline files ship with it. The 3P update guide sets a strict four-line format readable in under a minute, the newsletter guide asks for roughly 20-25 linked bullets grouped into sections for a 1000+ person company, the FAQ guide pairs one-sentence questions with short answers drawn from official communications, and a general guide covers everything else by first asking about audience, purpose, tone and format. Each guide tells Claude to pull material from Slack, email, documents and calendar when those tools are available, and to ask the user for the content when they are not.
What You Get
- A SKILL.md that maps a request for internal writing to the right guideline file
- A 3P update format: an emoji, the team name and dates, then one to three data-driven sentences each for Progress, Plans and Problems
- A company newsletter template of about 20-25 short, linked bullets in sections such as Company Announcements, Progress on Priorities, Leadership Updates and Social Updates
- An FAQ format of one-sentence questions and one-to-two-sentence answers, with guidance to flag uncertainty and questions that need an executive response
- A fallback guide for any other communication that starts by clarifying audience, purpose, tone and formatting
Common Use Cases
- Writing a team’s weekly 3P update for leadership from a week of Slack posts, docs and meetings
- Assembling a company-wide newsletter for Slack and email that summarises the week’s announcements and milestones
- Turning the questions employees keep asking into a short FAQ with answers linked to official sources
- Drafting a one-off announcement, incident report or project update when none of the fixed formats fit
What Makes It Unique
Where frontend-design and pdf in the same repository are about producing interfaces and files, internal-comms is about writing to a company’s own conventions. It does not try to cover every kind of message in one long prompt: each format lives in its own short guideline file that Claude loads only for the type requested, so a 3P update stays a strict four lines and a newsletter stays a sectioned list of linked bullets. The guides also tell Claude where good source material tends to be, such as Slack posts with many reactions or meetings with large attendee lists, rather than only how to phrase the result. The SKILL.md lists seven communication types but ships four guides, so status reports, leadership updates, project updates and incident reports go through the general guide.
Under The Hood
The skill is prose only: a short SKILL.md and four Markdown guideline files in an examples folder, with no scripts; the folder also holds the license text. When it loads, Claude reads the SKILL.md, picks the guide that matches the request and follows it. The guides ask Claude to gather context from Slack, email, Google Drive documents and calendar events if the session has tools for them, but the skill itself runs no commands, calls no services and writes no files. Without those tools, Claude asks the user for what to cover and formats what it is given. The 3P guide also says to confirm the team name and time period before drafting, and the general guide says to ask about audience, purpose and tone first.