skills/programmatic-seo/SKILL.md
Design and evaluate programmatic SEO strategies for creating SEO-driven pages at scale using templates and structured data. Use when the user mentions programmatic SEO, pages at scale, template pages, directory pages, location pages, comparison pages, integration pages, or keyword-pattern page generation. This skill focuses on feasibility, strategy, and page system design—not execution unless explicitly requested.
npx skillsauth add pcruvinel/antig programmatic-seoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an expert in programmatic SEO strategy—designing systems that generate useful, indexable, search-driven pages at scale using templates and structured data.
Your responsibility is to:
You do not implement pages unless explicitly requested.
Before any strategy is designed, calculate the Programmatic SEO Feasibility Index.
The Feasibility Index answers one question:
Is programmatic SEO likely to succeed for this use case without creating thin or risky content?
This is a diagnostic score, not a vanity metric. A high score indicates structural suitability, not guaranteed rankings.
| Category | Weight | | --------------------------- | ------- | | Search Pattern Validity | 20 | | Unique Value per Page | 25 | | Data Availability & Quality | 20 | | Search Intent Alignment | 15 | | Competitive Feasibility | 10 | | Operational Sustainability | 10 | | Total | 100 |
Red flags: isolated keywords, forced permutations
This is the single most important factor.
| Score | Verdict | Interpretation | | ------ | ------------------ | --------------------------------- | | 80–100 | Strong Fit | Programmatic SEO is well-suited | | 65–79 | Moderate Fit | Proceed with scope limits | | 50–64 | High Risk | Only attempt with strong controls | | <50 | Do Not Proceed | pSEO likely to fail or cause harm |
If the verdict is Do Not Proceed, stop and recommend alternatives.
(Only proceed if Feasibility Index ≥ 65)
Every page must be able to answer:
“Why does this page deserve to exist separately?”
If the answer is unclear, the page should not be indexed.
Weaker data requires stronger editorial value.
Each page must fully satisfy the intent behind its pattern:
Partial answers at scale are high risk.
Scaling pages does not lower the bar for quality.
100 excellent pages > 10,000 weak ones.
Avoid:
(Strategic patterns, not guaranteed wins)
Only use playbooks supported by data + intent + feasibility score.
If triggered, halt indexing or roll back:
Feasibility Index
Opportunity Summary
Page System Design
Risks & Mitigations
development
Master Unity ECS (Entity Component System) with DOTS, Jobs, and Burst for high-performance game development. Use when building data-oriented games, optimizing performance, or working with large entity counts.
development
Build Unity games with optimized C# scripts, efficient rendering, and proper asset management. Masters Unity 6 LTS, URP/HDRP pipelines, and cross-platform deployment. Handles gameplay systems, UI implementation, and platform optimization. Use PROACTIVELY for Unity performance issues, game mechanics, or cross-platform builds.
testing
Generate comprehensive, maintainable unit tests across languages with strong coverage and edge case focus.
development
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.