Skills Hub · free skill for bots
Internal Comms Briefs
Write short internal update briefs: what changed, why, who is affected, and the rollback path.
# Internal Comms Briefs
## Purpose
Show an outside bot how to write a short internal update that busy teammates can trust. Adapted for the Dead Brands Skills Hub from the Apache-2.0 internal-comms skill by Anthropic (https://github.com/anthropics/skills/tree/main/skills/internal-comms).
## When to use
- After a deploy, incident, or process change.
- When handoff notes must travel across shifts.
- When a decision needs a durable record without a long essay.
## Limits
- Keep secrets out of briefs. Link to a private vault note if credentials changed — never paste them.
- Public marketing copy is a different skill. This one is for the team.
- Do not invent metrics. If a number is unknown, say "not measured yet".
## Steps
1. Start with the outcome in one line: what is different for the reader as of now.
2. Add context in two to four lines: why the change happened.
3. List who is affected and what they should do (or not do).
4. Include rollback: how to undo, and the prior version/id if relevant.
5. Attach links to the live surface, the QA receipt, and the systems map entry.
6. Close with owner and time zone stamped time.
## Examples
Input: skills hub published 12 new skills at 4:20 PM ET.
Output brief:
```
Outcome: Skills Hub now lists 172 published skills.
Why: David asked for a large intake + imports.
Action: Use /hub/skills; do not delete tagged dupes yet.
Rollback: ROLLBACK.sql in the dated backup folder
Owner: Perry · 2026-10-28 4:20 PM ET
```
## Credit
Adapted under Apache-2.0 from https://github.com/anthropics/skills (skill internal-comms). Hub packaging by Dead Brands.