Home / qa-aman / claude-skills · GitHub

incident-response SKILL.md skillA

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

Install it, pinned

mdr add qa-aman/claude-skills/incident-response@git:20260303.ca0168f

Pins git:20260303.ca0168f in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: qa-aman/claude-skills
Path: skills/by-role/devops/incident-response/SKILL.md
Versions recorded: 1
Latest version: git:20260303.ca0168f, committed Mar 3, 2026
Size: 4,999 bytes
Repository stars: 21
License: MIT

Run a structured incident response. Use when the user says "we have an incident", "production is down", "service is degraded", "on-call response", "p0 incident", "something is broken in prod", "help me manage this incident", "incident commander", or there is an active production issue requiring coordinated response - even if they don't explicitly say "incident response".

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

## Overview

Based on the **Google SRE Book** by Beyer, Jones, Petoff & Murphy. Google's incident management framework establishes clear roles, communication protocols, and decision hierarchies that let teams respond to complex outages without chaos. The core principle: when systems fail, the response should be calmer and more structured than the incident itself.

Three SRE roles during an incident:
- **Incident Commander (IC)** - owns the response, makes decisions, delegates
- **Operations Lead** - makes changes to the system (the IC does not touch production)
- **Communications Lead** - handles stakeholder updates, keeps IC focused on the incident

## Workflow

### Step 1: Declare the incident

If in doubt, declare. It's always easier to stand down an incident than to escalate a non-incident that becomes one.

Set severity:

| Severity | Criteria | Response time |
|----------|----------|---------------|
| SEV1 / P0 | Total outage, revenue impact, data loss | Immediate - all hands |
| SEV2 / P1 | Significant degradation, major feature down | < 15 min response |
| SEV3 / P2 | Minor degradation, workaround available | < 1 hour response |

### Step 2: Assign the IC
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add qa-aman/claude-skills/incident-response@sha256:704162d5fd67a60b

The line at the top of this page pins the label git:20260303.ca0168f, 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](https://markdownregistry.com/badge/art_ldusqj6ypu3xh6cs.svg)](https://markdownregistry.com/a/art_ldusqj6ypu3xh6cs)

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

Versions

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

version	committed	commit	size	audit
git:20260303.ca0168f latest	2026-03-03	ca0168f	4,999 B	A	view

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 (4999 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

qa-aman/claude-skills · 21 stars · license MIT · pushed 2026-10-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ldusqj6ypu3xh6cs
GET https://markdownregistry.com/api/v1/resolve?ref=qa-aman/claude-skills/incident-response
GET https://markdownregistry.com/api/v1/blob/704162d5fd67a60b4362f2db52d2e90c4b3bd2f8597b649b4f9869b98e8021b8

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 qa-aman/claude-skills

create-skill SKILL.md skill

qa-aman/claude-skills · .claude/skills/create-skill/SKILL.md · Create or update Claude Code skills following Anthropic's official skill standard. Use when user says "create a skill"…

git:20260303.4fa499f · audit A · 21 stars

sync-skills SKILL.md skill

qa-aman/claude-skills · .claude/skills/sync-skills/SKILL.md · Fetch skills from projects on the current system, genericize them, and add to the claude-skills repository. Use when…

git:20260303.4fa499f · audit A · 21 stars

CLAUDE.md CLAUDE.md file

qa-aman/claude-skills · CLAUDE.md

git:20260808.3d6e28d · audit A · 21 stars

audit-workpaper SKILL.md skill

qa-aman/claude-skills · skills/by-role/accountant/audit-workpaper/SKILL.md · Write a clear, reviewable audit workpaper documenting procedures, evidence, and conclusions. Use when an auditor says…