incident-response SKILL.md skillA
incident-response from rampstackco/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rampstackco/claude-skills/incident-response@git:20260810.e5bc675Pins git:20260810.e5bc675 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rampstackco/claude-skills
- Path
skills/incident-response/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260810.e5bc675, committed Aug 10, 2026
- First version recorded
- Apr 28, 2026
- Size
- 9,957 bytes
- Repository stars
- 1,013
- License
- MIT
Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers on incident response, production incident, outage, service down, site down, P0, P1, severity, downtime, on-call, incident commander, status page, postmortem prep. Also triggers…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Incident Response Manage active production incidents from detection to resolution. Stack-agnostic. Tool-agnostic. This skill is for active incidents and incident process. For after-the-fact analysis, use `after-action-report`. For planned launches, use `launch-runbook`. --- ## When to use - An active incident is happening - Building incident response procedures - Defining severity levels - Setting up on-call rotations - Training a team on incident response ## When NOT to use - Post-incident retrospective (use `after-action-report`) - Planned launches (use `launch-runbook`) - Pre-launch issue triage (use `qa-testing`) --- ## Required inputs - Awareness of the incident (alert, customer report, internal observation) - Access to production systems and monitoring - Roles and authorities clearly defined - Communication channels operational --- ## The framework: 5 phases ### 1. Detection How the incident becomes known. **Detection sources:** - Automated alerts (monitoring, SLO violations, error rate spikes) - Customer reports (support tickets, social media, status page subscribers) - Internal observation (engineer notices something off) …
Read the whole file at its exact version.
How to install
mdr add rampstackco/claude-skills/incident-response@sha256:0a35b35d88f8c3c4The line at the top of this page pins the label git:20260810.e5bc675, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_omqdemirz23pjbuh)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 28, 2026 and Aug 10, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260810.e5bc675 latest | 2026-08-10 | e5bc675 | 9,957 B | A | view · diff |
| git:20260507.ac2b078 | 2026-05-07 | ac2b078 | 9,385 B | A | view · diff |
| git:20260505.c80b896 | 2026-05-05 | c80b896 | 9,350 B | A | view · diff |
| git:20260429.c2be03d | 2026-04-29 | c2be03d | 9,246 B | A | view · diff |
| git:20260428.f066ffe | 2026-04-28 | f066ffe | 9,269 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9957 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
rampstackco/claude-skills · 1,013 stars · license MIT · pushed 2026-10-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_omqdemirz23pjbuh GET https://markdownregistry.com/api/v1/resolve?ref=rampstackco/claude-skills/incident-response GET https://markdownregistry.com/api/v1/blob/0a35b35d88f8c3c49a527528f82870b31ce4a593e6e5c2fcfe530441fb7b3e46
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from rampstackco/claude-skills
Every file in rampstackco/claude-skills