pmstudio-recovery skillA
pmstudio-recovery is agent-read markdown (skill) from coco-research/coco: Generate detailed service restoration runbooks with step-by-step procedures. Use when someone asks to "create recovery procedures", "restoration runbook", "recovery steps", "how to restore service", or needs tactical step-by-step procedures for recovering from disaster scenarios. This is the execution companion to the DR plan — DR defines what and when, recovery-plan defines exactly how. Requires a DR plan to exist (will prompt to run /pmstudio-dr first if missing)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Recovery Plan — Service Restoration Runbooks ## Purpose Generates step-by-step runbooks for each disaster scenario defined in the DR plan. These are **tactical execution documents** — meant to be followed during an actual incident by someone who may not be the person who wrote the plan. ## Prerequisites **Hard dependency:** A DR plan must exist at `Operational/DR-Plan-*.html`. If not found, respond: > "No DR plan found for this project. The recovery plan is built from DR plan scenarios and RTO/RPO targets. Run `/dr-plan` first to create one, then run `/recovery-plan` to generate the runbooks." ## Process ### Step 1: Read Context **Required:** - `Operational/DR-Plan-*.html` — scenarios, RTO/RPO targets, dependencies, communication plan - `CLAUDE.local.md` — architecture, contacts, integrations **Optional (enriches the runbooks):** - `Operational/IRP-*.html` — escalation matrix, communication templates - `PRD/*.html` — integrations detail, technical considerations - `Architecture/` — system diagrams for reference ### Step 2: Extract Scenarios From the DR plan, extract: - Each disaster scenario (name, description, trigger condition) - RTO/RPO targets per component …
Read the whole file at its exact version.
How to install
mdr add coco-research/coco/pmstudio-recovery@git:20260802.1479e32mdr add coco-research/coco/pmstudio-recovery@sha256:60e72f750ec4d2a0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_qc5eox45pyt3bwou)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260802.1479e32 latest | 2026-08-02 | 1479e32 | 5,201 B | A | view · diff |
| git:20260426.d53cc6c | 2026-04-26 | d53cc6c | 5,189 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 (5201 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
coco-research/coco · 478 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qc5eox45pyt3bwou GET https://markdownregistry.com/api/v1/resolve?ref=coco-research/coco/pmstudio-recovery GET https://markdownregistry.com/api/v1/blob/60e72f750ec4d2a0775203ee5e2529120750ca799e2f02a2b20ed172125b92b6
Your agent 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.