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.
83
Quality
80%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./config/claude/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 is a strong description with excellent trigger term coverage and clear completeness. The explicit 'Use when' clause with comprehensive trigger terms makes skill selection straightforward. The main weakness is that the 'what' portion could be more specific about concrete actions beyond 'create pages at scale'.
Suggestions
Add 2-3 specific concrete actions to the opening clause, e.g., 'create SEO-driven pages at scale by generating templates, populating data variables, and structuring URLs'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (SEO-driven pages, templates, data) and mentions some actions (create pages at scale), but lacks specific concrete actions like 'generate meta tags', 'create URL structures', or 'populate template variables'. | 2 / 3 |
Completeness | Clearly answers both what ('create SEO-driven pages at scale using templates and data') and when ('Use when the user mentions...' with explicit trigger list). Also helpfully distinguishes from related skill (seo-audit) for boundary clarity. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'programmatic SEO', 'template pages', 'pages at scale', 'directory pages', 'location pages', '[keyword] + [city] pages', 'comparison pages', 'integration pages'. These are exactly what users searching for this capability would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Very distinct niche with specific triggers like 'programmatic SEO', '[keyword] + [city] pages'. The explicit callout to use seo-audit for auditing further reduces conflict risk with related skills. | 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 well-organized strategic framework for programmatic SEO with clear workflows and good progressive disclosure. However, it lacks concrete, executable examples—no actual template code, URL patterns with real syntax, or sample data structures. The content explains concepts Claude likely already understands (what thin content is, basic SEO principles) rather than providing the specific, actionable implementation details that would make this immediately useful.
Suggestions
Add concrete template examples with actual code (e.g., a Next.js dynamic route, a sample data schema, or actual meta tag templates with variable syntax)
Remove explanatory content about basic SEO concepts (thin content, keyword stuffing) that Claude already knows—focus on the specific implementation patterns
Include a real example of one playbook implementation end-to-end (e.g., actual URL structure, title template, and sample page content for a location-based page)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation (e.g., explaining what programmatic SEO is, listing obvious mistakes Claude would know to avoid). The tables and checklists are well-structured but some sections could be tightened. | 2 / 3 |
Actionability | Provides good frameworks and checklists but lacks concrete, executable examples. No actual code snippets, template examples, or copy-paste ready content. The guidance is structured but remains at the conceptual level rather than providing specific implementations. | 2 / 3 |
Workflow Clarity | Clear 5-step implementation framework with logical sequencing. Pre-launch and post-launch checklists provide explicit validation checkpoints. The workflow from research through monitoring is well-defined with clear phases. | 3 / 3 |
Progressive Disclosure | Excellent structure with overview tables pointing to detailed playbooks in references/playbooks.md. Content is appropriately split between high-level strategy in the main file and detailed implementation in referenced files. Clear navigation with related skills section. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- freekmurze/dotfiles
- Commit
355d067
- 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.