CtrlK
BlogDocsLog inGet started
Tessl Logo

keyword-clustering

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

56

Quality

64%

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

Quality

Content

75%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 content is a well-structured, actionable instruction skill with concrete tooling, decision rules, and validation checkpoints, held just below the top anchors by minor repetition and the absence of explicit error-recovery loops.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no padding about what SEO, keywords, or SERPs are — with only minor repetition of the Search Console/cannibalization point across Project context and Workflow, fitting the efficient-with-minor-trims anchor at 4 rather than the every-token-earns-its-place anchor at 5.

4 / 5

Actionability

Concrete MCP tool names are paired with specific parameters (e.g., get_search_console_performance with dimensions ["query","page"]), explicit decision rules (same SERP intent → together; different intent → split), and a defined output table, but it stops short of fully copy-paste-ready examples across every common case.

4 / 5

Workflow Clarity

A clear 7-step sequence includes checkpoints (reuse research within 30 days, SERP overlap check for borderline terms, ask before tagging), and the batch tagging operation is gated by confirmation, satisfying the destructive/batch validation requirement; it lacks an explicit error-recovery feedback loop, keeping it below 5.

4 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-labeled sections (Goal, Required inputs, Project context, Tools, Workflow, Output format, Guardrails) and no nested references; it earns 4 rather than 5 because the body exceeds 50 lines with minor overlap between the tools list and the workflow steps.

4 / 5

Total

16

/

20

Passed

Description

53%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 concise, third-person, and states a clear what, but it omits any when-to-use trigger guidance and lacks keyword synonyms, leaving it solidly mid-rubric rather than strong.

Suggestions

Add an explicit 'Use when...' trigger clause (e.g., 'Use when mapping keyword research to pages, grouping keywords by intent, or planning a site's page-to-keyword targeting').

Include natural synonyms users say — 'group keywords', 'keyword mapping', 'keyword research' — to improve trigger-term coverage.

Optionally name one more concrete action (e.g., surfacing cannibalization) to lift specificity toward the 4 anchor.

DimensionReasoningScore

Specificity

Names the domain and two concrete actions — "Cluster keywords by intent" and "map them to existing or proposed pages" — but the action set is not comprehensive, matching the 1-2 concrete actions anchor rather than the several-actions anchor at 4.

3 / 5

Completeness

It clearly answers "what" (cluster and map keywords) but provides no "Use when..." clause or equivalent trigger guidance, so per the rubric guideline a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes the natural core terms "keywords" and "cluster"/"map", but misses common variations and synonyms a user might say ("group keywords", "keyword research", "keyword mapping", "SERP"), fitting the some-relevant-keywords-but-missing-synonyms anchor.

3 / 5

Distinctiveness Conflict Risk

It targets a clear niche (intent-based keyword-to-page mapping) with low conflict risk, though "keywords"/"intent" leave minor overlap with adjacent SEO research skills, placing it just below the minimal-conflict anchor at 5.

4 / 5

Total

13

/

20

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.