CF clawusage
Run local clawusage monitoring commands from chat (Telegram/Feishu). Use when user types `/clawusage ...` or asks to check Codex usage, enable/disable auto idle alerts, set idle reminder threshold, or switch language with `lang english|chinese`.
As a process F 41/100 · Will not run — References files that are not bundled: scripts/clawusage.ps1
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.
- The text references files that are not there: add them or drop the references.
- 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 · 7
-
high Dangerous commands
cmd-persistencescripts/clawusage.ps1.txt:152Persistence mechanism (cron / launchd / scheduled task / autorun registry)if (-not (Get-Command Register-ScheduledTask -ErrorAction SilentlyContinue)) { -
high Dangerous commands
cmd-persistencescripts/clawusage.ps1.txt:177Persistence mechanism (cron / launchd / scheduled task / autorun registry)Register-ScheduledTask -TaskName $taskName -Action $action -Trigger $trigger -Settings $settings -Principal $principal -Description "clawusage idle reminder (send to latest OpenClaw chat)." -Force | O
Medium and low: 5
-
medium Dangerous commands
cmd-persistencescripts/clawusage.ps1.txt:153Persistence mechanism (cron / launchd / scheduled task / autorun registry) (quoted — discussed, not commanded)throw "Register-ScheduledTask cmdlet not found on this system."
quoted -
medium Dangerous commands
cmd-execpolicy-bypassSKILL.md:95Runs PowerShell with execution policy bypassed& powershell -NoProfile -ExecutionPolicy Bypass -File (Join-Path $runtimeRoot "claw…ps1") @args
-
low Dangerous commands
cmd-execpolicy-bypassscripts/clawusage.ps1.txt:159Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)"-ExecutionPolicy Bypass",
quoted -
low Dangerous commands
cmd-execpolicy-bypassscripts/clawusage.ps1.txt:248Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)Write-Host ("repair: powershell -NoProfile -ExecutionPolicy Bypass -File `"{0}`"" -f $repairScript)quoted -
low Dangerous commands
cmd-execpolicy-bypassSKILL.md:53Runs PowerShell with execution policy bypassed (quoted — discussed, not commanded)- `& powershell -NoProfile -ExecutionPolicy Bypass -File "<runtime_root>\\claw…ps1" <args>`
quoted
Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/clawusage.ps1
Process rating: all ten parameters 41/100
- 0Tools and files. 1 referenced file(s) missing: scripts/clawusage.ps1
- 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
- 40Consistency. Frontmatter name (clawusage) differs from the folder (clawusage-windows-hardlock)
- 100Steps. 37 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Execution cost. Instruction body is 872 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)
- +4Structure: 1 headings, hard to scan
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 245: enough signal without eating the budget
- +3Step-by-step instructions: 37 items
- +4Has examples (1 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.