programmatic-seo

When the user wants to create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/programmatic-seo/SKILL.md

Quality

Content

53%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 well-structured strategy skill with good progressive disclosure and a sound high-level workflow, but it leans conceptual over executable and lacks explicit validation feedback loops in its batch-generation workflow. Some restated SEO basics and a duplicated table trim conciseness and organization slightly.

Suggestions

Add an explicit validation checkpoint to the Implementation Framework (e.g., generate a small pilot batch -> check indexation/thin-content signals -> fix template -> regenerate) to support the batch nature of the work.

Trim well-known SEO explanations (subfolders vs subdomains, doorway pages, keyword stuffing) to brief reminders, since Claude already knows these concepts.

Remove the duplicated "Choosing Your Playbook" table from either SKILL.md or playbooks.md so the overview stays a true pointer and the reference holds the detail.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with well-chosen tables and bullets, but it restates SEO concepts Claude already knows (subfolders vs subdomains, doorway pages, "better 100 great pages than 10,000 thin ones") and could be tightened.	3 / 5
Actionability	Offers some concrete guidance (URL patterns like `/templates/[type]/`, playbook pattern tables), but much of the body is strategic questions, principles, and checklists rather than specific executable steps.	3 / 5
Workflow Clarity	The 5-step Implementation Framework is sequenced and backed by a pre-launch checklist and post-launch monitoring, but generating pages at scale is a batch operation and the workflow lacks explicit validate->fix->retry checkpoints between steps, capping this at 3.	3 / 5
Progressive Disclosure	The body is an overview that routes detail to a clearly signaled, one-level-deep reference (references/playbooks.md, verified present), with content appropriately split; minor deduction for the "Choosing Your Playbook" table being duplicated in both the body and the reference.	4 / 5
	Total	13 / 20 Passed

Description

90%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, trigger-rich description that clearly answers both what and when while distinguishing itself from neighboring skills. The only weak spot is specificity, which restates one core action rather than listing several distinct concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain and a couple of concrete actions ("create SEO-driven pages at scale using templates and data", "create many similar pages targeting different keywords or locations"), but does not enumerate multiple distinct actions as the top anchor requires.	3 / 5
Completeness	Explicitly states both what (create SEO-driven pages at scale via templates and data) and when, with concrete "Use when the user mentions..." / "Also use when..." trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including synonyms and shorthand ("programmatic SEO", "pSEO", "template pages", "pages at scale", "[keyword] + [city] pages", "generate 100 pages", "templated landing pages") that users would naturally say.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche with distinct triggers and explicitly routes adjacent intents away ("For auditing existing SEO issues, see seo-audit", "For content strategy planning, see content-strategy"), minimizing conflict risk.	5 / 5
	Total	18 / 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: coreyhaines31/marketingskills
Path: skills/programmatic-seo/SKILL.md
Commit: c6ea128

Reviewed: 2 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.