ai-seo

When the user wants to build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production. Also use when the user mentions 'SEO,' 'programmatic SEO,' 'AI content,' 'competitor alternative pages,' 'AI Overviews,' 'search optimization,' 'DataForSEO,' 'content at scale,' 'keyword strategy,' or 'organic traffic.' This skill covers AI-powered SEO strategy from keyword research through programmatic page generation. Do NOT use for technical implementation, code review, or software architecture.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable SEO playbook with concrete commands, decision matrices, and templates, plus reasonable validation for batch page generation. Its main weaknesses are conciseness (conceptual padding and undated-sensitive pricing/year values) and the absence of any progressive disclosure — everything lives in one large inline file.

Suggestions

Move time-sensitive values (tool pricing, "2026" year-stamped examples, "Updated [Month] [Year]") into a dedicated versioned/deprecated section so stale figures do not bloat the evergreen guidance.

Split the large reference material — full tool-comparison tables, the page-template and content-brief templates, and the Examples/Troubleshooting blocks — into reference files under references/ and link to them one level deep from SKILL.md to improve progressive disclosure.

Trim Claude-known marketing rationale (e.g. the 'Why This Converts 3-5x Higher Than TOFU' explanation) down to the actionable conversion-rate data points that Claude cannot infer.

Dimension	Reasoning	Score
Conciseness	Mostly efficient reference material (tables, templates, MCP commands), but it includes conceptual padding Claude does not need ("Why This Converts 3-5x Higher Than TOFU" rationale) and time-sensitive values like "Pricing (2025)", "Mailchimp pricing 2026", and "Best CRM Software 2026" that are not isolated in a deprecated/old-patterns section — the guidelines penalize conciseness for exactly this.	3 / 5
Actionability	Highly actionable throughout: copy-paste bash such as "claude mcp add dataforseo --transport sse ...", concrete decision thresholds ("DR > 40 --> Surfer SEO"), real tool names, prioritized content calendar (P0-P4), and explicit page/brief templates cover the common cases.	5 / 5
Workflow Clarity	Clear numbered sequences (Before Starting, Acquisition Playbook, keyword research Steps 1-4, monthly iteration cycle) with validation for the batch operation (uniqueness > 70%/page, 10% manual review, GSC indexing check after 48 hours), but the AirOps generation workflow states "Quality: Uniqueness score > 70%" then publishes without an explicit validate->fix->retry loop, leaving a minor checkpoint gap.	4 / 5
Progressive Disclosure	No bundle files exist and the body is a single ~460-line monolith with good headers but zero references to separate files; detailed reference material that would benefit from splitting (full tool comparison, page/brief templates, examples) is fully inlined rather than disclosed one level deep.	3 / 5
	Total	15 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-structured description: concrete capabilities, exhaustive natural trigger terms, explicit use-when guidance, and a clear negative boundary to avoid misfires. Voice is correctly third person ("the user"), so no specificity penalty applies.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "build programmatic SEO with AI", "create competitor alternative pages", "optimize for AI Overviews", "scale content production" plus "from keyword research through programmatic page generation" — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what (AI-powered SEO strategy, keyword research through programmatic page generation) and when ("Also use when the user mentions...") with concrete trigger phrases, so it clears the explicit-trigger bar rather than capping at 3.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and specific products: "SEO", "programmatic SEO", "AI content", "competitor alternative pages", "AI Overviews", "search optimization", "DataForSEO", "content at scale", "keyword strategy", "organic traffic" — all phrases a user would naturally say.	5 / 5
Distinctiveness Conflict Risk	Clear niche (AI-powered programmatic SEO) with distinct triggers and an explicit negative boundary ("Do NOT use for technical implementation, code review, or software architecture") that minimizes overlap with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: tech-leads-club/agent-skills
Path: packages/skills-catalog/skills/(gtm)/ai-seo/SKILL.md
Commit: fe318be

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.