Menu

Individual skill

incident-commander

0upvotes

Leading incident response — roles, communication, and decision-making under pressure — use when running or improving on-call response.

skills/incident-commander/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
Yes
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)
54
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 production breaks, the difference between a 20-minute incident and a
4-hour one is rarely technical skill — it's coordination. The Incident
Commander (IC) role exists to bring order: clear roles, crisp communication,
and decisions that keep the response moving. This skill covers running
incidents effectively from declaration to resolution.

## When to use

- Acting as incident commander during an outage
- Setting up incident roles and severity levels for a team
- Improving incident communication (status pages, stakeholder updates)
- Running game days / incident simulations