agentleFS
kryptophonikkryptophonik/SRE-Skills/skills/sre-incident-command/SKILL.md

sre-incident-command

Skill4 starsChanged 23 days agoMITView on GitHub

Use when an incident is declared or suspected: declare, assign roles (IC, ops, comms, scribe), set severity, keep the timeline, drive decisions, hand off and close. Debugging goes to sre-engineer.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.

    line 12
  2. Distinctive:

    When unsure, pick the higher severity.

    line 26
  3. Distinctive:

    Stabilize first: Ask ops for the fastest safe mitigation (rollback, scale, flag off) before root cause.

    line 39
  4. Distinctive:

    Hand off: if the IC changes or a shift ends (see Handoff note).

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Incident Command

Safety gates (REQUIRED)

  1. Read-only diagnosis first.
  2. Propose each change with risk (low/med/high) and reversibility.
  3. Wait for explicit human approval before any prod-changing command, MCP write tool, or external post.
  4. Act only as approved, verify, and stop and escalate if anything gets worse.

Full rules: sre-safety-gates. Read-only MCP setup: sre-safety-gates/references/mcp.md.

Severity guide

SevDefinitionResponse
SEV-1Critical user impact, revenue/data at risk, broad outagePage IC + on-call now; update cadence per sre-incident-communication
SEV-2Major degradation or partial outagePage on-call; IC assigned; update cadence per sre-incident-communication
SEV-3Minor impact, workaround existsTicket + on-call aware; update cadence per sre-incident-communication
SEV-4No user impactTicket only

When unsure, pick the higher severity; downgrade later.

Roles

  • Incident Commander (IC): owns decisions, severity, and approvals. Always a human, never the assistant. If the paged responder is alone, they are the IC: they say so in the incident channel ("I'm IC until handoff"), page a second person for any SEV-1 or SEV-2, and hand off command when that person joins. When someone else is already responding, nobody self-appoints: agree on the IC first.
  • Ops lead: runs diagnosis and remediation (sre-engineer).
  • Comms lead: a human who approves and sends updates. The assistant only drafts them (sre-incident-communication).
  • Scribe: keeps the timeline (this skill can act as scribe).

Workflow

  1. Declare. Confirm impact, pick severity, open channel/bridge, name the IC.
  2. Assign roles. Record names and contact.
  3. Stabilize first. Ask ops for the fastest safe mitigation (rollback, scale, flag off) before root cause.
  4. Run the loop every 15–30 min: current status, what changed, next actions with owners, next update time.
  5. Track decisions. Log each decision, who approved, and timestamp (UTC).
  6. Hand off if the IC changes or a shift ends (see Handoff note).
  7. Resolve. Confirm metrics at baseline and stable 15+ min; IC declares resolved.
  8. Close out. Draft resolution notice, schedule the postmortem within 48 h of resolution (sre-postmortem-templates), file follow-ups.

Handoff note

## IC handoff — [incident ID] — [time UTC]
- **Severity / status:** [SEV-x / Investigating|Identified|Mitigating|Monitoring]
- **Impact:** [who/what is affected]
- **Timeline so far:** [key events]
- **Hypotheses:** [confirmed / ruled out]
- **Actions in flight:** [owner — action — ETA]
- **Pending approvals / risks:** [...]
- **Next update due:** [time]
- **New IC acknowledges:** [name, time]

Output

  • Incident log: severity, roles, timeline (UTC), decisions with approver, actions, resolution time, follow-ups

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.