AA youmind-devto-article
Write and publish Dev.to articles with AI — topic research via YouMind knowledge base, developer-audience adapted writing, Markdown with front matter formatting, and one-click publishing. Use when user wants to "write Dev.to article", "publish to Dev.to", "post on Dev.to".
Write and publish Dev.to articles with AI — topic research via YouMind knowledge base, developer-audience adapted writing, Markdown with front matter…
As a process A 80/100 · Runs to the end — weak spots: result and completion, running it twice
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 106, 116, 119, 231): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 80/100
- 0Result and completion. Does not say what the result is
- 30Running it twice. 26 mutating operations with no state check
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 39 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3136 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
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 3 example trigger phrases
- +3Description length 273: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 39 items
- +4Has examples (2 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.