write-runbook SKILL.md skillA
write-runbook from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/write-runbook@git:20261026.66cdcd9Pins git:20261026.66cdcd9 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/write-runbook/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261026.66cdcd9, committed Oct 26, 2026
- Size
- 7,900 bytes
- Repository stars
- 30
- License
- MIT
Write or rewrite an operational runbook in roost's recordable, gated format, with literal commands for each environment, a run record, pass/fail gates and a rollback, and keep it one to one with the rollout ticket's sub-tasks (one sub-task per stage, same number and name, checked both ways). Use when the user asks for a runbook, a rollout or migration procedure, or says an existing runbook doesn't follow our runbook practices.
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
# Write Runbook
**First, load the team config with `roost-config`.** Runbooks live in `deploy.runbooks.dir` in the `deploy.runbooks.repo` repo. If the config names a model runbook (`deploy.runbooks.model`), read it before writing and follow its shape. Follow every rule in `deploy.runbooks.house_rules` as well as the rules below.
## What every runbook has
1. **Header:** title with the ticket key, the ticket and epic, the audience ("whoever flips X in production"), and the namespace, workload and secret names the commands use.
2. **Preconditions:** what must be merged, deployed and verified first, each checkable.
3. **How to record this run:**
- Copy the runbook to a working file so the template stays blank: `cp docs/runbooks/<file>.md ~/<key>-run-$(date +%Y%m%d).md`
- Capture a transcript: `script -a ~/<key>-run-$(date +%Y%m%d).log`
- A **run header** table (date and operator, environments touched, image tag, transcript path, outcome checkboxes).
- A **status roll-up** table: every step, what it proves, done, result, evidence. Gate rows in bold. A `fail` in any gate stops the run.
…Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/write-runbook@sha256:f46938222d3fe6d5The line at the top of this page pins the label git:20261026.66cdcd9, 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_hok2uddoppt6euhh)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 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 (7900 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hok2uddoppt6euhh GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/write-runbook GET https://markdownregistry.com/api/v1/blob/f46938222d3fe6d5e78b654d17ec9659d480b44c8b7e2fbcf48f49fc512f0333
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.