DC backup
Backup and restore openclaw configuration, skills, commands, and settings. Sync across devices, version control with git, automate backups, and migrate to new machines.
Backup and restore openclaw configuration, skills, commands, and settings.
As a process C 54/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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.
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.
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
- 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.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 4
-
high Dangerous commands
cmd-persistenceSKILL.md:594Persistence mechanism (cron / launchd / scheduled task / autorun registry)# Create plist: ~/Library/LaunchAgents/com.openclaw.backup.plist
-
high Dangerous commands
cmd-persistenceSKILL.md:595Persistence mechanism (cron / launchd / scheduled task / autorun registry)cat > ~/Library/LaunchAgents/com.openclaw.backup.plist << 'EOF'
-
high Dangerous commands
cmd-persistenceSKILL.md:620Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/com.openclaw.backup.plist
Medium and low: 1
-
low Dangerous commands
cmd-cron-mentionSKILL.md:548Mentions editing / listing crontabcrontab -e
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
edit-residuethe text marks something as outdated (lines 30): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 54/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 4437 tokens
- 100Tools and files. No external tools needed
- 100Steps. 6 steps
- 100Consistency. Name and required fields are in place
- low 12 top-level sections: this looks like several domains in one skill
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
- -4Absolute local paths (C:\Users, /home/…): not portable
- +1No license
- +2Single-language instructions
- +3Description length 168: enough signal without eating the budget
- +4Structure: 42 headings
- +3Step-by-step instructions: 6 items
- +4Has examples (29 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.