FD backup-manager-pro
Manage automated backups for OpenClaw configurations, clean expired backups, and create pre-modification snapshots. 自动化备份管理系统：配置备份、过期清理、修改前快照。
As a process D 45/100 · Unfinished process — 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.
- 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 · 16
-
high Dangerous commands
cmd-persistencesetup-cron-auto.sh:77Persistence mechanism (cron / launchd / scheduled task / autorun registry)EXISTING_CRON=$(crontab -l 2>/dev/null || true)
-
high Dangerous commands
cmd-persistencesetup-cron-auto.sh:92Persistence mechanism (cron / launchd / scheduled task / autorun registry)} | crontab -
-
high Dangerous commands
cmd-persistencesetup-cron-auto.sh:95Persistence mechanism (cron / launchd / scheduled task / autorun registry)NEW_CRON=$(crontab -l 2>/dev/null || true)
-
high Dangerous commands
cmd-persistencesetup-cron.sh:94Persistence mechanism (cron / launchd / scheduled task / autorun registry)EXISTING_CRON=$(crontab -l 2>/dev/null || true)
-
high Dangerous commands
cmd-persistencesetup-cron.sh:109Persistence mechanism (cron / launchd / scheduled task / autorun registry)} | crontab -
-
high Dangerous commands
cmd-persistencesetup-cron.sh:112Persistence mechanism (cron / launchd / scheduled task / autorun registry)NEW_CRON=$(crontab -l 2>/dev/null || true)
Medium and low: 10
-
low Dangerous commands
cmd-cron-mentionsetup-cron-auto.sh:77Mentions editing / listing crontabEXISTING_CRON=$(crontab -l 2>/dev/null || true)
-
low Dangerous commands
cmd-cron-mentionsetup-cron-auto.sh:95Mentions editing / listing crontabNEW_CRON=$(crontab -l 2>/dev/null || true)
-
low Dangerous commands
cmd-cron-mentionsetup-cron-auto.sh:116Mentions editing / listing crontabcrontab -l
-
low Dangerous commands
cmd-cron-mentionsetup-cron-auto.sh:129Mentions editing / listing crontab (string literal in code, not executed)echo "1. 查看Cron任务: crontab -l"
code literal -
low Dangerous commands
cmd-cron-mentionsetup-cron-auto.sh:130Mentions editing / listing crontab (string literal in code, not executed)echo "2. 编辑Cron任务: crontab -e"
code literal -
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:94Mentions editing / listing crontabEXISTING_CRON=$(crontab -l 2>/dev/null || true)
-
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:112Mentions editing / listing crontabNEW_CRON=$(crontab -l 2>/dev/null || true)
-
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:133Mentions editing / listing crontabcrontab -l
-
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:151Mentions editing / listing crontab (string literal in code, not executed)echo "1. 查看Cron任务: crontab -l"
code literal -
low Dangerous commands
cmd-cron-mentionsetup-cron.sh:152Mentions editing / listing crontab (string literal in code, not executed)echo "2. 编辑Cron任务: crontab -e"
code literal
Files scanned: 16. 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 45/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 52 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1546 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +1No license
- +2Single-language instructions
- +3Description length 142: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 52 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.