AB youmind-beehiiv-article
Write and publish Beehiiv posts with AI — topic research via YouMind knowledge base, newsletter-publication writing, Markdown-to-HTML conversion, and publishing through the Beehiiv account already connected in YouMind. Use when user wants to "write Beehiiv article", "publish to Beehiiv", "Beehiiv post", "Beehiiv newsletter", "写 Beehiiv 文章", "发布到 Beehiiv".
Write and publish Beehiiv posts with AI — topic research via YouMind knowledge base, newsletter-publication writing, Markdown-to-HTML conversion, and…
As a process B 74/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 116, 119): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 74/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 23 mutating operations with no state check
- 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. 27 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2522 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
- +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 357: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 27 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.