BC data-sentinel-pro
7x24 小时监控网页、商品价格、竞对动态，变化即通知。 Use when: 用户需要监控特定网页的变化（价格、内容、状态）。 NOT for: 一次性数据查询，实时聊天。
As a process C 57/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
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 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
- 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 Exfiltration
exfil-webhook-urlmonitor.py:121Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)tg_url = f"https://api.telegram.org/bot{config['telegram_token']}/sendMessage"quoted -
medium Exfiltration
exfil-webhook-urlscripts/monitor.py:121Webhook / callback URL commonly used for exfiltration (verify the destination) (quoted — discussed, not commanded)tg_url = f"https://api.telegram.org/bot{config['telegram_token']}/sendMessage"quoted -
low Dangerous commands
cmd-cron-mentioncrontab-example.txt:4Mentions editing / listing crontab (test fixture / example file; documentation of a security skill)# 编辑方式：crontab -e
fixturesecurity skill -
low Dangerous commands
cmd-cron-mentioncrontab-example.txt:21Mentions editing / listing crontab (test fixture / example file; documentation of a security skill)# 4. 运行 crontab -e 粘贴进去
fixturesecurity skill
Files scanned: 10. 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 57/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
- 50When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 25 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 667 tokens
- 100Running it twice. No mutating operations
- 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
- +3Description length 86: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 11 headings
- +3Step-by-step instructions: 25 items
- +4Has examples (11 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.