incident-slo-runbook SKILL.md skillA
incident-slo-runbook from majiayu000/spellbook is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add majiayu000/spellbook/incident-slo-runbook@git:20260626.97a677ePins git:20260626.97a677e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- majiayu000/spellbook
- Path
skills/incident-slo-runbook/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260626.97a677e, committed Jun 26, 2026
- Size
- 1,837 bytes
- Repository stars
- 290
- License
- MIT
Create or audit SLOs, SLIs, alert rules, incident response steps, escalation paths, postmortems, operational runbooks, and customer-impact communication. Use when defining production reliability, preparing launch readiness, responding to an outage, writing a runbook, tuning alerts, or closing the loop after an incident.
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 SLO Runbook ## Purpose Use this skill to connect observability to action. Metrics and logs are not enough; each critical user journey needs an SLO, alert, owner, response path, and post-incident learning loop. ## SLO Design Define: 1. User journey or system capability. 2. SLI: request success, latency, freshness, durability, or job completion. 3. SLO target and measurement window. 4. Error budget and burn-rate alerts. 5. Exclusions with rationale. 6. Dashboard and data source. 7. Owner and escalation path. Avoid vanity metrics. Prefer user-visible success and latency over internal counters unless internal counters are the only reliable proxy. ## Runbook Requirements Each runbook should include: - Symptom and alert name. - Impacted users or systems. - First 5-minute checks. - Triage decision tree. - Mitigation steps with commands. - Rollback or failover path. - Escalation owner. - Customer/support communication note. - Postmortem trigger. Commands must be safe to run or explicitly labeled destructive. ## Incident Flow 1. Declare severity and incident commander. 2. Confirm impact from live evidence. 3. Stabilize with the lowest-risk mitigation. …
Read the whole file at its exact version.
How to install
mdr add majiayu000/spellbook/incident-slo-runbook@sha256:78027b49edde1321The line at the top of this page pins the label git:20260626.97a677e, 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_iyawcmtjzd5oux6b)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 26, 2026.
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 (1837 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
majiayu000/spellbook · 290 stars · license MIT · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_iyawcmtjzd5oux6b GET https://markdownregistry.com/api/v1/resolve?ref=majiayu000/spellbook/incident-slo-runbook GET https://markdownregistry.com/api/v1/blob/78027b49edde132129540577f7d43a1caca8797ffb94707ea4f34e5870b80b9a
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.