incident-runbook SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
incident-runbook from byerlikaya/claude-starter-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add byerlikaya/claude-starter-kit/incident-runbook@git:20261015.84a7109Pins git:20261015.84a7109 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- byerlikaya/claude-starter-kit
- Path
kit/skills/incident-runbook/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261015.84a7109, committed Oct 15, 2026
- First version recorded
- Sep 24, 2026
- Size
- 2,202 bytes
- Repository stars
- 26
- License
- MIT
Incident response: diagnose → mitigate → resolve, then a blameless postmortem and a repeatable runbook. Stop the impact first, root cause second. Use when production is degraded or broken, an outage keeps recurring, or for the postmortem.
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 & Runbook <!-- routing-eval reads the next line; why it sits in the body: AGENT_TEMPLATE.md --> Trigger phrases: "incident", "incident response", "runbook", "postmortem", "root cause", "outage", "production incident", "post-incident" Two modes: **live incident** (what to do right now) and **aftermath** (postmortem + runbook). Priority: stopping user impact > finding the root cause. No panic, one ordered step at a time. ## Live incident — sequence 1. **Acknowledge & classify** — what is the impact (who, how much), severity (SEV1 full outage … SEV3 minor). 2. **Mitigate the impact FIRST** — rollback, turn off a feature flag, shift traffic, scale up. Without waiting on the root cause. 3. **Single coordinator** — it is clear who decides; communication goes through one channel. 4. **Diagnose** — last change? (deploy/migration/config) narrow it down with logs+metrics+traces (observability). 5. **Resolve** — the smallest safe fix; then verify (health check). 6. **Close** — confirm the impact is over; note the timeline (a postmortem input). ## Mitigation reflexes - Last deploy suspect → **rollback** (deploy revert). …
Read the whole file at its exact version.
How to install
mdr add byerlikaya/claude-starter-kit/incident-runbook@sha256:d75caf94b8079b05The line at the top of this page pins the label git:20261015.84a7109, 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_w2fn2d5kdfvtiorw)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 24, 2026 and Oct 15, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261015.84a7109 latest | 2026-10-15 | 84a7109 | 2,202 B | A | view · diff |
| git:20260924.a457823 | 2026-09-24 | a457823 | 2,204 B | A | view · diff |
| git:20260924.ad81b1a | 2026-09-24 | ad81b1a | 2,398 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 (2202 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
byerlikaya/claude-starter-kit · 26 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w2fn2d5kdfvtiorw GET https://markdownregistry.com/api/v1/resolve?ref=byerlikaya/claude-starter-kit/incident-runbook GET https://markdownregistry.com/api/v1/blob/d75caf94b8079b05fe8716ffd8ea5d39e6e04ce370d62492c6f617378eec501d
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 byerlikaya/claude-starter-kit
Every file in byerlikaya/claude-starter-kit