BD wechat-publisher
微信公众号一键发布技能。帮助用户将 Markdown 文章自动发布到公众号草稿箱， 包括：Access Token 获取、封面图生成与压缩、永久素材上传、草稿 JSON 构造与提交。 当用户要求"发布公众号"、"写公众号文章"、"公众号草稿"时触发。
As a process D 46/100 · Unfinished process — 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.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
medium Exfiltration
exfil-secret-in-urlreferences/api_ref.md:49Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (quoted — discussed, not commanded)$url = "https://api.weixin.qq.com/cgi-bin/material/add_material?access_token=…&type=image"
quoted
Files scanned: 8. 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") - note
frontmatter-keyunknown frontmatter key "agent_created"
Process rating: all ten parameters 46/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
- 40Consistency. Frontmatter name (wechat-publisher) differs from the folder (wechatdoc-publisher)
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Execution cost. Instruction body is 647 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 125: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 32 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 4 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.