Internal Communications Writer
anthropics/skills
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…
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and…
Install Team Communications
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install alirezarezvani/claude-skills team-communications --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/project-management/skills/team-communications .claude/skills/team-communications && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .claude/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communicationsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install alirezarezvani/claude-skills team-communications --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/project-management/skills/team-communications .agents/skills/team-communications && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .agents/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install alirezarezvani/claude-skills team-communications --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/project-management/skills/team-communications .cursor/skills/team-communications && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .cursor/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/alirezarezvani/claude-skills.git --path project-management/skills/team-communications--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install alirezarezvani/claude-skills team-communications --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/project-management/skills/team-communications .gemini/skills/team-communications && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .gemini/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install alirezarezvani/claude-skills team-communicationsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/project-management/skills/team-communications .github/skills/team-communications && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .github/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add alirezarezvani/claude-skills --skill team-communications -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install alirezarezvani/claude-skills team-communications --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/alirezarezvani/claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/project-management/skills/team-communications .opencode/skills/team-communications && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-communications" agent skill from https://github.com/alirezarezvani/claude-skills/tree/main/project-management/skills/team-communications into .opencode/skills/team-communications/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-communications", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-communications- GitHub stars
- 28k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 468 words
- Files
- 5 (incl. references)
- Skills in repo
- 342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and…
- Works in 5 steps: Read the reference file for the matched… → Gather inputs. Use available MCP tools… → Clarify scope. Confirm: team name (for… → …
- Keywords like 3P
- SKILL.md covers Routing, Workflow, Tone & Style (applies to all… and When tools are unavailable, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Team Communications is an agent skill from alirezarezvani/claude-skills. Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for…
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/3p-updates.md`, `references/company-newsletter.md` and `references/faq-answers.md`).
It sits in Writing & Content, covering Internal communications and Newsletters. The repository describes itself as: 380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8… The licence is MIT.
When your agent uses it
- Keywords like 3P
- Incident report
- Any request to summarize work for leadership
- The broader company
Example prompts
- “weekly update”
- “newsletter”
- “internal comms”
- “/team-communications”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Read the reference file for the matched type. Follow its formatting exactly.
- Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user…
- Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
- Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
- Present the draft and ask if anything needs to be added, removed, or reworded.
What it can do on your machine
Read from SKILL.md and the folder at commit 19392f7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Team Communications loads about 1.1k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 173 tokens; SKILL.md has 468 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from alirezarezvani/claude-skills at commit 19392f7, republished under its MIT licence (© alirezarezvani). 468 words, ~1,100 tokens.
Download SKILL.mdSave it as
.claude/skills/team-communications/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- team-communications
- description
- Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms. Use this skill any time the user asks to draft, edit, or format something meant for internal audiences. Trigger on keywords like "3P", "weekly update", "newsletter", "FAQ", "internal comms", "status report", "company update", "team update", "incident report", or any request to summarize work for leadership, teammates, or the broader company. Even casual requests like "write my update" or "summarize what my team did this week" should trigger this skill.
Internal Comms
Originally contributed by maximcoding — enhanced and integrated by the claude-skills team.
Write polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.
Routing
Identify the communication type from the user's request, then read the matching reference file before writing anything:
| Type | Trigger phrases | Reference file |
|---|---|---|
| 3P Update | "3P", "progress plans problems", "weekly team update", "what did we ship" | references/3p-updates.md |
| Newsletter | "newsletter", "company update", "weekly/monthly roundup", "all-hands summary" | references/company-newsletter.md |
| FAQ | "FAQ", "common questions", "what people are asking", "confusion around" | references/faq-answers.md |
| General | anything internal that doesn't match above | references/general-comms.md |
If the type is ambiguous, ask one clarifying question — don't guess.
Workflow
- Read the reference file for the matched type. Follow its formatting exactly.
- Gather inputs. Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull real data. If no tools are connected, ask the user to provide bullet points or raw context.
- Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
- Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
- Present the draft and ask if anything needs to be added, removed, or reworded.
Tone & Style (applies to all types)
- Use "we" — you are part of the company.
- Active voice, present tense for progress, future tense for plans.
- Concise. Every sentence should carry information. Cut filler.
- Include metrics and links wherever possible.
- Professional but approachable — not corporate-speak.
- Put the most important information first.
Show full SKILL.md (210 more words)Show less
When tools are unavailable
If the user hasn't connected Slack, Gmail, Drive, or Calendar, don't stall. Ask them to paste or describe what they want covered. You're formatting and sharpening — that's still valuable. Mention which tools would improve future drafts so they can connect them later.
Anti-Patterns
| Anti-Pattern | Why It Fails | Better Approach |
|---|---|---|
| Writing updates without reading the reference template first | Output won't match company format — user has to reformat | Always load the matching reference file before drafting |
| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |
| Using passive voice for accomplishments | "The feature was shipped" hides who did the work | "Team X shipped the feature" — active voice credits the team |
| Writing walls of text for status updates | Leadership scans, doesn't read — key info gets buried | Lead with the headline, follow with 3-5 bullet points |
| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |
Related Skills
| Skill | Relationship |
|---|---|
project-management/senior-pm | Broader PM scope — status reports feed into PM reporting |
project-management/meeting-analyzer | Meeting insights can feed into 3P updates and status reports |
project-management/confluence-expert | Publish comms as Confluence pages for permanent record |
marketing-skill/content-production | External comms — use for public-facing content, not internal |
© alirezarezvani, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in project-management/skills/team-communications of alirezarezvani/claude-skills.
- SKILL.md
- references/3p-updates.md
- references/company-newsletter.md
- references/faq-answers.md
- references/general-comms.md
Open the folder on GitHubat commit 19392f7
Compare with similar skills
Team Communications next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Communications this skillalirezarezvani/claude-skills | 28k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Internal Communications Writeranthropics/skills | 180k | 38 repos | ~378 | Automated safety check: Pass | Apache-2.0 | |
| Internal Comms Anthropicsickn33/agentic-awesome-skills | 47k | 1 repos | ~702 | Automated safety check: Pass | Apache-2.0 | |
| Internal Communicationsnightly-labs/openbot | 473 | — | ~305 | Automated safety check: Pass | Custom licence | |
| CommsIgorWarzocha/Opencode-Workflows | 122 | — | ~314 | Automated safety check: Pass | None | |
| Internal Commsaiskillstore/marketplace | 430 | — | ~2.8k | Automated safety check: Pass | None |
Similar skills
- Official
Internal Comms Anthropic
sickn33/agentic-awesome-skills
Compatibility alias for internal-comms: draft status updates, newsletters and FAQs from approved sources.
Internal Communications
nightly-labs/openbot
Draft status reports, leadership updates, project announcements, FAQs, newsletters, and incident communications for an internal audience.
Comms
IgorWarzocha/Opencode-Workflows
Apply standardized formats for internal business communications.
Internal Comms
aiskillstore/marketplace
Professional internal communications creation and management with templates for status reports, newsletters, announcements, team updates, and cross-functional communication.
Natural Japanese Business Writing
coji/natural-japanese
Writes and edits Japanese business documents so they read clearly and naturally, removes AI-sounding phrasing and can score how AI-like a text reads.
More from alirezarezvani/claude-skills
All 342 skills in this repoAgile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Product Strategist
alirezarezvani/claude-skills
OKR cascade toolkit for product leaders: generates aligned company-to-team OKRs from five strategy types and scores how well they line up.
App Store Optimization
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store.
AWS Solution Architect
alirezarezvani/claude-skills
Design AWS architectures for startups using serverless patterns and IaC templates.
Campaign Analytics
alirezarezvani/claude-skills
Calculates attribution, funnel and ROI figures for marketing campaigns with three Python scripts that need only the standard library.
Code to PRD
alirezarezvani/claude-skills
Reverse-engineers a frontend, backend or fullstack codebase into a product requirements document with per-page docs, an enum dictionary and an API inventory.
Related
Categories
Questions about Team Communications
What does Team Communications do?
Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and…. Team Communications is an agent skill from alirezarezvani/claude-skills. Write internal company communications — 3P updates (Progress/Plans/Problems), company-wide newsletters, FAQ roundups, incident reports, leadership updates, status reports, project updates, and general internal comms.
When should I use Team Communications?
Team Communications fits situations like: keywords like 3P; incident report; any request to summarize work for leadership; the broader company.
How do I install Team Communications in Claude Code?
Run `npx skills add alirezarezvani/claude-skills --skill team-communications -a claude-code`. Or copy the skill folder (project-management/skills/team-communications in alirezarezvani/claude-skills) into .claude/skills/team-communications in your project. Claude Code loads it when a task matches its description.
How do I install Team Communications in Codex?
Run `npx skills add alirezarezvani/claude-skills --skill team-communications -a codex`. Or copy the skill folder (project-management/skills/team-communications in alirezarezvani/claude-skills) into .agents/skills/team-communications in your project. Codex loads it when a task matches its description.
Can I use Team Communications in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add alirezarezvani/claude-skills --skill team-communications -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-communications, .gemini/skills/team-communications, .github/skills/team-communications and .opencode/skills/team-communications in your project.
What does Team Communications need to run?
SKILL.md names no scripts, command-line tools or credentials: Team Communications is instructions for the agent only.
Does Team Communications access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Team Communications safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Team Communications use?
Team Communications is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Communications use?
About 1.1k tokens (SKILL.md is roughly 4.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.4k tokens, read only when the agent opens those files.
What are the alternatives to Team Communications?
Skills that share tags, products or a category with Team Communications: Internal Communications Writer (anthropics/skills, 180k stars), Internal Comms Anthropic (sickn33/agentic-awesome-skills, 47k stars), Internal Communications (nightly-labs/openbot, 473 stars) and Comms (IgorWarzocha/Opencode-Workflows, 122 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Communications?
alirezarezvani (a GitHub user) maintains it in alirezarezvani/claude-skills, which has 27,891 GitHub stars. The repository holds 342 skills in this directory. The repository was last updated on August 30, 2026.
Source: alirezarezvani/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.