incident-response SKILL.md skillA

incident-response from jamestorrevillas/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add jamestorrevillas/dev-skills/incident-response@git:20260320.869847a

Pins git:20260320.869847a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
jamestorrevillas/dev-skills
Path
.github/skills/incident-response/SKILL.md
Versions recorded
1
Latest version
git:20260320.869847a, committed Mar 20, 2026
Size
3,301 bytes
Repository stars
3
License
MIT

Use this skill when handling production incidents, outages, or critical bugs — from initial detection through resolution and post-mortem. Trigger on keywords: incident, outage, production down, on-call, P1, P2, critical bug, postmortem, root cause analysis, runbook, service disruption.

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

## The Five Phases

```
DETECT → ASSESS → RESPOND → RESOLVE → LEARN
```

Every incident touches all five. Never skip LEARN — it's the only one that prevents recurrence.

---

## Phase 1: Detect & Assess (First 5 Minutes)

```
1. What is broken? (specific service, feature, endpoint)
2. Who is affected? (all users, subset, specific region)
3. What is the impact? (data loss? revenue? user-facing?)
4. When did it start? (correlate with recent deploys/changes)
5. Severity: P1 (all users, data loss) / P2 (major feature) / P3 (minor)
```

**Communicate immediately** — even if you don't know the cause yet:
```
"We're investigating an issue with [service]. 
Impact: [who is affected]. 
We'll update in 15 minutes."
```

---

## Phase 2: Respond (During Incident)

### Incident Roles
- **Incident Commander** — coordinates, communicates, makes calls
- **Technical Lead** — investigates and fixes
- **Communicator** — updates stakeholders

### Response Checklist
- [ ] Create incident channel/ticket
- [ ] Assign IC and Technical Lead
- [ ] Begin investigation (check logs, metrics, recent changes)
- [ ] Post status updates every 15-30 minutes
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_p7rjdhlura6hl6mq/4597bd6ad168f658e40b8679baa3104819ad78da9919c12913101b6426c6b072.json

Then /plugin install incident-response@markdownregistry-p7rjdhlura6hl6mq in Claude Code. It installs git:20260320.869847a, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add jamestorrevillas/dev-skills/incident-response@sha256:4597bd6ad168f658

The line at the top of this page pins the label git:20260320.869847a, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_p7rjdhlura6hl6mq.svg)](https://markdownregistry.com/a/art_p7rjdhlura6hl6mq)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in jamestorrevillas/dev-skills/incident-response since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of incident-response from somewhere else? Ask it: where did my incident-response come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Mar 20, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20260320.869847a latest2026-03-20 869847a 3,301 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (3301 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

GitHub

jamestorrevillas/dev-skills · 3 stars · license MIT · pushed 2026-03-20 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_p7rjdhlura6hl6mq
GET https://markdownregistry.com/api/v1/resolve?ref=jamestorrevillas/dev-skills/incident-response
GET https://markdownregistry.com/api/v1/blob/4597bd6ad168f658e40b8679baa3104819ad78da9919c12913101b6426c6b072

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 jamestorrevillas/dev-skills

copilot-instructions.md
jamestorrevillas/dev-skills · .github/copilot-instructions.md
git:20260320.869847a · audit A · 3 stars
ai-agent-design SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/ai-agent-design/SKILL.md · Use this skill when building AI agents, designing multi-agent systems, integrating LLMs into applications, building RAG…
git:20260320.869847a · audit A · 3 stars
ai-assisted-learning SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/ai-assisted-learning/SKILL.md · Use this skill when using AI to learn new technologies, navigate unfamiliar codebases, do interview prep, identify…
git:20260320.869847a · audit A · 3 stars
ai-prompting-patterns SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/ai-prompting-patterns/SKILL.md · Use this skill when designing how an AI agent should communicate with developers — intent clarification, progress…
git:20260320.869847a · audit A · 3 stars
api-design SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/api-design/SKILL.md · Use this skill when designing or reviewing APIs — REST, GraphQL, tRPC, or gRPC. Trigger on keywords: API design, REST…
git:20260320.869847a · audit A · 3 stars
backend-dev SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/backend-dev/SKILL.md · Use this skill for backend development — server logic, authentication, microservices, serverless functions, middleware…
git:20260320.869847a · audit A · 3 stars
career-growth SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/career-growth/SKILL.md · Use this skill for career planning, goal setting, skill gap analysis, promotion preparation, or thinking through your…
git:20260320.869847a · audit A · 3 stars
client-communication SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/client-communication/SKILL.md · Use this skill when communicating with clients, freelance customers, or external stakeholders — scoping projects…
git:20260320.869847a · audit A · 3 stars
code-explanation SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/code-explanation/SKILL.md · Use this skill when writing code comments, explaining code decisions, documenting the "why" behind implementation…
git:20260320.869847a · audit A · 3 stars
code-reading SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/code-reading/SKILL.md · Use this skill when navigating unfamiliar codebases, understanding legacy code, onboarding to a new project, or…
git:20260320.869847a · audit A · 3 stars
code-review SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/code-review/SKILL.md · Use this skill when performing code reviews, security audits, architecture reviews, vulnerability analysis, or…
git:20260320.869847a · audit A · 3 stars
cross-functional-collab SKILL.md skill
jamestorrevillas/dev-skills · .github/skills/cross-functional-collab/SKILL.md · Use this skill when working with designers, product managers, business stakeholders, or non-technical team members…
git:20260320.869847a · audit A · 3 stars

Every file in jamestorrevillas/dev-skills

Other files named incident-response

incident-response SKILL.md skill
cbrock84/headcount · plugins/security/skills/incident-response/SKILL.md · Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review…
git:20260916.0e7cd01 · audit A · 2,543 stars
incident-response SKILL.md skill
rampstackco/claude-skills · skills/incident-response/SKILL.md · Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured…
git:20260810.e5bc675 · audit A · 1,100 stars
incident-response SKILL.md skill
hypnguyen1209/offensive-claude · skills/incident-response/SKILL.md · Use when responding to or forensically investigating an incident — triage acquisition (Velociraptor/KAPE), Volatility 3…
git:20260630.df7d895 · audit A · 421 stars
incident-response SKILL.md skill
harness/harness-skills · skills/observability-governance/incident-response/SKILL.md · Incident response and analysis via Harness MCP. Correlate incidents with recent deployments, assess blast radius and…
v1.0.0 · audit A · 134 stars
incident-response SKILL.md skill
miosa-osa/osa · priv/skills/incident-response/SKILL.md · Investigate suspected compromise, preserve incident evidence, build a timeline and plan containment, recovery and…
v1.0.200 · audit A · 79 stars
incident-response SKILL.md skill
stbenjam/skillsaw · tests/fixtures/apm/clean/.apm/skills/incident-response/SKILL.md · Triage and respond to production incidents. Use when handling an outage.
v1.2 · audit A · 73 stars
incident-response SKILL.md skill
nahid-sparktales/agent-dispatcher · skills/devops/incident-response/SKILL.md · Stabilize a system that is failing right now — name the signal that flagged it, size the blast radius in numbers, keep…
git:20260919.a0d4f55 · audit A · 58 stars
incident-response SKILL.md skill
drafthq/draft · skills/incident-response/SKILL.md · Incident management lifecycle — triage, communicate, mitigate, postmortem. Three modes — new (start incident), update…
git:20260819.fda278e · audit A · 40 stars

Browse by kind, by grade A, or by owner.

Kept in .github/skills, the folder GitHub Copilot reads. More agent skills for GitHub Copilot.