Retention & RPO Compliance SKILL.md skillA
Retention & RPO Compliance from wyre-ai/msp-claude-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add wyre-ai/msp-claude-plugins/Retention & RPO Compliance@git:20260804.5567c51Pins git:20260804.5567c51 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- wyre-ai/msp-claude-plugins
- Path
msp-claude-plugins/backup-pack/skills/retention-rpo-compliance/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260804.5567c51, committed Aug 4, 2026
- First version recorded
- Jul 15, 2026
- Size
- 8,344 bytes
- Repository stars
- 52
- License
- Apache-2.0
Comparing configured backup retention and cadence against contracted retention windows and RPO (recovery point objective) targets: the two distinct retention gap types (configured-shorter-than-contracted vs. storage-forced truncation), why achievable RPO must be derived from actual job success history rather than the nominal schedule, where the contracted side of the comparison actually lives, and why "no documented requirement" is its own finding rather than an automatic pass.
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
# Retention & RPO Compliance ## Overview Retention and RPO commitments are made in two places that routinely drift apart: the contract or SOW (what was promised — "1-year retention," "4-hour RPO") and the actual backup system configuration (what's actually happening — a 90-day local retention policy, a nightly-only backup schedule). Nobody discovers the gap until a restore request for month 8 of a promised 12-month retention window comes back empty, or a ransomware event reveals that the "4-hour RPO" client's most recent recovery point is actually 22 hours old. This skill exists to find that gap proactively by comparing what's promised against what's configured — not to audit whether backups are running (`backup-job-health`) or recoverable (`restore-test-verification`), both of which are prerequisites to this check actually meaning anything. ## Anti-triggers - **Framework or control compliance** — "compliance" here means a contracted retention window and RPO target, not CIS/SOC 2/HIPAA control evidence; for that use `evidence-mapping` in compliance-pack. - **Reading the agreement itself** — pulling a client's contract terms, …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Retention & RPO Compliance@sha256:f74c082fdaf43295The line at the top of this page pins the label git:20260804.5567c51, 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_pmrjsoidkynmih75)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jul 15, 2026 and Aug 4, 2026, about one every 10 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260804.5567c51 latest | 2026-08-04 | 5567c51 | 8,344 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 7,943 B | A | view · diff |
| git:20260715.834bb35 | 2026-07-15 | 834bb35 | 8,134 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 (8344 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
wyre-ai/msp-claude-plugins · 52 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pmrjsoidkynmih75 GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Retention & RPO Compliance GET https://markdownregistry.com/api/v1/blob/f74c082fdaf432959d57415977229877f36a712ad5b45b847c9a8dcafbc6cdda
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.