Preface¶

Writing 3P weekly reports, compiling company-wide Newsletters, replying to FAQs, drafting incident notifications—these internal communication documents vary in format and audience, yet all require clear messaging within a limited word count. It’s not hard to draft one from scratch, but the challenge lies in recalling every time: What template does our team use? What tone should I adopt? How long should it be?

Anthropic has released a Skill called internal-comms in their official Skills repository: it packages the writing specifications for various internal communication documents into a reusable instruction set, allowing AI agents to generate content in Cursor, Claude Code, and other tools following predefined formats. This represents a typical direction for Agent Skills expanding from “writing code, designing artifacts” to “workplace collaboration and productivity.”

What is this¶

internal-comms is an enterprise communication sample Skill in the anthropics/skills repository, maintained by Anthropic and following the universal SKILL.md open format (see agentskills.io for details).

Its positioning is straightforward: when you need to write various internal communication materials, the agent will first identify the document type, then load the corresponding format guide from the examples/ directory, and generate a draft in line with the company’s preferred structure, tone, and length requirements.

The officially supported document types explicitly listed in SKILL.md include:
- 3P updates (Progress / Plans / Problems)
- Company Newsletter (all-staff communication)
- FAQ replies
- Status reports
- Leadership updates
- Project updates
- Incident reports

For types without separate template files (such as status reports, incident reports, etc.), the Skill will fall back to the general principles in examples/general-comms.md, and proactively confirm the audience, purpose, and tone with you when information is insufficient.

Core Features and Highlights¶

1. Load format guides by category, instead of “one-size-fits-all”¶

The core workflow of the Skill is written in SKILL.md, divided into three steps:
1. Identify the communication type from the user’s request;
2. Load the corresponding guide file from the examples/ directory;
3. Complete the writing in accordance with the format, tone, and information collection requirements in that file.

The responsibilities of each guide file are as follows:

This design of “lightweight main Skill, on-demand loading of reference materials” aligns with the progressive context loading advocated by Agent Skills: the agent only reads the corresponding template when writing a specific type of document, avoiding stuffing all specifications into the context at once.

2. Built-in writing specifications for multiple enterprise communication scenarios¶

Take 3P updates as an example, the official guide requires:
- Audience is management and cross-team colleagues, readable in 30–60 seconds;
- Fixed three-part structure: Progress (completed this week), Plans (next week’s plans), Problems (obstacles and risks);
- 1–3 sentences per section, data-driven, with a plain tone and no flowery language;
- Strict output format, for example:

[pick an emoji] [Team Name] (Dates Covered)
Progress: [1-3 sentences]
Plans: [1-3 sentences]
Problems: [1-3 sentences]

The Company Newsletter guide focuses on: about 20–25 bullet points, using the “we” perspective, organizing by product/marketing/hiring and other categories, attaching links to Slack messages, Google Drive documents, emails, etc. as much as possible, and prioritizing company-level impact over team trivial details.

The FAQ guide requires presenting content in “Question + Short Answer” pairs, answering based on official communication materials, clearly marking when uncertain, and linking to authoritative sources when necessary.

3. Guide agents to pull context from collaboration tools¶

Multiple guide files mention that if the agent has access to tools such as Slack, Google Drive, Email, Calendar, etc., it should prioritize collecting this week’s progress, announcements, and employee questions from these channels; without tool permissions, it will ask the user for key points and let the Skill handle the formatting. This allows the Skill to work in both “integrated environment” and “pure conversational input” modes.

4. A representative example of enterprise collaboration scenarios¶

In the classification of the anthropics/skills repository, internal-comms belongs to the Enterprise & Communication skill set, alongside document-related Skills such as docx and pdf. It demonstrates that Skills can not only assist creativity and development, but also固化 the organization’s internal communication conventions for team members to reuse.

Installation and Activation¶

internal-comms is a standard Skill directory containing SKILL.md, the examples/ subdirectory, and LICENSE.txt, with no additional dependencies required.

Usage in Cursor¶

Cursor will automatically discover Skills from the following paths (official documentation):
- Project level: .cursor/skills/ or .agents/skills/
- User level: ~/.cursor/skills/ or ~/.agents/skills/

Copy the official directory to the corresponding location:

git clone https://github.com/anthropics/skills.git
mkdir -p ~/.cursor/skills
cp -r skills/skills/internal-comms ~/.cursor/skills/

If you want to share it with your team, you can place it in the project root directory:

mkdir -p .cursor/skills
cp -r skills/skills/internal-comms .cursor/skills/

Restart Cursor or confirm that the Skill has been detected in Customize → Skills. The agent will automatically determine whether to enable it based on the description field, or you can manually call it by entering /internal-comms in the Agent conversation.

