# Why do internal updates get ignored?

Canonical URL: https://bestskillsforclaude.com/en/skills/internal-comms
Language: en
Skill: internal-comms
Publisher: Anthropic (https://github.com/anthropics)
Source: https://github.com/anthropics/skills/tree/main/skills/internal-comms
License as stated by the publisher: Apache 2.0
Runtime: Claude apps and Claude Code
Category: Planning and teamwork
Last reviewed: 2026-08-05

Because the decision is buried under context nobody asked for.

## Short answer
The internal-comms skill helps produce internal announcements, updates and summaries that lead with the decision and the impact instead of the background. It is a small skill with a disproportionate effect in organisations where important changes routinely arrive as unreadable paragraphs.

Best for: Change announcements, incident updates, weekly summaries and anything sent to a whole team.
Skip it if: You are writing for customers, where positioning and brand voice matter more than internal clarity.

## What to remember
- Decision first, context second. Most readers never reach the second half.
- Say explicitly who has to do something, or nobody assumes it is them.
- It is for internal writing. Customer messaging needs brand voice as well.
- Pair it with brand-guidelines when tone is standardised across the company.

## What it changes in practice
Internal writing usually fails by ordering: background, reasoning, discussion, and only then the change. Readers scanning on a phone see everything except the part that affects them.
Inverting the order is unremarkable advice that almost nobody follows under time pressure, which is exactly the kind of thing worth delegating to a skill.

## Where it disappoints
It cannot fix an unclear decision. If the change itself is ambiguous, clear writing only makes the ambiguity easier to see, which is useful but not what was asked for.
Sensitive announcements still need human judgement about what to say and when, which no skill should be making for you.

## Install and first run
1. Install it from anthropics/skills under Apache 2.0.
2. State the decision, who is affected and what they must do, then let the skill arrange the rest.
3. Check that the first two lines survive alone, because for most readers that is the whole message.

## Questions
### Is it only for announcements?
It suits any internal message where a decision or an update has to reach people quickly, including incident updates.

### Does it handle customer communication?
It is aimed at internal clarity. Customer messaging needs brand voice and positioning on top.

### What is the fastest quality check?
Read only the first two lines. If the decision and the affected people are not there, rewrite.

## Sources
- anthropics/skills on GitHub: https://github.com/anthropics/skills
- anthropics/skills, internal-comms skill directory: https://github.com/anthropics/skills/tree/main/skills/internal-comms

## Other languages
- Spanish: https://bestskillsforclaude.com/es/skills/internal-comms
- Brazilian Portuguese: https://bestskillsforclaude.com/pt-br/skills/internal-comms
- Japanese: https://bestskillsforclaude.com/ja/skills/internal-comms