disaster-recovery-plan SKILL.md skillA
disaster-recovery-plan from fattain-naime/engineering-docs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add fattain-naime/engineering-docs/disaster-recovery-plan@git:20260717.2f82174Pins git:20260717.2f82174 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- fattain-naime/engineering-docs
- Path
skills/disaster-recovery-plan/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260717.2f82174, committed Jul 17, 2026
- First version recorded
- Jul 12, 2026
- Size
- 22,569 bytes
- Repository stars
- 6
- License
- MIT
Write a disaster recovery and business continuity plan defining RTO/RPO targets, backup and failover procedures, DR tiers, and a recovery drill cadence for surviving major infrastructure loss, data corruption, ransomware, or regional outages. Use before launch of any system holding critical or financial data, or to formalize continuity commitments for compliance (PCI-DSS, SOC 2, ISO 22301).
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
## Purpose Produce a disaster recovery (DR) and business continuity plan that defines, per system, how much downtime (RTO) and data loss (RPO) is tolerable, and the concrete backup, replication, and failover procedure required to stay within those limits when the primary environment is lost entirely. **A backup that has never been restored is not a backup - it is an unverified assumption.** This skill treats the recovery drill, not the document, as the real proof the plan works. ## Input **Works best with:** The name of the system or service, and what infrastructure it currently runs on. **Also valuable:** Current backup tooling and frequency, any prior outage or data-loss history, compliance obligations (PCI-DSS, SOC 2), and the business cost of downtime or data loss for this system. **Example invocation:** `Write a DR plan for our production system. We run on a single VPS with MySQL, daily automated backups to object storage, no secondary region, and no replica database. Extended downtime and data loss are both expensive for us, but we've never tested a full restore.` ## Key Concepts ### RTO vs RPO …
Read the whole file at its exact version.
How to install
mdr add fattain-naime/engineering-docs/disaster-recovery-plan@sha256:d328001d02e227c0The line at the top of this page pins the label git:20260717.2f82174, 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_xpvuwfyy6e3775he)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 12, 2026 and Jul 17, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260717.2f82174 latest | 2026-07-17 | 2f82174 | 22,569 B | A | view · diff |
| git:20260712.59c5852 | 2026-07-12 | 59c5852 | 7,862 B | A | view · diff |
| git:20260712.7e3d1bb | 2026-07-12 | 7e3d1bb | 7,956 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 (22569 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
fattain-naime/engineering-docs · 6 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xpvuwfyy6e3775he GET https://markdownregistry.com/api/v1/resolve?ref=fattain-naime/engineering-docs/disaster-recovery-plan GET https://markdownregistry.com/api/v1/blob/d328001d02e227c012c462dd006e672fd2e20bc4b5dfced150933fc0f74b8c8b
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.