AB blog-meta
Generate SEO-optimized title, SEO title, SEO description, SEO slug, and social tips for a blog post. Use when the user provides a blog name or slug to look up in ~/blogs, wants all meta fields generated using researched SEO best practices and current trends, and wants the result saved as JSON in ~/blog-meta.
As a process B 65/100 · Nearly there — weak spots: result and completion, consistency, 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: 5. 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 65/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (blog-meta) differs from the folder (re-blog-meta)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 30 steps
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 707 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 309: enough signal without eating the budget
- +4Structure: 5 headings
- +3Step-by-step instructions: 30 items
- +4Reference files are cited in the instructions (2 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.