CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

seo-cannibalization-detector

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

Quality

70%

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 ./skills/seo-cannibalization-detector/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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 covers the domain broadly with a well-organized section structure and a concrete output template, but dilutes itself with circular 'Use this skill when' boilerplate and four overlapping recommendation lists. The 7-step approach names its stages without specifying how to perform the analysis and includes no validation checkpoints.

Suggestions

Delete the circular 'Use this skill when / Do not use this skill when' sections and the generic 'Instructions' bullets — they restate the skill name without adding information.

Add concrete analytical detail to the Approach steps, e.g., a keyword-overlap threshold, a method for assessing content similarity, and the exact inputs to request (page text, target keyword list, ranking data).

Consolidate the overlapping Prevention Strategy / Resolution Tactics / Prevention Framework / Quick Fixes lists into one section, and add a validation checkpoint such as confirming target keywords with the user before recommending consolidation or redirects.

DimensionReasoningScore

Conciseness

The domain lists are lean, but the body carries pure filler: circular boilerplate ('Working on seo cannibalization detector tasks or workflows'), generic instructions ('Apply relevant best practices and validate outcomes'), and redundant overlap among Prevention Strategy, Prevention Framework, Resolution Tactics, and Quick Fixes. Not 2 because padding is a modest fraction and the rest is tight; not 4 because the filler sections earn no tokens and the redundant lists need consolidation.

3 / 5

Actionability

The output template is concrete ('Conflict: [Keyword]', 'Competing Pages:', resolution checkboxes) and tactics are specific ('301 redirect weak pages', 'Implement canonical to primary'), but the Approach steps name stages without any method ('Assess content similarity percentage' gives no threshold or technique, 'Identify topic and keyword overlap' gives no procedure). Not 4 because the core analytical method is unspecified; not 2 because the report format and tactics provide real, usable guidance.

3 / 5

Workflow Clarity

The Approach section is a coherent numbered 7-step sequence ('1. Analyze keywords in provided pages' through '7. Recommend unique angle for each'), but no validation checkpoints exist — 'Apply relevant best practices and validate outcomes' is a vague gesture, not a checkpoint. Not 4 because checkpoints are entirely absent and steps are terse labels; not 2 because the sequence is complete and logically ordered.

3 / 5

Progressive Disclosure

Self-contained single file with clear section headers (Focus Areas, Cannibalization Types, Prevention Strategy, Approach, Output) and no external references needed at this size. Not 5 because Prevention Strategy, Resolution Tactics, Prevention Framework, and Quick Fixes overlap substantially and could be consolidated; not 3 because the structure is good and content is appropriately placed in one file.

4 / 5

Total

13

/

20

Passed

Description

75%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 clearly states what the skill does through three concrete actions and includes an explicit 'Use when' clause, anchored by natural trigger terms like 'cannibalization' and 'keyword overlap'. Its main weakness is the generic 'when' trigger ('reviewing similar content'), which could be more specific and creates minor overlap risk with general content-review skills.

DimensionReasoningScore

Specificity

Lists three concrete actions — 'identify keyword overlap', 'potential cannibalization issues', and 'Suggests differentiation strategies' — matching the several-specific-actions-with-minor-gaps anchor. Not 5 because coverage has gaps (e.g., consolidation or canonical recommendations are unmentioned); not 3 because it goes beyond 1-2 actions and all are concrete.

4 / 5

Completeness

Clearly answers 'what' (three concrete analysis actions) and includes an explicit 'when' clause ('Use when reviewing similar content'). Not 5 because the when clause is generic rather than concrete trigger phrases; not 3 because the when guidance is explicitly stated, not merely implied.

4 / 5

Trigger Term Quality

'keyword overlap', 'cannibalization', and 'differentiation' are terms users would naturally say when needing this skill. Below 5 because common variations like 'SEO', 'competing pages', or 'multiple pages ranking for the same keyword' are missing; above 3 because the key natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

Keyword cannibalization analysis is a distinct niche, but 'Use when reviewing similar content' is broad and could overlap with general content-audit or SEO skills. Not 5 due to that broad trigger; not 3 because the core capability is clearly distinguishable.

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

rmyndharis/antigravity-skills

Path

skills/seo-cannibalization-detector/SKILL.md

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.