SKILLEMALL.ai

BC auto-rollback

Timed rollback safety net for edits to ~/.openclaw/openclaw.json on macOS. Use when changing Gateway config, restarting Gateway after config edits, or needing backup + auto-restore protection via launchd and BOOT.md health-check cancellation.

Not recommendedcritical or high security findings
ClawHub Agent Skills author: extraterrest v1.2.0-alpha.2 MIT-0 5 files · 1 script body ≈ 482 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 55/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

GeneratorInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
82
Quality 40%
85
Run on models
none yet
Process rating
C
55/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

What is at stake

The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.

Dangerous commands
If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

  1. Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
For the model run — optional
  • 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

  • high Dangerous commands cmd-persistence auto-rollback.sh:282
    Persistence mechanism (cron / launchd / scheduled task / autorun registry)
    launchctl load "$plist_file" 2>/dev/null && log "✅ launchd job loaded" || log "⚠️ launchd load failed or job already exists"

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

✓ No remarks against the Agent Skills spec

Process rating: all ten parameters 55/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 13 steps
  • 100Failures and branches. 3 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 482 tokens
  • 100Progress reporting. Reports progress

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

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +2Single-language instructions
  • +3Description length 242: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 13 items
  • +4Has examples (4 code blocks)
  • +1License stated

Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.

External checks

ClawHub: suspicious
This appears to be a legitimate local rollback helper, but it needs review because its cleanup code can trust a mutable state file when deleting a launchd plist.
LLM: suspicious (medium) · VirusTotal: benign · 28 May 2026