CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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," "templated landing pages," or "which CMS for pSEO." 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.

69

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

78%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: concise tables and checklists, a coherent assessment-to-launch-to-monitoring workflow, and clean two-file progressive disclosure with verified references. Weaker spots are the absence of any example output (title/meta template, schema markup sample) and of explicit error-recovery loops after the pre-launch checklist and during post-launch monitoring.

Suggestions

Add one compact example of the promised outputs in the Output Format section — e.g., a filled title/meta template ('{Keyword} in {City}: 12 Top Options for 2026') and a sample schema markup block — so Claude has copy-paste-ready models rather than just category labels.

Add a short feedback loop to Quality Checks: what to do when a pre-launch checklist item fails, and which remediation actions follow each post-launch warning (e.g., noindex thin pages on 'thin content warnings', consolidate pages on cannibalization).

Merge or differentiate 'Initial Assessment' and 'Task-Specific Questions', which ask overlapping things (target audience, search patterns, data, technical stack), to trim redundant tokens.

DimensionReasoningScore

Conciseness

The body is dense and efficient — tables, checklists, and one-line principles like 'Use subfolders, not subdomains' with good/bad URL examples, and no time is spent explaining SEO basics Claude already knows. Minor trimming is possible (the 'Initial Assessment' questions and 'Task-Specific Questions' sections overlap, and single-line principles like 'Quality Over Quantity: Better to have 100 great pages than 10,000 thin ones' pad slightly), which keeps it below the lean 5 anchor but above 'some unnecessary explanation'.

4 / 5

Actionability

Mostly concrete, actionable guidance for an instruction-only strategy skill: specific URL examples ('yoursite.com/templates/resume/'), a playbook-selection decision table, a 6-step implementation framework, and a checkbox pre-launch checklist with specific items ('Unique titles and meta descriptions', 'No conflicting noindex'). Minor gaps keep it from 5: no example of the promised outputs (a title/meta template, a schema markup snippet, or a sample strategy document), and steps like 'Validate demand: Aggregate search volume' give no method or tool.

4 / 5

Workflow Clarity

A clear end-to-end sequence — Initial Assessment → Core Principles → playbook selection → 6-step Implementation Framework → pre-launch Quality Checks → post-launch monitoring — with a checkbox checklist gating launch and post-launch monitoring ('Watch for: Thin content warnings, Ranking drops, Manual actions') acting as a feedback channel for this batch-style operation. It is not a 5 because there is no explicit fix-and-retry loop (e.g., what to do when a checklist item fails or rankings drop), only monitoring guidance.

4 / 5

Progressive Disclosure

The body is a well-organized overview that defers detail to two clearly signaled, one-level-deep references — 'For detailed playbook implementation: See [references/playbooks.md]' and 'Options and tradeoffs: [references/implementation-platforms.md]' — both of which exist as real files and contain no nested references. The inline 12-playbook table is an appropriate overview summary with detail split out; navigation is easy and nothing that belongs in a reference is inlined.

5 / 5

Total

17

/

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 description with explicit what/when structure, excellent trigger-term coverage including synonyms ('pSEO', 'programmatic SEO'), and explicit boundary pointers to sibling skills. The only weakness is that it names a single capability (creating pages at scale) rather than enumerating the several sub-capabilities the skill body actually covers.

Suggestions

Enumerate 2-3 distinct capabilities in the description (e.g., 'choose a playbook, design page templates, plan internal linking and indexation') instead of restating 'create pages at scale' in many phrasings.

Trim redundant trigger phrasings that restate the same idea ('building many pages for SEO', 'generate 100 pages', 'pages at scale') to reduce description length without losing coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action — 'create SEO-driven pages at scale using templates and data' — but the rest of the text restates that single capability ('building many pages for SEO', 'generate 100 pages') rather than listing several distinct actions (e.g., keyword pattern research, template design, platform selection). This matches the 'names domain and 1-2 concrete actions, but not comprehensive' anchor, and is below the 'lists several specific actions' anchor.

3 / 5

Completeness

Explicitly answers both what ('create SEO-driven pages at scale using templates and data') and when ('When the user wants to... Also use when the user mentions... Use this whenever someone wants to create many similar pages'), with a long list of concrete trigger phrases. Matches the 'clearly and explicitly answers both what AND when with concrete trigger phrases' anchor; not a 4 because the when-clause is maximally explicit, not merely adequate.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage with synonyms and colloquial variants users would actually say: 'programmatic SEO', 'pSEO', 'template pages', 'location pages', 'directory pages', 'comparison pages', 'integration pages', 'data-driven pages', 'templated landing pages', 'generate 100 pages', and even a question phrasing ('which CMS for pSEO'). Clearly matches the top anchor; nothing common is missing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (programmatic page generation at scale) with distinct triggers, and explicit de-conflict pointers — 'For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy' — that route adjacent requests away. Minimal conflict risk; matches the top anchor.

5 / 5

Total

18

/

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

coreyhaines31/marketingskills

Path

skills/programmatic-seo/SKILL.md

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.