Internal Comms
AnthropicOfficialPublished by Anthropic
- Skill
- Content generator
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The internal-comms skill provides a standardized approach for creating consistent and professional internal documentation. It guides the user through selecting appropriate templates for common corporate communication types, such as status reports, newsletters, and project updates, ensuring that tone and formatting align with organizational expectations.
What it does
- Provides templates for 3P progress, plans, and problems updates.
- Offers guidelines for drafting company-wide newsletters.
- Standardizes the format for FAQ responses.
- Supports the creation of incident and project status reports.
- Ensures consistent tone and structure across internal messaging.
When to use it
- When you need to draft regular team or project status updates.
- When preparing leadership communications or company newsletters.
- When responding to frequently asked questions from internal stakeholders.
- When documenting incident reports or project milestones.
Advantages
- Reduces time spent on formatting and structuring internal documents.
- Promotes consistency in communication style across the organization.
- Provides clear guidance for various common corporate reporting scenarios.
Usage examples
- “Write a 3P update for the Q3 marketing project.”
- The agent will load the 3P updates template and draft a report structured by Progress, Plans, and Problems specific to the marketing project.
- “Draft a company newsletter about our new office policy.”
- The agent will apply the company newsletter guidelines to ensure the announcement is formatted correctly for internal distribution.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/internal-comms/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip internal-comms.zip -d .agents/skills
Documentation by Anthropic
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 updatesexamples/company-newsletter.md- For company-wide newslettersexamples/faq-answers.md- For answering frequently asked questionsexamples/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
Files
- ATTRIBUTION.mdAdded by AutoGineer877 B
- LICENSE.txt11.1 KiB
- SKILL.md1.5 KiB
- examples/3p-updates.md3.2 KiB
- examples/company-newsletter.md3.2 KiB
- examples/faq-answers.md2.3 KiB
- examples/general-comms.md602 B
examples/company-newsletter.md
Instructions
You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
Ideally it includes the following attributes:
Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
Tools to use
If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.
Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
Email: look for things from executives that discuss company-wide announcements
Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
External press: if you see references to articles or press we've received over the past week, that could be really cool too.
If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
Sections
The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
Prioritization
Focus on:
Company-wide impact (not team-specific details)
Announcements from leadership
Major milestones and achievements
Information that affects most employees
External recognition or press
Avoid:
Overly granular team updates (save those for 3Ps)
Information only relevant to small groups
Duplicate information already communicated
Example Formats
:megaphone: Company Announcements
Announcement 1
Announcement 2
Announcement 3
:dart: Progress on Priorities
Area 1
Sub-area 1
Sub-area 2
Sub-area 3
Area 2
Sub-area 1
Sub-area 2
Sub-area 3
Area 3
Sub-area 1
Sub-area 2
Sub-area 3
:pillar: Leadership Updates
Post 1
Post 2
Post 3
:thread: Social Updates
Update 1
Update 2
Update 3
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/skills · skills/internal-comms · commit 2c5958e
- Licence
- Apache License 2.0 (redistribution allowed)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download internal-comms.zip