BF wechat-tutorial-editor-publisher
模仿作者写作风格,完成教程类微信公众号文章编写,输出 Markdown 文件,一键发布到微信公众号草稿箱。
As a process F 33/100 · Will not run — References files that are not bundled: images/photo.jpg, /Users/bruce/photo.jpg
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.
For the model run — optional
- 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 · 5
✓ No critical or high findings
Medium and low: 5
-
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:36High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…B4t+D+OBkj…bcE+mWTyvVV7D/zsdE…1Rw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:50High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…dTg+QahU…hsw==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:56High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…FFX/+gVeY…NlM++NqRc…bqg==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:122High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…XgO/OSZV…lro+7Hf6…5Fj+EDe8gO/lxc1…xvA==",
detector -
low Secrets in code
secret-high-entropy-tokenscripts/package-lock.json:190High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"integrity": "sha5…EPE+Ei8nl6/g4FB…DDo/DWp0…2Pw==",
detector
Files scanned: 15. 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: images/photo.jpg - warning
missing-refreference to a missing file: /Users/bruce/photo.jpg
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: images/photo.jpg, /Users/bruce/photo.jpg
- 0Tools and files. 2 referenced file(s) missing: images/photo.jpg, /Users/bruce/photo.jpg
- 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. 3 mutating operations with no state check
- 100Steps. 54 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1377 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)
- +3Description length 53: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- -4Absolute local paths (C:\Users, /home/…): not portable
- -2localhost URLs: will not work for another user
- -217 emoji in the instructions: noise for the model
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Structure: 24 headings
- +3Step-by-step instructions: 54 items
- +4Has examples (20 code blocks)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.
External checks
ClawHub: suspicious
The skill mostly matches its WeChat article publishing purpose, but it needs review because it stores and reads WeChat publishing credentials and personal profile data in unsafe, under-scoped ways.
LLM: suspicious (high) · VirusTotal: · 29 May 2026