team-communications
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 upd
Profile →npx skills add alirezarezvani/claude-skills --skill team-communications --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Internal Comms > Originally contributed by [maximcoding](https://github.com/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 1. **Read the reference file** for the matched type. Follow its formatting exactly. 2. **Gather inputs.** Use available MCP tools (Slack, Gmail, Google Drive, Calendar) to pull
- Routing
- Workflow
- Tone & Style (applies to all types)
- When tools are unavailable
- Anti-Patterns
- Related Skills
What does the team-communications skill do?
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 upd
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill team-communications --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.