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.
86
80%
Does it follow best practices?
Impact
97%
1.19xAverage score across 3 eval scenarios
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/programmatic-seo/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at trigger term coverage and completeness, with extensive natural keywords users would say and clear 'when to use' guidance including helpful cross-references to related skills. The main weakness is the lack of specific concrete actions describing what the skill actually does beyond 'create pages' - it focuses heavily on when to trigger but less on the specific capabilities.
Suggestions
Add 2-3 specific concrete actions at the beginning, such as 'Generates templated landing pages, populates data-driven content, creates URL structures, and optimizes meta tags for programmatic SEO.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (SEO-driven pages, templates, data) and mentions some actions like 'create' pages at scale, but lacks specific concrete actions like 'generate templates', 'populate data fields', or 'optimize meta tags'. The 'what it does' is implied rather than explicitly listed. | 2 / 3 |
Completeness | Clearly answers both 'what' (create SEO-driven pages at scale using templates and data) and 'when' (explicit 'Use when' clause with extensive trigger terms). Also helpfully distinguishes from related skills (seo-audit, content-strategy) to clarify scope. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'programmatic SEO', 'pSEO', 'template pages', 'pages at scale', 'directory pages', 'location pages', '[keyword] + [city] pages', 'comparison pages', 'integration pages', 'generate 100 pages', 'data-driven pages', 'templated landing pages'. These are highly specific and match real user vocabulary. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (programmatic SEO/templated pages at scale). Explicitly differentiates from related skills (seo-audit, content-strategy), reducing conflict risk. The specific trigger terms like 'pSEO', '[keyword] + [city] pages' are unique identifiers. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a comprehensive strategic framework for programmatic SEO with good workflow structure and appropriate content organization. However, it leans toward describing concepts rather than providing executable, copy-paste-ready examples. The content assumes less of Claude's baseline knowledge than necessary, explaining SEO fundamentals that don't need explanation.
Suggestions
Add concrete, executable examples: actual URL patterns, title tag templates with variables (e.g., '{service} in {city} | {brand}'), and sample meta description formulas
Remove explanatory content Claude already knows (e.g., why subfolders consolidate domain authority, what thin content is) and replace with specific implementation patterns
Include a concrete template example showing actual HTML/markdown structure with placeholder variables rather than just describing what templates should contain
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary explanation (e.g., explaining what subdomains vs subfolders do, basic SEO concepts Claude would know). The 12 playbooks table and implementation framework could be tighter. | 2 / 3 |
Actionability | Provides structured guidance and checklists but lacks concrete, executable examples. No code snippets, no specific template examples, no actual URL patterns or meta description templates that could be copy-pasted. Mostly describes what to do rather than showing how. | 2 / 3 |
Workflow Clarity | Clear multi-step implementation framework (Research → Data → Template → Linking → Indexation) with explicit pre-launch and post-launch checklists. The workflow is well-sequenced with validation checkpoints built into the checklists. | 3 / 3 |
Progressive Disclosure | Good structure with overview in main file and reference to detailed playbooks in separate file. Clear navigation to related skills. Content is appropriately split between overview and detailed implementation guidance. | 3 / 3 |
Total | 10 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- coreyhaines31/marketingskills
- Commit
9d4d29a
- 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.