AB youmind-wordpress-article
Write and publish WordPress articles end-to-end with AI — topic mining via YouMind knowledge base, de-AI voice writing, Markdown-to-HTML conversion, featured image upload, and one-click publishing. Use when user wants to "wordpress article", "publish to wordpress", "wp article", "wp post", "WordPress 文章", "发布到 WordPress". Do NOT trigger for: WeChat articles, Ghost posts, emails/newsletters, PPT, short video scripts.
Write and publish WordPress articles end-to-end with AI — topic mining via YouMind knowledge base, de-AI voice writing, Markdown-to-HTML conversion, featured…
As a process B 69/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
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: 24. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "triggers" - note
edit-residuethe text marks something as outdated (lines 174, 184, 187): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 69/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 18 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2721 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 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 6 example trigger phrases
- +3Description length 419: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 26 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.