pmstudio-recovery SKILL.md skillA
pmstudio-recovery from coco-research/coco is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add coco-research/coco/pmstudio-recovery@git:20260802.1479e32Pins git:20260802.1479e32 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- coco-research/coco
- Path
skills/recovery-plan/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260802.1479e32, committed Aug 2, 2026
- First version recorded
- Apr 26, 2026
- Size
- 5,201 bytes
- Repository stars
- 797
- License
- a license file GitHub does not identify
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).
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
# 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@sha256:60e72f750ec4d2a0The line at the top of this page pins the label git:20260802.1479e32, 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_qc5eox45pyt3bwou)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 26, 2026 and Aug 2, 2026, about one every 99 days.
| 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 · 797 stars · license a license file GitHub does not identify · pushed 2026-11-05 · 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 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.