cloud-disaster-recovery SKILL.md skillA
cloud-disaster-recovery from amey-thakur/ai-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add amey-thakur/ai-skills/cloud-disaster-recovery@git:20260720.3c9eba4Pins git:20260720.3c9eba4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- amey-thakur/ai-skills
- Path
skills/cloud/cloud-disaster-recovery/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260720.3c9eba4, committed Jul 20, 2026
- Size
- 3,358 bytes
- Repository stars
- 14
- License
- MIT
Build disaster recovery around RTO/RPO tiers, verified backups, and drills that prove the numbers. Use when writing a DR plan or testing whether the existing one actually works.
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
# Cloud disaster recovery DR is a set of promises (how much data lost, how long down) that are only real after a drill proves them. Untested DR is a document that makes people feel better until the day it matters. ## Method 1. **Tier services by business tolerance.** For each service, the owners set RTO (downtime tolerated) and RPO (data loss tolerated), in numbers. Tier 0: minutes/near-zero (payments, auth). Tier 1: hours/minutes. Tier 2: a day/hours (internal tools, analytics). The tier decides the spend; DR-ing everything to tier 0 is how DR programs die of cost. 2. **Match strategy to tier.** Tier 2: backups + restore runbooks. Tier 1: warm standby (replicated data, scaled-down stack) or pilot-light (data live, compute cold but scripted). Tier 0: active-passive with tested promotion or full active-active (see multi-region-design for the write-path reality). Every tier's strategy is IaC-scripted (see infrastructure-as-code); a DR environment built by hand during the disaster is a second disaster. 3. **Design backups against the real threat list.** Not just region loss: ransomware and operator error mean backups must be versioned, …
Read the whole file at its exact version.
How to install
mdr add amey-thakur/ai-skills/cloud-disaster-recovery@sha256:b5b2e65b2dd594c9The line at the top of this page pins the label git:20260720.3c9eba4, 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_lxvviep4elkp3foy)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 20, 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 (3358 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
amey-thakur/ai-skills · 14 stars · license MIT · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lxvviep4elkp3foy GET https://markdownregistry.com/api/v1/resolve?ref=amey-thakur/ai-skills/cloud-disaster-recovery GET https://markdownregistry.com/api/v1/blob/b5b2e65b2dd594c9ff5b98fe1755c6a70999e14f0443607c44824e1c301ed8a7
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.