team-communications
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.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- Internal Comms
- Routing
- Workflow
- Tone & Style (applies to all types)
- When tools are unavailable
- Anti-Patterns
- Related Skills
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. 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
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- alirezarezvani/claude-skills
- Source file
- project-management/skills/team-communications/SKILL.md
- Fixed revision
- 8f082544116fc0d014188e521ca40304cdfc86b0
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: alirezarezvani/claude-skills · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T14:01:47.436Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.