BC clawtune
为人类用户提供 AI 原创音乐歌单，并在合适时机把灵感推进成一首歌。用户提到想听背景音乐、需要歌单、表达情绪、送礼、纪念、想把故事写成歌、想下单、想查完成后结果时，都应优先使用本 skill。始终遵守对象锚点与恢复规则，不要临时自由发挥。
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Exfiltration
net-credential-usescripts/api-request.sh:42Credential used in a network call (verify the destination is the intended service)CURL_ARGS+=( -H "Idempotency-Key: ${CLAWTUNE_IDEMPOTENCY_KEY}" )
Files scanned: 28. 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")
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. 113 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1036 tokens
- low 10 top-level sections: this looks like several domains in one skill
- medium 8 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
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 119: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -37 of 17 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +4Structure: 28 headings
- +3Step-by-step instructions: 113 items
- +4Reference files are cited in the instructions (2 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 66.