BC openclaw-security-checklist
OpenClaw 部署前安全检查清单。聚焦合规导向的部署前检查(非事后加固),覆盖防火墙、SSH、API 密钥管理、数据出境合规、多部署场景验证。使用清单式检查,可逐项打勾并生成报告。适用于个人 Mac、VPS、Docker、企业部署场景。
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
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
- 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 · 11
✓ No critical or high findings
Medium and low: 11
-
medium Dangerous commands
cmd-persistencereferences/deployment-scenarios/enterprise.md:142Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)echo "0 0 1 * * certbot renew --quiet" | crontab -
security skill -
low Dangerous commands
cmd-cron-mentionREADME.md:230Mentions editing / listing crontab (documentation of a security skill)# crontab -e
security skill -
low Secrets in code
secret-password-literalreferences/api-key-management.md:72Hard-coded password / key literal (may be an example) (placeholder value)const apiKey = "sk-1…def";
placeholder -
low Dangerous commands
cmd-shell-rcreferences/api-key-management.md:158Writes to a shell startup file (documentation of a security skill)echo "export OPENCLAW_API_KEY=$NEW_KEY" >> ~/.zshrc
security skill -
low Dangerous commands
cmd-shell-rcreferences/deployment-scenarios/docker.md:63Writes to a shell startup file (documentation of a security skill)echo "export DOCKER_CONTENT_TRUST=1" >> ~/.bashrc
security skill -
low Secrets in code
secret-password-literalreferences/deployment-scenarios/docker.md:267Hard-coded password / key literal (may be an example) (placeholder value)ENV API_KEY=sk-1…890
placeholder -
low Dangerous commands
cmd-cron-mentionreferences/deployment-scenarios/docker.md:361Mentions editing / listing crontab (documentation of a security skill)# crontab -e
security skill -
low Dangerous commands
cmd-background-processreferences/deployment-scenarios/vps.md:103Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable firewalld
security skill -
low Dangerous commands
cmd-privilegereferences/deployment-scenarios/vps.md:114Privilege escalation / world-writable permissions (documentation of a security skill)sudo cp /etc/fail2ban/jail.conf /etc/fail2ban/jail.local
security skill -
low Dangerous commands
cmd-background-processreferences/deployment-scenarios/vps.md:115Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable fail2ban
security skill -
low Dangerous commands
cmd-background-processreferences/deployment-scenarios/vps.md:127Starts a background / autostarted process (documentation of a security skill)sudo systemctl enable yum-cron
security skill
Files scanned: 14. 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")
Process rating: all ten parameters 51/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
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 47 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 840 tokens
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
- -220 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 120: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.