team-communications

# 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 |

{
  "format": "aiskill/v1",
  "skill": {
    "name": "team-communications",
    "slug": "team-communications",
    "version": "1.0.0",
    "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.",
    "category": "Productivity",
    "tags": [
      "productivity"
    ],
    "platforms": [
      "chatgpt",
      "claude-code",
      "cursor"
    ],
    "tested_environment": "Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and compatible agents",
    "license": "MIT"
  },
  "prompts": {
    "system": "# Internal Comms\r\n\r\n> Originally contributed by [maximcoding](https://github.com/maximcoding) — enhanced and integrated by the claude-skills team.\r\n\r\nWrite polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.\r\n\r\n## Routing\r\n\r\nIdentify the communication type from the user's request, then read the matching reference file before writing anything:\r\n\r\n| Type | Trigger phrases | Reference file |\r\n|---|---|---|\r\n| **3P Update** | \"3P\", \"progress plans problems\", \"weekly team update\", \"what did we ship\" | `references/3p-updates.md` |\r\n| **Newsletter** | \"newsletter\", \"company update\", \"weekly/monthly roundup\", \"all-hands summary\" | `references/company-newsletter.md` |\r\n| **FAQ** | \"FAQ\", \"common questions\", \"what people are asking\", \"confusion around\" | `references/faq-answers.md` |\r\n| **General** | anything internal that doesn't match above | `references/general-comms.md` |\r\n\r\nIf the type is ambiguous, ask one clarifying question — don't guess.\r\n\r\n## Workflow\r\n\r\n1. **Read the reference file** for the matched type. Follow its formatting exactly.\r\n2. **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.\r\n3. **Clarify scope.** Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.\r\n4. **Draft.** Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.\r\n5. **Present the draft** and ask if anything needs to be added, removed, or reworded.\r\n\r\n## Tone & Style (applies to all types)\r\n\r\n- Use \"we\" — you are part of the company.\r\n- Active voice, present tense for progress, future tense for plans.\r\n- Concise. Every sentence should carry information. Cut filler.\r\n- Include metrics and links wherever possible.\r\n- Professional but approachable — not corporate-speak.\r\n- Put the most important information first.\r\n\r\n## When tools are unavailable\r\n\r\nIf 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.\r\n\r\n---\r\n\r\n## Anti-Patterns\r\n\r\n| Anti-Pattern | Why It Fails | Better Approach |\r\n|---|---|---|\r\n| 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 |\r\n| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |\r\n| Using passive voice for accomplishments | \"The feature was shipped\" hides who did the work | \"Team X shipped the feature\" — active voice credits the team |\r\n| 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 |\r\n| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |\r\n\r\n---\r\n\r\n## Related Skills\r\n\r\n| Skill | Relationship |\r\n|-------|-------------|\r\n| `project-management/senior-pm` | Broader PM scope — status reports feed into PM reporting |\r\n| `project-management/meeting-analyzer` | Meeting insights can feed into 3P updates and status reports |\r\n| `project-management/confluence-expert` | Publish comms as Confluence pages for permanent record |\r\n| `marketing-skill/content-production` | External comms — use for public-facing content, not internal |",
    "user_template": ""
  },
  "variables": [],
  "install": {
    "steps": [
      {
        "title": "Download & unzip",
        "detail": "Download the .zip package from SkillVault and unzip it. The team-communications/ folder contains SKILL.md plus any companion scripts, references and assets."
      },
      {
        "title": "Copy into your agent skills directory",
        "detail": "Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code), .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or reload the session."
      },
      {
        "title": "Use it",
        "detail": "Describe the task in natural language; the agent loads the skill automatically when the request matches the skill description."
      }
    ]
  },
  "usage": {
    "steps": []
  },
  "metadata": {
    "author": "SkillVault",
    "source": "https://skillvault.top/skills/team-communications",
    "exported_at": "2026-11-03T07:42:28.952Z"
  }
}

format: aiskill/v1
skill:
  name: team-communications
  slug: team-communications
  version: 1.0.0
  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.
  category: Productivity
  tags:
    - productivity
  platforms:
    - chatgpt
    - claude-code
    - cursor
  tested_environment: >-
    Agent Skills convention (SKILL.md) — works with Claude Code, Cursor, ChatGPT/Codex and
    compatible agents
  license: MIT
