AF seo-audit
When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," or "SEO health check." For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema-markup.
When the user wants to audit, review, or diagnose SEO issues on their site.
As a process F 46/100 · Will not run — References files that are not bundled: references/ai-writing-detection.md, references/aeo-geo-patterns.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
- warning
missing-refreference to a missing file: references/ai-writing-detection.md - warning
missing-refreference to a missing file: references/aeo-geo-patterns.md
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: references/ai-writing-detection.md, references/aeo-geo-patterns.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (seo-audit) differs from the folder (cs-seo-audit)
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 58 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Execution cost. Instruction body is 1406 tokens
- 100Running it twice. Mutating operations check current state
- low 10 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)
- +4No input/output examples
- -31 of 1 scripts are never mentioned in SKILL.md
- +2Single-language instructions
- +5Description quotes 7 example trigger phrases
- +3Description length 350: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 58 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.