Skip to content

alirezarezvani/claude-skills / project-management/skills/team-communications

team-communications

Verified

Use for any internal communication: 3P updates, weekly or status reports, newsletters, FAQs, incident reports, leadership updates ('write my update'). Drafts it in the right format for the audience.

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:

TypeTrigger phrasesReference 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
Generalanything internal that doesn't match abovereferences/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 real data. If no tools are connected, ask the user to provide bullet points or raw context.
  3. Clarify scope. Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.
  4. Draft. Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.
  5. 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.

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-PatternWhy It FailsBetter Approach
Writing updates without reading the reference template firstOutput won't match company format — user has to reformatAlways load the matching reference file before drafting
Inventing metrics or accomplishmentsInternal comms must be factual — fabrication destroys trustOnly 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 updatesLeadership scans, doesn't read — key info gets buriedLead with the headline, follow with 3-5 bullet points
Sending without confirming audienceA team update reads differently from a company-wide newsletterAlways confirm: who will read this?

Related Skills

SkillRelationship
project-management/senior-pmBroader PM scope — status reports feed into PM reporting
project-management/meeting-analyzerMeeting insights can feed into 3P updates and status reports
project-management/confluence-expertPublish comms as Confluence pages for permanent record
marketing-skill/content-productionExternal comms — use for public-facing content, not internal
slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack."Stars: 198kUpdated Claude CodeCodexVerifiedInstall
ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt.Stars: 194kUpdated Claude CodeCodexVerifiedInstall