CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

blog-cannibalization

Detect keyword cannibalization across blog posts by extracting primary keywords from titles and headings, clustering semantically similar targets, and flagging posts competing for the same search intent. Supports a free local mode (file analysis) and a paid DataForSEO API mode that runs only after the user approves the call count. Outputs a severity-scored report with a recommended action per cluster (merge, differentiate, canonical, noindex, or no action). Use when the user says "cannibalization", "keyword overlap", "competing pages". Not a site audit (blog-audit) or cluster planning (blog-cluster); it changes no files or redirects.

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable body with clear sequenced workflows, explicit spend-approval gates, and error-recovery loops for both modes. Its weaknesses are token efficiency (redundant severity descriptions, convoluted path preamble, inline dated pricing asides) and progressive disclosure (a dangling orchestration-details.md reference and a large inlined API/recommendation playbook with no bundled reference files).

Suggestions

Move the DataForSEO endpoint payloads, spend-approval policy, and API error-retry rules into a bundled references/ file (e.g. references/dataforseo-api.md) and keep a short API-mode summary in SKILL.md — this shortens the body and gives the bundle a real reference layer.

Resolve the dangling reference: 'orchestration-details.md' is called the main reference but no such file exists in the bundle (there is no references/ directory); either bundle it or remove the instruction.

Tighten the time-stamped pricing asides: consolidate the two inline 'checked 2026-10-12' sentences into a single dated line (or move them into the references file), and merge the three severity descriptions (table, API formula, local heuristic) where they overlap.

DimensionReasoningScore

Conciseness

Mostly operational, but the opening ${CLAUDE_SKILL_DIR}/blog_reference_root paragraph is convoluted, severity is described three times (table, API formula, local heuristic), and inline time-stamped asides ('checked 2026-10-12' twice; 'the Labs docs say each request is charged, point to the DataForSEO Pricing page, and list no flat price') pad the body. Not 4: these passages could clearly be tightened; not 2: there is no concept tutorial padding and nearly every line is operational.

3 / 5

Actionability

Gives concrete Glob patterns and skip lists, a deterministic n-gram extraction algorithm, copy-paste POST JSON payloads for both endpoints, and an exact output table. Not 5: the 'dedicated local CLI wrapper' is required for API mode but never given an invocation command, so that mode cannot be executed from the document alone; not 3: local mode and the payloads are executable, not pseudocode.

4 / 5

Workflow Clarity

Both modes have numbered, clearly sequenced steps with explicit checkpoints and recovery loops: spend approval 'before any API call', 'Cannibalization analysis requires at least 2 posts', and 'If a 429 response is received, wait and retry once. If it persists, switch to local mode'. Not 4: validation gates and error-recovery feedback loops are explicit, not merely implied.

5 / 5

Progressive Disclosure

The bundle contains no references/, scripts/, or assets/ files, yet the body names a 'main reference `orchestration-details.md`' that does not exist, and ~150 lines of DataForSEO endpoint detail and recommendation playbooks are inlined in SKILL.md. Not 2: section headers and tables provide genuine structure and navigation; not 4: the one named reference is dangling and bulk detail belongs in separate files.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description: concrete, third-person capability statements, both operating modes with their cost implications, explicit trigger phrases, and explicit disambiguation from sibling skills. The only weakness is trigger coverage that omits a few natural phrasing variations users might say.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'extracting primary keywords from titles and headings, clustering semantically similar targets', 'Outputs a severity-scored report with a recommended action per cluster (merge, differentiate, canonical, noindex, or no action)' — covering detection, clustering, both modes, and output with no notable gap. Not 4: coverage is comprehensive rather than having minor gaps, and the voice is consistently third person ('Detect', 'Supports', 'Outputs').

5 / 5

Completeness

Explicitly answers both what ('Detect keyword cannibalization... flagging posts competing for the same search intent', plus modes and output actions) and when (quoted trigger phrases). Not 4: the 'when' clause is explicit with concrete triggers rather than merely present-but-imprecise.

5 / 5

Trigger Term Quality

'Use when the user says "cannibalization", "keyword overlap", "competing pages"' captures the core terms of art a user would naturally say. Not 5: common variations like 'competing for the same keywords' or 'multiple pages ranking for the same term' are missing; not 3: the primary natural phrases are present, not just generic keywords.

4 / 5

Distinctiveness Conflict Risk

'Not a site audit (blog-audit) or cluster planning (blog-cluster); it changes no files or redirects' explicitly fences sibling skills, and the cannibalization niche has distinct triggers. Not 4: conflict risk is actively addressed by boundary statements rather than merely minor.

5 / 5

Total

19

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

AgriciDaniel/claude-blog

Path

skills/blog-cannibalization/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.