Drafts, edits, and formats internal company communications such as 3P updates, newsletters, FAQs, and incident reports. It ensures the output matches specific company templates, uses a professional yet approachable tone, and highlights key metrics and progress.
Say it in your own words; the assistant finds this recipe by itself. Examples:
Use this skill when the user asks to write, summarize, or format updates for internal audiences like leadership, teammates, or the whole company. It is ideal for creating 3P (Progress/Plans/Problems) reports, company-wide newsletters, or incident post-mortems. It also handles requests to summarize recent team work or answer common internal questions.
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.
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.
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-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? |
| 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 |
LICENSESKILL.mdreferences/3p-updates.mdreferences/company-newsletter.mdreferences/faq-answers.mdreferences/general-comms.mdVendored from alirezarezvani/claude-skills, commit 27cfcd0fb0a4, path project-management/skills/team-communications, licence MIT. The upstream licence file ships inside the skill.