CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-cannibalization-detector

Analyzes multiple provided pages to identify keyword overlap and potential cannibalization issues. Suggests differentiation strategies. Use PROACTIVELY when reviewing similar content.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/seo-cannibalization-detector/SKILL.md

The canonical home for this skill is seo-cannibalization-detector in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

40%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 concise and well-sectioned but lacks executable guidance and validation, and it references a missing playbook file. It reads as a templated checklist rather than an actionable specialist skill.

Suggestions

Add a concrete overlap-detection method or command (e.g., a keyword-extraction prompt, a comparison table template, or a tool invocation) instead of listing only abstract tactics.

Insert validation checkpoints in the Approach workflow — e.g., verify ranking data before recommending consolidation, and confirm redirect targets before suggesting 301s — since canonical/redirect changes are destructive.

Create the referenced resources/implementation-playbook.md (or remove the broken reference) and move the inlined tactics/prevention lists into it for genuine one-level-deep progressive disclosure.

DimensionReasoningScore

Conciseness

The body is largely terse bullet lists with little padding and assumes SEO competence; minor redundancy between 'Resolution Tactics', 'Quick Fixes', and 'Prevention Framework' keeps it just below a 5.

4 / 5

Actionability

Guidance is high-level and checklist-style ('Merge similar content', '301 redirect weak pages') with no concrete commands, tools, or executable method for actually detecting overlap, matching the 2-anchor of minimal concrete guidance.

2 / 5

Workflow Clarity

The 'Approach' section lists a rough 7-step sequence but defines no validation checkpoints, and resolution tactics (301 redirects, canonicals) are destructive/batch operations that lack error-recovery loops, matching the 2-anchor.

2 / 5

Progressive Disclosure

The single reference 'open resources/implementation-playbook.md' points to a non-existent file with no bundle present, and content that could be split (tactics, prevention) is inlined, matching the 2-anchor of minimal/buried structure.

2 / 5

Total

10

/

20

Passed

Description

70%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 well-formed: third person, answers both what and when, and uses recognizable SEO terms. It is solid but not maximally specific or comprehensive in its trigger coverage.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions ('identify keyword overlap', 'Suggests differentiation strategies'), matching the 3-anchor; it does not list multiple comprehensive actions to reach 4.

3 / 5

Completeness

Provides a clear 'what' ('Analyzes... identifies... Suggests...') and an explicit 'when' ('Use PROACTIVELY when reviewing similar content'), but the trigger clause is somewhat generic rather than concrete, matching the 4-anchor.

4 / 5

Trigger Term Quality

'keyword overlap', 'cannibalization issues', 'reviewing similar content' are natural terms with good coverage, though common synonyms like 'duplicate content' or 'competing pages' are missing, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

'cannibalization' is a distinct SEO niche with minimal overlap risk versus general skills, though it could still overlap with broader SEO/content-audit skills, so it is mostly distinct rather than a clear niche.

4 / 5

Total

15

/

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
administrakt0r/AI-Agents-Safe-Coding-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.