internal-comms

---
name: internal-comms
description: "Use when writing internal company communications — status reports, leadership updates, 3P updates, newsletters, FAQs, incident reports — so the agent matches your company's preferred formats and tone."
source: https://github.com/anthropics/skills/tree/main/skills/internal-comms
generated: 2026-07-02T18:42:00.260Z
category: concept
audience: general
---

## When to use

- Drafting a weekly 3P update (Progress, Plans, Problems) for a team or leadership
- Writing a company-wide newsletter that needs a consistent house voice
- Answering an FAQ or common question in the company's standard format
- Producing a status report, project update, or incident report for internal readers

## Key concepts

### Communication-type routing

The skill first classifies the request into a known type (3P update, newsletter, FAQ, general) and loads the matching guideline file so formatting and tone fit that specific format rather than a generic template.

### 3P updates (Progress, Plans, Problems)

A structured team-update format organized around what shipped (Progress), what's next (Plans), and what's blocked or risky (Problems). Backed by its own guideline in examples/3p-updates.md.

### Format-specific guideline files

Each comms type has a dedicated guide in the examples/ directory (3p-updates.md, company-newsletter.md, faq-answers.md, general-comms.md) that dictates content gathering, tone, and layout.

### General-comms fallback

Anything that doesn't match a named type routes to general-comms.md; if even that doesn't fit, the skill asks for clarification instead of guessing the desired format.

## API reference

```
npx skills add anthropics/skills --skill internal-comms
```

Install the internal communications writing skill.

```
npx skills add anthropics/skills --skill internal-comms
```

## Gotchas

- The skill only shines when the request clearly names a comms type; vague asks land in the general fallback
- Formatting and tone come from the loaded guideline file, so skipping that load produces off-brand output
- If the type matches no existing guideline, the intended behavior is to ask for clarification, not invent a format
- It's tuned to one company's preferred formats; another org's conventions won't be encoded unless you adapt the examples

---
Generated by SkillMake from https://github.com/anthropics/skills/tree/main/skills/internal-comms on 2026-07-02T18:42:00.260Z.
Verify against source before relying on details.

File: ~/.claude/skills/internal-comms/SKILL.md