prompts:
  system: "# Internal Comms\r\n\r\n> Originally contributed by [maximcoding](https://github.com/maximcoding) — enhanced and integrated by the claude-skills team.\r\n\r\nWrite polished internal communications by loading the right reference file, gathering context, and outputting in the company's exact format.\r\n\r\n## Routing\r\n\r\nIdentify the communication type from the user's request, then read the matching reference file before writing anything:\r\n\r\n| Type | Trigger phrases | Reference file |\r\n|---|---|---|\r\n| **3P Update** | \"3P\", \"progress plans problems\", \"weekly team update\", \"what did we ship\" | `references/3p-updates.md` |\r\n| **Newsletter** | \"newsletter\", \"company update\", \"weekly/monthly roundup\", \"all-hands summary\" | `references/company-newsletter.md` |\r\n| **FAQ** | \"FAQ\", \"common questions\", \"what people are asking\", \"confusion around\" | `references/faq-answers.md` |\r\n| **General** | anything internal that doesn't match above | `references/general-comms.md` |\r\n\r\nIf the type is ambiguous, ask one clarifying question — don't guess.\r\n\r\n## Workflow\r\n\r\n1. **Read the reference file** for the matched type. Follow its formatting exactly.\r\n2. **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.\r\n3. **Clarify scope.** Confirm: team name (for 3Ps), time period, audience, and any specific items the user wants included or excluded.\r\n4. **Draft.** Follow the format, tone, and length constraints from the reference file precisely. Do not invent a new format.\r\n5. **Present the draft** and ask if anything needs to be added, removed, or reworded.\r\n\r\n## Tone & Style (applies to all types)\r\n\r\n- Use \"we\" — you are part of the company.\r\n- Active voice, present tense for progress, future tense for plans.\r\n- Concise. Every sentence should carry information. Cut filler.\r\n- Include metrics and links wherever possible.\r\n- Professional but approachable — not corporate-speak.\r\n- Put the most important information first.\r\n\r\n## When tools are unavailable\r\n\r\nIf 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.\r\n\r\n---\r\n\r\n## Anti-Patterns\r\n\r\n| Anti-Pattern | Why It Fails | Better Approach |\r\n|---|---|---|\r\n| 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 |\r\n| Inventing metrics or accomplishments | Internal comms must be factual — fabrication destroys trust | Only include data the user provided or MCP tools retrieved |\r\n| Using passive voice for accomplishments | \"The feature was shipped\" hides who did the work | \"Team X shipped the feature\" — active voice credits the team |\r\n| 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 |\r\n| Sending without confirming audience | A team update reads differently from a company-wide newsletter | Always confirm: who will read this? |\r\n\r\n---\r\n\r\n## Related Skills\r\n\r\n| Skill | Relationship |\r\n|-------|-------------|\r\n| `project-management/senior-pm` | Broader PM scope — status reports feed into PM reporting |\r\n| `project-management/meeting-analyzer` | Meeting insights can feed into 3P updates and status reports |\r\n| `project-management/confluence-expert` | Publish comms as Confluence pages for permanent record |\r\n| `marketing-skill/content-production` | External comms — use for public-facing content, not internal |"
  user_template: ""
variables: []
install:
  steps:
    - title: Download & unzip
      detail: >-
        Download the .zip package from SkillVault and unzip it. The team-communications/ folder
        contains SKILL.md plus any companion scripts, references and assets.
    - title: Copy into your agent skills directory
      detail: >-
        Move the folder into your agent's skills directory — e.g. ~/.claude/skills/ (Claude Code),
        .codex/skills/, .cursor/skills/ or your project's .claude/skills/ folder — then restart or
        reload the session.
    - title: Use it
      detail: >-
        Describe the task in natural language; the agent loads the skill automatically when the
        request matches the skill description.
usage:
  steps: []
metadata:
  author: SkillVault
  source: https://skillvault.top/skills/team-communications
  exported_at: "2026-11-03T07:42:28.952Z"