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," or "building many pages for SEO." For auditing existing SEO issues, see seo-audit.

Quality

78%

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 ./config/claude/skills/programmatic-seo/SKILL.md

The canonical home for this skill is programmatic-seo in coreyhaines31/marketingskills

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, instruction-only skill with strong progressive disclosure and a sensible workflow sequence. Its weaknesses are verbosity from playbook-table/reference overlap and guiding-question style steps without an explicit validation feedback loop for batch generation.

Suggestions

Collapse the 12-playbook overview table to a brief pointer to references/playbooks.md to remove duplication and tighten conciseness.

Convert the Implementation Framework's guiding questions into concrete, ordered actions with a validate-before-launch checkpoint (e.g., run the pre-launch checklist, fix failures, re-check) to support a feedback loop and lift workflow_clarity.

Trim self-evident SEO rules (doorway pages, keyword stuffing, subfolders-not-subdomains) to the non-obvious recommendations only.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and well-structured, but the 12-playbook overview table overlaps with references/playbooks.md and several items restate basic SEO knowledge Claude already has ("No doorway pages," "No keyword stuffing," "subfolders not subdomains"), so it is not the lean every-token-earns-its-place anchor at 3.	2 / 3
Actionability	Provides concrete specifics (URL patterns like `yoursite.com/templates/resume/`, playbook patterns with examples, pre-launch checklists), but the Implementation Framework steps are framed as guiding questions ("What's the repeating structure?", "What data populates each page?") rather than copy-paste-ready instructions, matching the some-concrete-but-incomplete anchor.	2 / 3
Workflow Clarity	There is a clear sequence (Assessment → Core Principles → Choose Playbook → Implementation Framework 1–5 → Quality Checks) and a pre-launch checklist, but programmatic page generation is a batch operation with no explicit validate→fix→retry feedback loop, which per the rubric caps this dimension at 2.	2 / 3
Progressive Disclosure	The body keeps a concise overview and pushes detail to a single, clearly signaled one-level-deep reference ("See [references/playbooks.md](references/playbooks.md)") that exists in the bundle, with well-organized sections — matching the clear-overview-with-well-signaled-references anchor.	3 / 3
	Total	9 / 12 Passed

Description

100%

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: concrete action, comprehensive natural trigger terms, explicit what-and-when guidance, and a clear redirect that distinguishes it from the related seo-audit skill. Third-person/trigger-clause phrasing matches the accepted good-example pattern.

Dimension	Reasoning	Score
Specificity	Lists a concrete primary action ("create SEO-driven pages at scale using templates and data") and enumerates multiple specific page categories (templates, directory, location, comparison, integration), matching the multiple-concrete-actions anchor rather than the single-domain anchor at 2.	3 / 3
Completeness	Explicitly answers what (create SEO-driven pages at scale using templates and data) and when ("Also use when the user mentions...") with an explicit trigger clause, satisfying the both-what-and-when anchor; it is not the 2 anchor where 'when' is only implied.	3 / 3
Trigger Term Quality	Covers many natural terms a user would say — "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO" — well beyond the partial-coverage anchor at 2.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (programmatic/at-scale template SEO) with distinct triggers and an explicit handoff ("For auditing existing SEO issues, see seo-audit"), making conflicts unlikely — not the generic anchor at 2.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: freekmurze/dotfiles
Path: config/claude/skills/programmatic-seo/SKILL.md
Commit: d0073bc

Reviewed: about 10 hours 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.