CtrlK
BlogDocsLog inGet started
Tessl Logo

programmatic-seo-spy

Reverse-engineer how competitors do programmatic SEO. Detects URL pattern clusters (vs/, integrations/, for-{industry}/), estimates page count per pattern, analyzes template quality, infers which patterns actually drive traffic, and identifies gaps you can exploit. Outputs a competitive pSEO landscape report.

57

Quality

66%

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/seo/composites/programmatic-seo-spy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The body is a well-structured, actionable multi-phase workflow with concrete commands and templates, but it carries some redundancy and lacks explicit validation checkpoints for a batch crawling operation. Progressive disclosure is solid given the absence of bundle files.

Suggestions

Add explicit validation checkpoints after the sitemap crawl and pattern detection (e.g., 'verify URL count is non-empty and patterns cover expected categories before proceeding').

Remove the redundant 'Trigger Phrases' section that duplicates the 'When to Use' list, or merge them.

Tighten the quoted 'Agent Prompt to User' block, which is verbose for an inline skill body.

DimensionReasoningScore

Conciseness

Mostly substantive but includes redundancy — the 'Trigger Phrases' section duplicates 'When to Use', and the quoted agent-prompt-to-user block is padded — so it could be tightened.

3 / 5

Actionability

Provides concrete executable commands (catalog_content.py invocation, DataForSEO POST example), specific regex pattern tables, and a copy-paste output template, with only minor gaps.

4 / 5

Workflow Clarity

Phases 0-6 are clearly sequenced, but this batch crawling/analysis workflow lacks explicit validation checkpoints verifying crawl output or pattern detection, capping workflow clarity at 3.

3 / 5

Progressive Disclosure

Well-organized with clear section headers and a logical phase structure; no bundle files exist so all content is inline, but the structure keeps it navigable with only minor organization gaps.

4 / 5

Total

14

/

20

Passed

Description

71%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.

The description is specific and action-rich with strong trigger keywords, but it omits an explicit 'Use when' guidance clause, leaving the invocation conditions only implied. Distinctiveness is good with minor overlap risk against related SEO skills.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when analyzing competitors' programmatic SEO, finding pSEO gaps, or reverse-engineering competitor URL structures').

Include a few more natural user phrasings such as 'comparison pages' or 'competitor SEO pages' alongside 'programmatic SEO'/'pSEO'.

Clarify the boundary versus the referenced programmatic-seo-planner skill to reduce overlap ambiguity.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Detects URL pattern clusters', 'estimates page count per pattern', 'analyzes template quality', 'infers which patterns actually drive traffic', 'identifies gaps', 'Outputs a competitive pSEO landscape report' — giving comprehensive coverage.

5 / 5

Completeness

The 'what' is clearly and comprehensively answered, but there is no explicit 'Use when...' trigger clause; the 'when' is only weakly implied, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Good natural keyword coverage including synonyms ('programmatic SEO', 'pSEO', 'competitors', 'URL pattern clusters'), though a few common user phrasings like 'competitor SEO pages' or 'comparison pages' are absent.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (reverse-engineering competitor programmatic SEO) with distinct triggers, but has minor overlap risk with adjacent SEO/planner skills referenced in the body.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.