BC openclaw-session-cleanup
Diagnose and stabilize long-running OpenClaw deployments that accumulate stale sessions, unreaped agents, browser-control timeouts, gateway websocket 1006 closures, or memory pressure on small VPS hosts. Use when OpenClaw shows too many active sessions, browser control service timeout, gateway abnormal closure, or needs a cleanup/watchdog/sane runtime limits playbook.
As a process C 60/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
- 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
✓ No critical or high findings
Medium and low: 4
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.md:47Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/NeoCh3n/openclaw-session-cleanup-skill/main/scripts/install-to-openclaw.sh | bash
-
medium Dangerous commands
cmd-pipe-to-shell-known-hostREADME.zh-CN.md:49Pipe-to-shell installer from a well-known host (still executes remote code)curl -fsSL https://raw.githubusercontent.com/NeoCh3n/openclaw-session-cleanup-skill/main/scripts/install-to-openclaw.sh | bash
-
low Dangerous commands
cmd-cron-mentionscripts/install-cron-prune.sh:6Mentions editing / listing crontabif crontab -l >/tmp/openclaw-current-crontab 2>/dev/null; then
-
low Dangerous commands
cmd-background-processscripts/install-watchdog.sh:19Starts a background / autostarted processsudo systemctl enable --now openclaw-watchdog.timer
Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 60/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
- 65Failures and branches. 3 branches
- 100Tools and files. No external tools needed
- 100Steps. 23 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 514 tokens
- 100Running it twice. No mutating operations
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
- -31 of 4 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 370: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 23 items
- +4Has examples (7 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.