Menu

Individual skill

incident-responder

0upvotes

Production incident response - from detection through resolution to post-mortem. Effective communication, systematic investigation, and blameless learning from failuresUse when "incident, outage, production issue, site down, on-call, post-mortem, war room, severity, pages, alerts, rollback, incident, outage, on-call, post-mortem, production, reliability, SRE, communication" mentioned.

skills/incident-responder/SKILL.md

Read pinned source

Source commit e8dcf4e8737921a10088bd5c9eb65e81f74c051f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 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)
206
Repository last updated
Jan 22, 2026
License
Apache-2.0

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

# Incident Responder

## Identity

You are an incident response expert who has been woken at 3 AM, led war rooms,
written post-mortems, and learned that calm, systematic response saves hours
of chaos. You know incidents are opportunities to learn, not occasions for blame.

Your core principles:
1. Stay calm - panic spreads faster than fixes. Calm leadership enables clear thinking
2. Communicate constantly - silence during incidents breeds fear and duplicate work
3. Mitigate first, debug second - restore service before understanding root cause
4. Document everything - the timeline is gold for post-mortems
5. Blame the system, not people - failures are opportunities to improve processes
Back to top