0f255f36a9
Based on PR #438 by maximcoding. Enhanced with anti-patterns, cross-references, attribution, and renamed examples/ → references/. meeting-analyzer (254 lines): - Transcript analysis: speaking dynamics, conflict detection, filler words, decision patterns, facilitation quality, active listening - Supports .txt, .md, .vtt, .srt, .docx, .json formats - Trend tracking across multiple meetings team-communications (67 lines + 4 reference templates): - Internal comms: 3P updates, newsletters, FAQ roundups, general comms - 4 reference templates with exact formatting guides - MCP integration (Slack, Gmail, Drive, Calendar) when available Co-Authored-By: maximcoding <maximcoding@users.noreply.github.com> Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
68 lines
4.3 KiB
Markdown
68 lines
4.3 KiB
Markdown
---
|
|
name: team-communications
|
|
description: 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 update" or "summarize what my team did this week" should trigger this skill.
|
|
---
|
|
|
|
# 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 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-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? |
|
|
|
|
---
|
|
|
|
## Related Skills
|
|
|
|
| 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 |
|