BB seo-blog-writer
Fully automated SEO article writer. Give it a topic and domain — it handles everything: auto-discovers product context, researches keywords, analyzes competitors, writes the article, verifies links, and delivers a complete publication package (article + QA report + schema markup + promotion checklist). One confirmation gate before writing starts, then hands-off execution. Works for any site, any industry, any CMS. No hardcoded dependencies.
As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, execution cost, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 13022 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "triggers" - note
frontmatter-keyunknown frontmatter key "external_access" - note
frontmatter-keyunknown frontmatter key "permissions"
Process rating: all ten parameters 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 13022 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (read, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 102 steps
- 100Failures and branches. 11 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- low 17 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
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +1No license
- +2Single-language instructions
- +3Description length 444: enough signal without eating the budget
- +4Structure: 49 headings
- +3Step-by-step instructions: 102 items
- +3Output format is stated explicitly
- +4Has examples (73 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.