AD publish-to-wechat
Use when the user says "share it to WeChat", "send this to WeChat", "make it a web page", "give me a link" or "who read it", or finishes a report, proposal, notes, guide or deck for others. Publishes to LivePage: a page that opens in WeChat, keeps the same link across updates, and shows who read how far plus feedback. 用户说「发到微信」「分享到微信」「发成网页」「生成个链接」「谁看了」，或做完周报、方案、纪要、攻略、演示稿要发给别人看时使用：发成链接不变、可反复更新的网页，微信里点开就能看，读回谁看了、看到哪、反馈。 用戶說「發到微信」「分享到微信」「發成網頁」「產生一個連結」「誰看了」，或做完週報、方案、紀要、攻略、簡報要發給別人看時使用：發成連結不變、可反覆更新的網頁，微信裡點開就能看，讀回誰看了、看到哪、回饋。
Use when the user says "share it to WeChat", "send this to WeChat", "make it a web page", "give me a link" or "who read it", or finishes a report, proposal…
As a process D 48/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 48/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
- 30Running it twice. 40 mutating operations with no state check
- 60Tools and files. Uses tools (web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4617 tokens
- 100Steps. 83 steps
- 100Consistency. Name and required fields are in place
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (10 tags): a typed call is more reliable
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
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 523: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 83 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.