AD seo-autopilot
Fully automated SEO content freshness engine. Monitors a keyword research reports directory, automatically generates landing pages and blog posts, runs SEO audits, and pushes updates. Use when: you need to keep SEO content fresh without manual publishing, you want to automate the flow from keyword research to live pages, or you need a pipeline that converts keyword reports into deployed web pages. Works with Next.js, Astro, Nuxt, and static site frameworks. Trigger phrases: "automate SEO content", "keyword report to page", "auto-generate SEO pages", "content freshness engine", "deploy SEO pages automatically"
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, failures and branches
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: 4. 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 46/100
- 0Result and completion. Does not say what the result is
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 22 mutating operations with no state check
- 40Consistency. Frontmatter name (seo-autopilot) differs from the folder (seo-autopilot-pro)
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 35 steps
- 100Execution cost. Instruction body is 1324 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
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 616: enough signal without eating the budget
- +4Structure: 26 headings
- +3Step-by-step instructions: 35 items
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 85.