DF wukong-invite-monitor
钉钉悟空邀请码监控，零 token 消耗。自动监控邀请码图片版本变化，支持本地 Tesseract OCR 识别和心跳推送通知。
As a process F 35/100 · Will not run — References files that are not bundled: LOCAL-OCR.md
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 skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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.
- 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 · 8
-
high Dangerous commands
cmd-persistenceHEARTBEAT.md:29Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab /tmp/wukong-cron.txt
-
high Dangerous commands
cmd-persistenceREADME.md:83Persistence mechanism (cron / launchd / scheduled task / autorun registry)crontab /tmp/wukong-cron.txt
-
high Dangerous commands
cmd-persistencescripts/setup-cron.sh:6Persistence mechanism (cron / launchd / scheduled task / autorun registry)(crontab -l 2>/dev/null | grep -v wukong; echo "# wukong"; echo "$CRON") | crontab -
Medium and low: 5
-
medium Broad scope
meta-agent-memory-dumpHEARTBEAT.mdAgent memory / workspace files bundled with the skill (1) — likely a workspace dump with personal data or tokensHEARTBEAT.md
-
low Dangerous commands
cmd-cron-mentionHEARTBEAT.md:36Mentions editing / listing crontabcrontab -l | grep wukong
-
low Dangerous commands
cmd-cron-mentionHEARTBEAT.md:121Mentions editing / listing crontabcrontab -e
-
low Dangerous commands
cmd-cron-mentionREADME.md:118Mentions editing / listing crontabcrontab -e # 删除包含 wukong 的行
-
low Dangerous commands
cmd-cron-mentionscripts/setup-cron.sh:6Mentions editing / listing crontab(crontab -l 2>/dev/null | grep -v wukong; echo "# wukong"; echo "$CRON") | crontab -
Files scanned: 13. 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") - warning
missing-refreference to a missing file: LOCAL-OCR.md
Process rating: all ten parameters 35/100
- 0Tools and files. 1 referenced file(s) missing: LOCAL-OCR.md
- 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
- 100Steps. 8 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 195 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)
- +3Description length 64: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -33 of 7 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 5 headings
- +3Step-by-step instructions: 8 items
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.