CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

63%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 knowledge-rich, well-structured strategy skill with concrete thresholds, templates, commands, and validation loops for batch content operations. Its main weaknesses are a monolithic single-file layout with no progressive disclosure, time-sensitive pricing data embedded in the main body, and some intake-question redundancy.

Suggestions

Split stable reference material (tool comparison/MCP tables, GEO audit checklist, page-template structures) into one-level-deep files under references/ (e.g., references/tool-stack.md, references/geo-checklist.md) and point to them from a leaner SKILL.md overview.

Move 2025 pricing figures and dated examples into a dated reference section or file so time-sensitive data doesn't age the main workflow body, and trim the ASCII diagrams in favor of brief inline lists.

Deduplicate the intake questions — merge 'Before Starting' and 'Questions to Ask' into one checklist to remove ~20 lines of repeated content.

DimensionReasoningScore

Conciseness

The body is dense and mostly non-redundant domain knowledge (tool capabilities, keyword patterns, GEO checklists) that Claude does not inherently know, but it carries avoidable weight: time-sensitive pricing tables ("Pricing (2025)," "$99-219/mo," "Mailchimp pricing 2026") not placed in a dated/deprecated section, ASCII diagrams that add length over clarity, and duplicated intake questions ("Before Starting" items overlap the "Questions to Ask" section). This fits the score-3 anchor ("mostly efficient but includes some unnecessary explanation or could be tightened") better than 4, which requires only minor trimming.

3 / 5

Actionability

Guidance is highly concrete for an instruction-only skill: copy-paste MCP setup commands ("claude mcp add dataforseo --transport sse ..."), a fill-in content brief template, a complete page-template skeleton, numeric thresholds ("volume > 200, KD < 40"), and a P0-P4 prioritization matrix. It sits below the score-5 anchor because several steps remain high-level directives ("create related programmatic pages," "Generate content briefs using Frase or Surfer") without the specific steps to execute them, matching score 4 ("concrete code or commands with minor gaps").

4 / 5

Workflow Clarity

Sequencing is clear via numbered sections and explicit step lists (4-step keyword research workflow, 6-step agent workflow, monthly iteration cycle), and validation/feedback for the batch page-generation operation is present (uniqueness > 70%, 10% manual review sample, GSC index monitoring, troubleshooting cause→fix pairs, resubmit via IndexNow). It falls short of anchor 5 because the end-to-end ordering across the eight sections is implicit — no single ordered engagement flow ties stack selection, keyword research, page generation, and measurement together — leaving minor checkpoint gaps characteristic of score 4.

4 / 5

Progressive Disclosure

No references/, scripts/, or assets/ bundle directories exist, and everything — tool comparison tables, the full GEO audit checklist, page templates, budget stacks — is inlined in a single ~460-line SKILL.md with no pointers to detail files. Section headers and a Quick Reference give it real structure (so not the score-2 "minimal structure" anchor), but content that clearly belongs in separate reference files is inlined, which is exactly the score-3 anchor ("some structure... content that should be separate is inline").

3 / 5

Total

14

/

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.

The description is a strong exemplar: concrete capabilities, natural and varied trigger terms, explicit what/when guidance, and clear negative boundaries. Third-person voice is maintained and it stays concise despite covering a broad skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — "build programmatic SEO with AI, create competitor alternative pages, optimize for AI Overviews, or scale content production" plus "from keyword research through programmatic page generation" — matching the comprehensive-coverage anchor. It is not below 5 because no capability area of the skill is left unmentioned at the summary level, and not a vague or partial list like the score-4 example.

5 / 5

Completeness

It explicitly answers "what" ("This skill covers AI-powered SEO strategy from keyword research through programmatic page generation") and "when" with two explicit trigger clauses ("When the user wants to build..." and "Also use when the user mentions..."). It also adds boundary guidance ("Do NOT use for technical implementation..."), going beyond the score-5 anchor's requirements; a missing when-clause would cap it at 3, but that cap does not apply.

5 / 5

Trigger Term Quality

Trigger terms are comprehensive and natural: "SEO," "programmatic SEO," "AI content," "competitor alternative pages," "AI Overviews," "search optimization," "DataForSEO," "content at scale," "keyword strategy," "organic traffic" — covering synonyms and phrasings users would actually say. It exceeds the score-4 anchor ("a few natural terms missing") since both casual ("SEO") and specific ("DataForSEO") variations are present.

5 / 5

Distinctiveness Conflict Risk

The SEO/GEO niche is clearly staked out with distinct triggers ("AI Overviews," "DataForSEO," "competitor alternative pages") and an explicit exclusion clause ("Do NOT use for technical implementation, code review, or software architecture") that reduces overlap with adjacent content or engineering skills. Minor overlap with generic content-marketing skills keeps it from being conflict-free, but the anchor for 5 ("clear niche with distinct triggers; minimal conflict risk") is the best fit.

5 / 5

Total

20

/

20

Passed

Validation

100%

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
Reviewed

Table of Contents

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.