AB seo-agi
Write SEO pages that rank in Google AND get cited by LLMs (ChatGPT, Perplexity, Claude). Use when creating airport parking pages, local service pages, listicles, comparison pages, pricing pages, or any content that must pass the Reddit Test -- meaning a knowledgeable practitioner would upvote it, not call it AI slop. Enforces information gain, 500-token chunk architecture, real HTML tables, verification tags, and honest "Not For You" sections. Triggers on: "write an SEO page", "seo-agi", "seo agi", "seo page for [keyword]", "create a landing page", "rank for [keyword]", "rewrite this page for SEO", "optimize this content", "GEO", "AEO", "generative engine optimization", "seo-agi", "write a page that ranks". Do NOT trigger for pure technical SEO audits (crawl errors, robots.txt, sitemap validation).
Write SEO pages that rank in Google AND get cited by LLMs (ChatGPT, Perplexity, Claude).
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
How to improve
- 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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Exfiltration
read-dotenvREADME.md:235Reads a .env file (documentation of a security skill)cp ~/.claude/skills/seo-agi/.env.example ~/.config/seo-agi/.env
security skill -
low Exfiltration
read-dotenvREADME.md:286Reads a .env file (documentation of a security skill)cat ~/.config/seo-agi/.env 2>/dev/null || echo "No .env file -- skill will use fallback mode"
security skill
Files scanned: 19. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 6197 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 4 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70Execution cost. Instruction body is 6197 tokens
- 85Steps. 122 steps, 1 vague phrases
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 19 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (3 tags): a typed call is more reliable
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
- +3Description length 809: 120–800 characters recommended
- -31 of 3 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 56 headings
- +3Step-by-step instructions: 122 items
- +3Output format is stated explicitly
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.