BB openclaw-emergency-rollback
OpenClaw Emergency Config Rollback — dead man's switch system for safely making risky changes to OpenClaw configuration. Use this skill whenever the user mentions wanting to make changes to openclaw.json or agent configs and wants a safety net, says anything like "set emergency recovery", "create a snapshot", "take a backup before changes", "set a backout timer", "restore snapshot", "accept changes", "test emergency recovery", "run recovery test", "how does the rollback work", "what rollback commands", or any variation of wanting to safely change OpenClaw config with an automatic recovery fallback. Also trigger when the user asks about recovery, rollback, emergency restore, or testing the recovery system in the context of OpenClaw. This skill manages the full lifecycle: snapshots, watchdog timers, auto-restore, post-restart reminders, and destructive testing of the recovery pipeline — all without requiring AI, network, or user intervention once the timer is set. Uses only Node.js (already required by OpenClaw), zip, and unzip. No additional dependencies to install.
As a process B 65/100 · Nearly there — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- Shorten the description to 1024 characters.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
low Concealment
en-hide-from-userreferences/SETUP.md:209Instruction to hide actions from the user (negated — the text forbids it)Never silently delete snapshots — always back them up first and ask.
negated
Files scanned: 17. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1082 chars, limit 1024
Process rating: all ten parameters 65/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 9 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 32 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 9 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3000 tokens
- 100Progress reporting. Reports progress
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (13 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 1081: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -32 of 10 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 10 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.