BD jike-wechat-writer
微信公众号文章创作技能，覆盖从选题挖掘到排版发布的全流程。当用户表达任何文章创作意图时都应激活——包括但不限于"写一篇文章"、"帮我写篇推文"、"公众号内容创作"、"帮我出一篇稿"、"这个选题怎么写"、"把这些素材整理成文章"、"写个公众号推送"、"帮我出个内容"、"围绕XX写点东西"等。即使用户只是给了一堆链接或素材然后说"帮我整理一下"，只要上下文暗示了创作需求，也应触发。当用户提到热点借势、选题挖掘、风格模仿、文章排版等公众号创作子环节时同样适用。未指定目标平台时，默认以微信公众号作为输出平台。此技能提供公众号创作各环节的核心指导模块，由 agent 根据上下文灵活编排。
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
net-redirectable-api-keyscripts/writer.py:63Helper sends the API key to a host configured by an environment variable — the key can be redirected to another serverAPI key + configurable base URL from environment
Files scanned: 15. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Unexpected scalar at node end at line 4, column 71: …挖掘到排版发布的全流程。当用户表达任何文章创作意图时都应激活——包括但不限于"写一篇文章"、"帮我写篇推文"、"公众号内容创作"、"帮我出一篇稿"、"这个选… ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
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
- 60Tools and files. Uses tools (web, python) that frontmatter does not declare
- 100Steps. 13 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 920 tokens
- 100Running it twice. No mutating operations
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
- +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
- +5Description quotes 9 example trigger phrases
- +3Description length 292: enough signal without eating the budget
- +4Structure: 7 headings
- +3Step-by-step instructions: 13 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +3All 2 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.