CC qclaw-watchdog
QClaw Watchdog - Monitors and auto-restarts QClaw when issues are detected. Works independently of QClaw, communicates via Feishu for alerts and commands. QClaw 看门狗 - 监控并自动重启 QClaw，独立于 QClaw 运行，通过飞书发送告警和接收指令。
As a process C 51/100 · Has gaps — 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.
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.
- 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
-
high Dangerous commands
cmd-persistenceSKILL.md:106Persistence mechanism (cron / launchd / scheduled task / autorun registry)cp com.user.qclaw-watchdog.plist ~/Library/LaunchAgents/
-
high Dangerous commands
cmd-persistenceSKILL.md:107Persistence mechanism (cron / launchd / scheduled task / autorun registry)launchctl load ~/Library/LaunchAgents/com.user.qclaw-watchdog.plist
Medium and low: 2
-
low Secrets in code
secret-high-entropy-tokenconfig.json:4High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"app_secret": "jfQq…f0L",
quoted -
low Dangerous commands
cmd-background-processSKILL.md:96Starts a background / autostarted processnohup ./start.sh >> watchdog.log 2>&1 &
Files scanned: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
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. 2 mutating operations with no state check
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 947 tokens
- low 10 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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +3Description length 209: enough signal without eating the budget
- +4Structure: 23 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (12 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.