Incident comms

Skill shinzoxD/knackbox/skills/writing/incident-comms

Write customer and stakeholder communications during incidents. Use whenever the user needs a status page update, outage notice, customer incident email, or internal incident broadcast — separate from the engineering postmortem write-up.From its SKILL.md

Install

npx -y skills add shinzoxD/knackbox --skill incident-comms

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

2.0 KB, 337 tokens by cl100k_base, as published. Nobody here has run it

Incident Communications

During an incident, communications reduce uncertainty. Be honest, frequent enough, and free of blame and speculation presented as fact.

Channels

Channel	Traits
Status page	short, timestamped, impact + next update time
Customer email	clearer narrative, who is affected, what to do
Internal	more detail, war-room links, roles

Workflow

Confirmed facts only: impact, start time, scope, workaround.
Separate known vs investigating.
Next update time commitment.
Customer actions (if any).
Resolve message when mitigated; promise post-incident follow-up without fake RCAs.

Output format

## Status update — <timestamp UTC>
**Impact:** …
**Current status:** investigating | identified | monitoring | resolved
**What we know:** …
**What we are doing:** …
**Workaround:** …
**Next update by:** …

Rules

Never invent root cause; "under investigation" is valid.
No humor that minimizes customer pain.
Security incidents: minimize exploit detail in public channels.
Match severity cadence (more frequent when impact is high).
Align public wording with legal/support guidance when provided.
Engineering postmortems are a different skill (incident-postmortems).

Edge cases

Partial degradation: be specific about who is affected.
False alarm: brief resolve with apology for noise if customers saw it.
Prolonged incident: rolling updates without repeating empty filler.

What ships with it: 1 file

1.3 KB alongside SKILL.md

benchmarks/

prompts.json1.3 KB