team-communications

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.