runbook SKILL.md skillA
runbook from testdouble/han is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testdouble/han/runbook@git:20260819.cdb751ePins git:20260819.cdb751e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testdouble/han
- Path
han-documentation/skills/runbook/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260819.cdb751e, committed Aug 19, 2026
- First version recorded
- Jul 31, 2026
- Size
- 17,354 bytes
- Repository stars
- 334
- License
- MIT
Create or update a runbook for an operational scenario — an incident an alert fires for, a recurring scheduled task, or a known failure mode on a live service — using a consistent template. Use when writing, drafting, authoring, or updating a runbook for an alert, incident, on-call procedure, scheduled maintenance, or operational SOP. Applies a YAGNI preflight requiring the scenario to be real before producing the runbook. Does not produce feature or system documentation — use…
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
# Create or Update Runbook ## Operating Principles - **YAGNI applies to runbooks themselves.** Apply the evidence-based YAGNI rule from [../../references/yagni-rule.md](../../references/yagni-rule.md). A runbook is worth writing only when the scenario is grounded in something real: an alert that has actually fired, a documented incident, a recurring task that exists, or a known failure mode on a service that receives production traffic. Runbooks for hypothetical alerts, "best practice says we should have one," or "we'll need this someday" are YAGNI candidates and the runbook should be deferred until the scenario actually occurs. The canonical anti-pattern from project history: Sentry runbooks for staging-only Sentry where data isn't reaching production — alerts that will never fire because no signal flows. The user always wins; the rule's job is to make the cost of speculative runbooks visible. - **The companion evidence rule applies to the runbook's supporting evidence.** Apply the evidence rule from [../../references/evidence-rule.md](../../references/evidence-rule.md) to the citations that ground the scenario: name …
Read the whole file at its exact version.
How to install
mdr add testdouble/han/runbook@sha256:1fd29933594a1917The line at the top of this page pins the label git:20260819.cdb751e, 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_uue43wv3eau2xxed)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 31, 2026 and Aug 19, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260819.cdb751e latest | 2026-08-19 | cdb751e | 17,354 B | A | view · diff |
| git:20260818.55bdb1d | 2026-08-18 | 55bdb1d | 17,280 B | A | view · diff |
| git:20260731.71a5102 | 2026-07-31 | 71a5102 | 17,168 B | A | view · diff |
| git:20260731.e79299f | 2026-07-31 | e79299f | 17,174 B | A | view · diff |
| git:20260731.d95412f | 2026-07-31 | d95412f | 17,379 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 (17354 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
testdouble/han · 334 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_uue43wv3eau2xxed GET https://markdownregistry.com/api/v1/resolve?ref=testdouble/han/runbook GET https://markdownregistry.com/api/v1/blob/1fd29933594a19177a60c77c98ae7cf776220aa67b5f11ae70d2851fc63eee37
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.