CD Proactive Claw
🦞 The most powerful proactive engine for OpenClaw. Your personal assistant that learns from you and helps you be more productive.
🦞 The most powerful proactive engine for OpenClaw.
As a process D 49/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-persistencescripts/install_daemon.sh:68Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load "$PLIST"
Medium and low: 5
-
medium Exfiltration
exfil-webhook-urlscripts/daemon.py:147Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)f"https://api.telegram.org/bot{token}/sendMessage",quoted -
medium Dangerous commands
cmd-persistencescripts/install_daemon.sh:74Persistence mechanism (cron / launchd / scheduled task / autorun registry) (string literal in code, not executed)echo "To restart: launchctl unload \"$PLIST\" && launchctl load \"$PLIST\""
code literal -
medium Dangerous commands
cmd-persistenceSECURITY.md:90Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)launchctl unload ~/Library/LaunchAgents/ai.openclaw.proactive-claw.plist
security skill -
medium Dangerous commands
cmd-persistenceSECURITY.md:91Persistence mechanism (cron / launchd / scheduled task / autorun registry) (documentation of a security skill)rm ~/Library/LaunchAgents/ai.openclaw.proactive-claw.plist
security skill -
low Risky intent
intent-offensive-securitySECURITY.md:146Offensive-security / dual-use content (legitimate for authorised testing; review intended use)| Privilege escalation | No sudo, no root, no system services |
Files scanned: 41. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 49/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
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (Proactive Claw) differs from the folder (proactive-claw)
- 50Failures and branches. 0 branches, has a failure section
- 85Steps. 47 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2666 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 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)
- +3Output format is not stated: the model decides each time
- -332 of 36 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 130: enough signal without eating the budget
- +4Structure: 38 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.