// Developer Tools

Restore Readiness Evidence Auditor

Audit restore-test evidence against declared RPO, RTO, recency, environment, dependency, smoke-check, and evidence requirements.

Get it on Agensi Find another skill $19 one-time

What problem does Restore Readiness Evidence Auditor solve?

A green backup job does not prove that each critical asset, dependency, and application path has recently cleared its declared recovery targets.

Use it to

Prepare an asset-level restore readiness review before an audit or renewal
Find critical systems with no recent restore-test evidence
Check whether tested backup age and restore duration cleared RPO and RTO
Create a vendor or client handoff without granting backup-platform access

What it returns

Severity-ranked restore-evidence findings
Asset-level BLOCKED, GAP, or READY ledger
JSON readiness gate and evidence totals
Review memo tied to the exact policy, inventory, and tests

A representative input and result

fixture-backed sample

input Asset: storefront, RPO 4 hours, RTO 90 minutes, dependency db-primary. Latest test: 8-hour-old backup, 120-minute restore, dependency absent, smoke checks unknown, evidence 178 days old.

result Readiness gate: BLOCK Critical: RPO and RTO breached; required dependency not restored. High: stale evidence and unverified smoke checks. Disposition: storefront BLOCKED until a controlled, evidenced restore test clears the declared policy.

Access and approval boundaries

Read access to user-supplied inventory CSV, restore-test CSV, and policy JSON.
Write access only to the selected local audit output directory.
No backup platform, cloud, browser, network, credential, decryption, or infrastructure access is required.

Known limitations

The result is limited to the supplied policy, asset inventory, and restore-test rows; missing or inaccurate evidence can change the result.
RPO is measured from tested backup creation to restore start, and RTO from restore start to completion; broader business recovery may require separate timing.
READY is not proof of current backup integrity, complete application recovery, regulatory compliance, or future recovery.

// need a reviewed release decision?

Turn this check into launch evidence.

Use this skill for the focused self-serve check. If you need one sanitized app snapshot reviewed across build, tests, data exposure, browser behavior, and recovery evidence, the Launch Evidence Review returns a checksum-pinned ledger and prioritized blockers.

See the $149 reviewed option

// choose with context

Is Restore Readiness Evidence Auditor the right skill?

Best fit

A green backup job does not prove that each critical asset, dependency, and application path has recently cleared its declared recovery targets.

It returns

Severity-ranked restore-evidence findings. Asset-level BLOCKED, GAP, or READY ledger.

Do not use it as

It does not access backup systems, decrypt media, restore data, run smoke tests, or change infrastructure.

Compatibility, access, version, and licence

Reads or accesses: Declared local scope: restore-readiness-input/**, restore-readiness-output/**, *.csv, *.json.
Compatibility: Platform-neutral CSV exports from backup, recovery, testing, CMDB, or asset-inventory workflows. A JSON policy using the documented assessment date and evidence requirements. Python 3 for the included deterministic local evidence helper.
Version: 1.0.0
Licence: Review the package licence and seller terms at the linked destination.

What happens next

The Agensi listing opens at the current offer. Complete purchase there, inspect SKILL.md and its bundled files, then add the complete folder to your agent.

Questions

Does it test or restore my backups?

No. It audits local evidence exports. It never accesses backup media, decrypts data, starts a restore, or changes infrastructure.

Which backup platforms are supported?

Any platform can work after its authorized records are mapped to the documented inventory and restore-test CSV fields.

How are RPO and RTO evaluated?

RPO uses tested backup creation to restore start. RTO uses restore start to completion. Broader business recovery timing remains separate.

Does READY prove we can recover today?

No. READY means the latest supplied test cleared the declared evidence checks. Media integrity, current configuration, coverage, and future recovery remain unknown.

What happens when a test row is missing?

An in-scope asset with no supplied test is blocked. The team must determine whether no test occurred or evidence collection is incomplete.

Can it handle application dependencies?

Yes. The inventory declares required asset IDs, and the latest test must record those dependencies as restored.