- name
- openclaw-recovery-drill
- description
- This skill should be used when the user asks to test OpenClaw recovery readiness, rehearse backup/restore, run a disaster-recovery drill, validate operator recovery playbooks, check restore confidence before upgrades, or prove that backups are actually restorable instead of merely existing.
OpenClaw Recovery Drill
Use this skill to verify that an OpenClaw deployment can be recovered under pressure.
Goal
Shift the conversation from “we have backups” to “we can recover reliably within an acceptable time.”
Workflow
- Identify the target workspace and any known backup roots.
- Run the bundled drill script.
- Review the readiness score, gaps, and proposed drill plan.
- If the result is
FAIL, treat it as an operator-readiness problem, not a documentation problem. - If the user wants a live drill, execute the restore only in a safe test location first.
Command
node {baseDir}/scripts/recovery-drill.mjs \
--workspace /absolute/path/to/workspace \
--backup-root /absolute/path/to/backupsBoth flags are optional. If omitted, the script checks common OpenClaw locations.
What the script checks
- whether candidate backup roots exist
- whether recent backup files or directories are present
- whether the workspace contains the key operator files needed for recovery
- whether restore/runbook signals exist
- whether backups look recent enough for a realistic drill
- whether the operator has clear next-step drill actions
Output format
The script returns JSON with:
scoreverdictsummaryfindingsrecommendationsdrillPlanevidence
Verdicts
PASS— recovery posture looks usable for a lightweight drillWARN— partial coverage; recoverability is uncertainFAIL— backup or restore confidence is too weak to trust
Important limits
- This is a readiness check, not proof of successful recovery by itself.
- A real drill should restore into an isolated test path and verify startup.
- Presence of backup files does not equal application-level recovery.
References
{baseDir}/references/drill-checklist.md