CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

programmatic-seo

When the user wants SEO pages at scale from templates and data, or asks whether a page set will rank or look thin: location, integration, comparison, directory, and '[X] for [Y]' pages, each useful rather than thin. For SEO audits, see seo-audit. For content planning, see content-strategy.

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/programmatic-seo/SKILL.md
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 well-structured overview skill with exemplary progressive disclosure and a clear sequenced framework with pre-launch and post-launch checkpoints. It is held back by generic SEO-knowledge padding in Core Principles and guidance that often tells Claude what to consider rather than exactly how to execute.

Suggestions

Cut or compress Core Principles items Claude already knows (search intent match, quality over quantity, avoid doorway pages/keyword stuffing) down to one line each, keeping only the skill-specific guidance like the data defensibility hierarchy and subfolder-over-subdomain rule.

Make the Implementation Framework steps executable rather than inquisitive: replace bullets like "Validate demand: aggregate search volume" with a concrete validation method (e.g., how to bucket pattern volume, what threshold justifies building a page set) and add a sample page template outline with title/meta patterns and schema types.

Add an explicit error-recovery loop to Post-Launch Monitoring, e.g., 'If indexation rate falls or thin-content warnings appear: noindex the thinnest variations, consolidate or enrich them, and resubmit the affected sitemap.'

DimensionReasoningScore

Conciseness

The body is structured and scannable, but Core Principles restates SEO knowledge Claude already has ("Pages must actually answer what people are searching for", "No doorway pages, no keyword stuffing"), and several sections could be tightened, matching the mostly-efficient anchor rather than the minor-trims anchor at 4.

3 / 5

Actionability

Concrete elements exist (playbook patterns with example queries, good/bad URL structures, the data defensibility hierarchy), but much of the guidance is consideration-level ("What search patterns exist?", "Track: Indexation rate, Rankings...") with no method for validating search demand, no schema markup examples, and no sample template outline, leaving key execution details missing.

3 / 5

Workflow Clarity

The six-step Implementation Framework gives a clear sequence, and the pre-launch checklist plus post-launch monitoring section supply most checkpoints; the gap versus 5 is the absence of explicit error-recovery loops (e.g., what to do when thin-content warnings or ranking drops appear).

4 / 5

Progressive Disclosure

The body is a genuine overview (a summary table of the 12 playbooks) with both detailed materials split into references/playbooks.md and references/implementation-platforms.md, which exist, are clearly signaled with context for when to load them, and are verifiably one level deep (they link only to external URLs, not further local files).

5 / 5

Total

15

/

20

Passed

Description

78%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 well-crafted description with explicit trigger guidance, distinctive page-type keywords, and good boundary routing to sibling skills. Its main weaknesses are the absent verb-level statement of what the skill does and the surprising omission of the term "programmatic SEO" itself.

DimensionReasoningScore

Specificity

Names the domain and several concrete scope elements ("SEO pages at scale from templates and data", "location, integration, comparison, directory, and '[X] for [Y]' pages", "rank or look thin"), but never states the skill's actions with explicit verbs like build or evaluate, leaving minor gaps versus comprehensive coverage.

4 / 5

Completeness

The "when" is explicit with concrete triggers ("When the user wants SEO pages at scale... or asks whether a page set will rank or look thin"), and the "what" is present but implied rather than stated as a capability, which matches the anchor where one half could be more explicit rather than the fully explicit 5.

4 / 5

Trigger Term Quality

Good natural keyword coverage ("SEO pages at scale", "[X] for [Y]", "look thin", page-type names), but it omits the phrase users most naturally say for this skill — "programmatic SEO" — plus synonyms like doorway or landing pages, so it falls short of the comprehensive anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinctive page-type triggers and explicit disambiguation to adjacent skills ("For SEO audits, see seo-audit. For content planning, see content-strategy."), minimizing the risk of triggering for the wrong skill.

5 / 5

Total

17

/

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.