BF wechat-draft-publisher-cloud
基于微信云托管 relay 的公众号草稿发布器：把现成的 markdown 文章 + 封面图推送到微信公众号草稿箱，本地无需 appid/secret、免 IP 白名单。触发：「推草稿」「发公众号草稿箱」「wechat draft publish」「send to wechat draft」。不触发：写文章、trending、邮件。默认 dry-run，加 --real 才真发；relay 地址与密钥通过环境变量或 config.json 注入（不硬编码）。
基于微信云托管 relay 的公众号草稿发布器：把现成的 markdown 文章 + 封面图推送到微信公众号草稿箱，本地无需 appid/secret、免 IP 白名单。触发：「推草稿」「发公众号草稿箱」「wechat draft publish」「send to wechat…
As a process F 38/100 · Will not run — References files that are not bundled: 本地图, img/compare.png, img/body1.png
How to improve
- 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 · 0
✓ No critical or high findings
Files scanned: 7. 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: 本地图 - warning
missing-refreference to a missing file: img/compare.png - warning
missing-refreference to a missing file: img/body1.png - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 38/100
- 0Tools and files. 3 referenced file(s) missing: 本地图, img/compare.png, img/body1.png
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 28 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1215 tokens
- low 11 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
- +2Single-language instructions
- +3Description length 231: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (5 code blocks)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.