CD openclaw-upgrade
OpenClaw版本升级标准流程。每次说"升级openclaw"、"openclaw升级"、"更新openclaw"时必须执行,先做环境探测+分类,再按Windows/schtasks或Linux/systemd分支走对应升级方案
As a process D 37/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.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
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 · 6
-
high Dangerous commands
cmd-persistenceSKILL.md:366Persistence mechanism (cron / launchd / scheduled task / autorun registry)schtasks /create /tn "OpenClaw Upgrade Once" `
Medium and low: 5
-
medium Exfiltration
net-credential-useSKILL.md:224Credential used in a network call (verify the destination is the intended service)curl -s -H "Authorization: token $GITHUB_TOKEN" \
-
low Dangerous commands
cmd-privilegeSKILL.md:176Privilege escalation / world-writable permissions (quoted — discussed, not commanded)[ "$JITI_PERM" != "1777" ] && echo "⚠️ /tmp/jiti 权限 $JITI_PERM,建议 sudo chmod 1777 /tmp/jiti" || echo "/tmp/jiti: 1777 ✅"
quoted -
low Exfiltration
read-dotenvSKILL.md:285Reads a .env filecp ~/.openclaw/.env ~/.openclaw/.env.bak-${CURRENT_VER} -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:367Runs PowerShell with execution policy bypassed (security demo / example; quoted — discussed, not commanded)/tr "powershell -NoProfile -ExecutionPolicy Bypass -File C:\Users\n3186\.openclaw\upgr…ps1 -Version $target" `
demoquoted -
low Exfiltration
read-dotenvSKILL.md:464Reads a .env filecp ~/.openclaw/.env.bak-${PREV_VER} ~/.openclaw/.env
Files scanned: 3. 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 37/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. 2 mutating operations with no state check
- 40Consistency. Frontmatter name (openclaw-upgrade) differs from the folder (oc-upgrade)
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70Execution cost. Instruction body is 4734 tokens
- 100Steps. 37 steps
- low 13 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 115: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Structure: 19 headings
- +3Step-by-step instructions: 37 items
- +4Has examples (21 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.