FC openclaw-health-guardian
(no description)
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice
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.
- Add a description to the frontmatter: without it the skill never triggers.
- 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 · 19
-
high Dangerous commands
cmd-persistencescripts/install.sh:98Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$LAUNCH_AGENT_DIR/com.openclaw.healthcheck.plist"
-
high Dangerous commands
cmd-persistencescripts/openclaw-health-check.sh:138Persistence mechanism (cron / launchd / scheduled task / autorun registry)if launchctl bootstrap gui/$(id -u) "$GATEWAY_PLIST" 2>&1 | tee -a "$LOG_FILE"; then
Medium and low: 17
-
medium Dangerous commands
cmd-persistencereferences/troubleshooting.md:14Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist 2>/dev/null
security skill -
medium Dangerous commands
cmd-persistencereferences/troubleshooting.md:15Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl load ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
medium Dangerous commands
cmd-persistencereferences/troubleshooting.md:104Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
medium Dangerous commands
cmd-persistencereferences/troubleshooting.md:147Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)rm -f ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
medium Dangerous commands
cmd-persistencereferences/troubleshooting.md:162Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
medium Dangerous commands
cmd-persistencescripts/install.sh:137Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)echo " 停止服务: launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/install.sh:138Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)echo " 启动服务: launchctl load ~/Library/LaunchAgents/com.openclaw.healthcheck.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/openclaw-health-check.sh:131Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)GATEWAY_PLIST="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
code literal -
medium Dangerous commands
cmd-persistencescripts/openclaw-health-check.sh:133Persistence mechanism (cron / launchd / scheduled task / autorun registry) (code comment)# Method 1: Try launchctl bootstrap directly
comment -
medium Dangerous commands
cmd-persistencescripts/openclaw-health-check.sh:135Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)log "Method 1: Trying launchctl bootstrap..."
code literal -
medium Dangerous commands
cmd-persistencescripts/openclaw-health-check.sh:179Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)GATEWAY_PLIST="$HOME/Library/LaunchAgents/ai.openclaw.gateway.plist"
code literal -
medium Dangerous commands
cmd-persistenceSKILL.md:105Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)~/Library/LaunchAgents/
security skill -
medium Dangerous commands
cmd-persistenceSKILL.md:136Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
medium Dangerous commands
cmd-persistenceSKILL.md:137Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)rm ~/Library/LaunchAgents/com.openclaw.healthcheck.plist
security skill -
low Dangerous commands
cmd-persistenceSKILL.md:86Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row; documentation of a security skill)| `launchctl unload ~/Library/LaunchAgents/com.openclaw.healthcheck.plist` | Stop service |
tablesecurity skill -
low Dangerous commands
cmd-persistenceSKILL.md:87Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation table row; documentation of a security skill)| `launchctl load ~/Library/LaunchAgents/com.openclaw.healthcheck.plist` | Start service |
tablesecurity skill
A further 1 matches are quotations in this security skill's documentation and are not counted as findings.
Files scanned: 9. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
name-missingSKILL.md: frontmatter has no `name` - error
description-missingSKILL.md: no `description` — the skill can never trigger
Process rating: all ten parameters 56/100
- 0Result and completion. Does not say what the result is
- 0When 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
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 903 tokens
- 100Progress reporting. Reports progress
- low 10 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Structure: 11 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (12 code blocks)
- +4Reference files are cited in the instructions (2 of 2)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 14.