Restore-Test Verification SKILL.md skillA
Restore-Test Verification 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/Restore-Test Verification@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/restore-test-verification/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260804.5567c51, committed Aug 4, 2026
- First version recorded
- Jul 15, 2026
- Size
- 8,441 bytes
- Repository stars
- 52
- License
- Apache-2.0
Whether a backup is actually recoverable rather than merely present: the ranked hierarchy of restore evidence (actual restore performed, full boot/virtualization verification, screenshot verification, spot-check restore drill, no evidence at all), adequate test cadence per data-criticality tier, and why a never-tested backup is the highest-priority finding — outranking even an actively failing job.
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
# Restore-Test Verification ## Overview A backup job reporting "success" proves that data was copied somewhere. It proves nothing about whether that data can be turned back into a working system or a usable file when someone actually needs it. Corruption, encryption-key problems, application- consistency failures, and format incompatibilities routinely surface only at restore time — never during the backup run itself. The gap between "backed up" and "recoverable" is where most DR failures actually happen, and it is invisible from a job-success dashboard. This skill exists to make that gap visible: tracking what restore-test evidence actually exists per protected system, and flagging where it doesn't. This skill assumes backup jobs are already running (see `backup-job-health` for that layer) and asks the next question: if this needed to be restored today, is there any evidence it actually could be? ## Anti-triggers - **Fetching a screenshot or boot-verification record** — the screenshot, activity, and asset endpoints are the appliance's own API surface; use `datto-bcdr-api-patterns`. This skill weighs what that evidence proves and flags where none exists. …
Read the whole file at its exact version.
How to install
mdr add wyre-ai/msp-claude-plugins/Restore-Test Verification@sha256:454eef1c97d1156eThe 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_dtjearbc5ndtjxvz)
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,441 B | A | view · diff |
| git:20260728.b7e78fc | 2026-07-28 | b7e78fc | 7,921 B | A | view · diff |
| git:20260715.834bb35 | 2026-07-15 | 834bb35 | 8,366 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 (8441 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_dtjearbc5ndtjxvz GET https://markdownregistry.com/api/v1/resolve?ref=wyre-ai/msp-claude-plugins/Restore-Test Verification GET https://markdownregistry.com/api/v1/blob/454eef1c97d1156e0182f4b07be060dfc90df4d194b6fbb7c6efda08dbfe6bbd
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.