Menu

Individual skill

incident-comms

0upvotes

Communicate during incidents — stakeholder updates, severity frameworks, war-room comms, and post-incident reviews.

skills/incident-comms/SKILL.md

Read pinned source

Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 8, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
55
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Overview

When systems fail, communication determines whether an incident is a blip or a crisis. This skill covers incident communications: severity frameworks, stakeholder update cadences, war-room communication discipline, customer messaging, executive briefings, and blameless post-incident reviews.


Incident communication is crisis communication at operational speed: telling affected customers what is happening, what you are doing, and when they will hear more — while the incident is still unfolding. Done well, it preserves trust through the worst moments; done poorly, it amplifies every failure. This is a rehearsed discipline, not improvisation.
## When to use

- Defining incident severity levels
- Communicating during an active outage
- Briefing executives during incidents
- Writing customer-facing incident updates
- Running post-incident reviews
- Improving incident response processes
Back to top