CtrlK
BlogDocsLog inGet started
Tessl Logo

keyword-clustering

Cluster keywords by intent and map them to existing or proposed pages.

64

Quality

75%

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 ./.agents/skills/keyword-clustering/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

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 tight, well-structured workflow that gives concrete tool calls, decision rules, validation checkpoints, and a defined output format without teaching concepts Claude already knows. All four dimensions score at the top of the scale.

DimensionReasoningScore

Conciseness

The body is lean bullet-and-section prose that assumes Claude's SEO competence; the only light glosses (e.g. 'one query splitting clicks across multiple URLs') earn their place as MCP-specific context, and there is no padding or concept teaching.

3 / 3

Actionability

Concrete, executable guidance throughout: named MCP tools with explicit parameters (dimensions: ["query","page"]), precise decision rules (same SERP intent groups together; different intent splits), and a fully specified output table plus per-cluster page brief structure.

3 / 3

Workflow Clarity

A clearly sequenced 7-step workflow with explicit validation checkpoints — a get_serp_results overlap check for borderline terms, cannibalization confirmed from real Search Console data, and an ask-before-tagging gate — reinforced by a Guardrails section, satisfying the batch-operation validation requirement.

3 / 3

Progressive Disclosure

A self-contained single file with no bundle files needed, organized into clearly navigable sections (Goal, Required inputs, MCP tools, Workflow, Output format, Guardrails); content is appropriately kept inline rather than split into unnecessary references.

3 / 3

Total

12

/

12

Passed

Description

50%Weight 40%Scale 1-3

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 concise, third-person, and states a clear niche with two concrete actions, but it lacks an explicit 'Use when...' trigger clause, which caps completeness and weakens trigger-term coverage and distinctiveness. All dimensions land at 2, yielding a mid-band result.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases, e.g. 'Use when the user wants to group or cluster keywords, map keywords to pages, or plan keyword-to-page targeting for SEO.'

Broaden trigger terms to include common variations users actually say: 'keyword research', 'keyword grouping', 'keyword mapping', 'SEO content mapping', and 'cannibalization'.

Add a third concrete capability to raise specificity (e.g. 'identify cannibalization across ranking URLs') alongside clustering and mapping.

DimensionReasoningScore

Specificity

Names two concrete actions ('Cluster keywords by intent', 'map them to existing or proposed pages') in an SEO domain, but is not comprehensive — the anchor-3 example lists three distinct actions, and this stops at two.

2 / 3

Completeness

Clearly states what the skill does (cluster and map keywords to pages) but provides no 'Use when...' trigger clause, so the 'when' guidance is missing rather than explicit — capping completeness at 2 per the rubric guideline.

2 / 3

Trigger Term Quality

Includes relevant terms like 'keywords', 'intent', and 'pages', but omits common natural variations a user would say such as 'keyword research', 'keyword grouping', 'keyword mapping', or 'SEO'.

2 / 3

Distinctiveness Conflict Risk

The SEO keyword-to-page mapping niche is fairly specific, but without explicit trigger guidance it could still overlap with a more general keyword-research skill, so conflict risk is not fully resolved.

2 / 3

Total

8

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
every-app/open-seo
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.