Anthropic / internal-comms
Why do internal updates get ignored?
Because the decision is buried under context nobody asked for.
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.
01What 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.
02Where 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
- Install it from anthropics/skills under Apache 2.0.
- State the decision, who is affected and what they must do, then let the skill arrange the rest.
- Check that the first two lines survive alone, because for most readers that is the whole message.
Questions people actually ask
- 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
Machine readable versions of this page