Usage in Claude Code¶

Anthropic’s official README provides a plugin installation method. internal-comms is included in the example-skills plugin set:

/plugin marketplace add anthropics/skills
/plugin install example-skills@anthropic-agent-skills

After installation, mentioning requirements such as “write a 3P update” or “draft a Newsletter” in the conversation will trigger the Skill; you can also directly specify “use the internal-comms skill”.

Usage in Claude.ai and API¶

According to the anthropics/skills README:
- Claude.ai: Sample Skills are now available to paid plan users; see Using skills in Claude for how to upload custom Skills.
- Claude API: You can use pre-built or uploaded Skills via the Skills API, refer to Skills API Quickstart.

Usage in compatible tools such as Codex CLI¶

Cursor’s documentation notes that to be compatible with the Claude and Codex ecosystems, it will also scan .codex/skills/ and ~/.codex/skills/. Place the internal-comms directory in the corresponding path, and the specific behavior shall be subject to the documentation of each tool.

Typical Usage Examples¶

After installation, you don’t need to memorize template details—just describe your requirements in natural language. Below are reproducible examples based on the official guide.

Example 1: Write a team 3P weekly report¶

Please use the internal-comms skill to write this week's 3P update for the "Platform Team".
Time range: August 1st – August 7th.
Progress: Launched a new log aggregation dashboard, P99 latency decreased by 12%.
Plans: Connect to the alert rule migration next week.
Problems: Insufficient disk quota in the test environment, affecting integration tests.

The agent will load examples/3p-updates.md, output a three-part update that conforms to the fixed format, and control the length of each section.

Example 2: Draft a company Newsletter¶

Help me write a company Newsletter for the second week of August, targeting 1000+ employees.
Key points include: Q3 product roadmap released, completed Series B financing, link to All-Hands recording.
Use the "we" tone, 1–2 sentences per bullet point, organize by product, marketing, and culture categories.

The agent will refer to examples/company-newsletter.md, generate a draft newsletter with section titles and bullet points, and prompt you to add Slack / document links.

Example 3: Compile an FAQ¶

Employees have repeatedly asked about the new office policy and remote work days in Slack #general,
please organize them into an FAQ, with each entry including a question and 1–2 sentences of answer.

The agent will load examples/faq-answers.md, output content in “Question / Answer” pairs, and suggest linking to the official policy document.

Example 4: Incident report (general communication)¶

The payment service experienced a 5xx peak from 23:00–23:45 last night, and has been rolled back.
Please write a brief incident notification for all employees, with a formal tone, presenting conclusions first followed by details.

Since there is no separate incident report template, the agent will use examples/general-comms.md: first confirm the audience and tone, then draft according to the principles of “important information first, active voice, concise and clear”.

Applicable Scenarios and Notes¶

Who is this for¶

• Team Lead / PM: Weekly 3P updates, project status updates;
• HR / Internal Communications: All-staff Newsletters, policy FAQs;
• SRE / On-call Engineers: Initial drafts of incident notifications, post-incident explanations;
• Anyone who wants to unify the team’s writing specifications: Just replace the files in examples/ with your company’s own templates.

Customization suggestions¶

The official sample templates are tailored to the English Silicon Valley collaboration context (Slack, Google Drive, emoji titles, etc.). Domestic teams can replace the Markdown files under examples/ with their own formats—for example, using Feishu document structure, Chinese paragraph habits, fixed headers and signatures— the Skill’s workflow remains unchanged, only the specification source is replaced with your files.

Limitations and notes¶

1. Demonstration nature: The anthropics/skills README notes that these Skills are mainly used for demonstration and education, and you need to fully test before using them in a production environment.
2. Does not replace fact-checking: The agent will format based on the materials you provide; if the input is incorrect, the output will also be incorrect. Be sure to manually review incident reports, policy FAQs, etc. before publishing.
3. Tool integration is not required: Slack, Email and other tools mentioned in the guide are “use if available”; pure text input is also usable.
4. Will ask for clarification when there is no matching template: When the type is unclear, the Skill requires the agent to confirm the format with the user to avoid forcibly applying the wrong template.

Summary¶

internal-comms turns “how to write internal communications” from personal experience into a versionable, team-shareable Skill package. It does not generate fancy copy, but helps you maintain consistency in format, length, and tone—exactly meeting the enterprise needs of “writing correctly, writing quickly, writing consistently”.

If you are already using Cursor or Claude Code, you might as well copy the official directory into the Skills path and try writing a 3P weekly report or organizing an FAQ; if you need to adapt it to your company’s style, start by modifying the four Markdown files in examples/.

Official link: https://github.com/anthropics/skills/tree/main/skills/internal-comms