CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-clustering

Groups candidate keywords by user task and tests whether one page can satisfy them. Use for same-page decisions, mixed intent and adjacent queries.

Quality

72%

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

Quality

Content

68%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 exceptionally lean and dense with genuine domain expertise (the conditional-modifier and opposite-output-requirements rules are non-obvious), but it reads as compressed expert notes rather than an executable procedure. Adding a worked example, an output template, and section headers would convert its implicit workflow into an explicit one without sacrificing conciseness.

Suggestions

Add a short worked example showing one candidate set, its task analysis, the classification decision, and the resulting cluster record — this would make the abstract output-field list concrete and executable.

Break the four prose paragraphs into labeled sections (e.g. "## Process", "## Classification rules", "## Output") so the implicit workflow sequence becomes scannable and explicit.

Spell out the validation loop explicitly: what evidence threshold resolves a pending intent decision, and when to re-check ranking URLs rather than leaving 'if search evidence and task analysis disagree' implicit.

DimensionReasoningScore

Conciseness

The body is ~250 words of pure directive prose with zero padding and no explanation of concepts Claude already knows; even the one example ("removing white to obtain transparency and adding white for a product listing have opposite output requirements") earns its place by clarifying a non-obvious rule. Every token carries instruction, matching the lean anchor 5.

5 / 5

Actionability

There is concrete guidance — an explicit relationship taxonomy ("same-page variants, parent/child, adjacent tasks, conditional modifiers, mixed intent or exclusions"), a defined output record ("representative term, same-page variants, concrete task, expected asset, adjacent clusters, evidence and unresolved check"), and handoff targets — but no worked input-to-output example, no output template, and no criteria for "compare page types". This is more than high-level hints (ruling out 2) but missing key execution details, matching anchor 3.

3 / 5

Workflow Clarity

A rough sequence exists in prose order (identify starting state/operation/result → group → check capability and page type → compare ranking URLs → record market/date → handle disagreement) and there are implicit checkpoints ("leave the decision pending", "unresolved check"), but steps are scattered across paragraphs with no explicit ordering and validation is implicit rather than spelled out. This matches anchor 3's 'sequence present but checkpoints missing or implicit', below anchor 4's clear sequenced steps.

3 / 5

Progressive Disclosure

The skill is under 50 lines, fully self-contained, and needs no external references, which suits a compact SKILL.md. The gap is organization: a single H1 over four unsegmented paragraphs with no section headers for process, classification rules, and output format — a minor organization gap that keeps it below the well-organized-sections bar of anchor 5 but above anchor 3's structural deficiencies.

4 / 5

Total

15

/

20

Passed

Description

62%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 solid third-person description with an explicit "Use for" clause and a distinctive same-page test, answering both what and when. Its weaknesses are limited action coverage and trigger terms that miss the natural synonyms (keyword grouping, search intent) users would actually say.

Suggestions

Add one or two more concrete actions to the description, e.g. "deduplicates variants and classifies relationships (parent/child, adjacent, mixed intent)" to lift specificity.

Broaden trigger terms to include natural variations users say, such as "keyword grouping", "search intent", or "can these keywords share a page".

DimensionReasoningScore

Specificity

"Groups candidate keywords by user task and tests whether one page can satisfy them" names the domain plus two concrete actions (grouping, same-page testing), but coverage stops there — no mention of deduplication, relationship classification, or output format. This matches the anchor for 1-2 concrete actions without comprehensiveness, and falls short of anchor 4 which expects several specific actions.

3 / 5

Completeness

The description answers both questions: a clear what ("Groups candidate keywords by user task and tests whether one page can satisfy them") and an explicit when ("Use for same-page decisions, mixed intent and adjacent queries"). The when-clause is explicit but its trigger phrases are less concrete than anchor 5's user-mention triggers, so it sits at anchor 4.

4 / 5

Trigger Term Quality

"same-page decisions, mixed intent and adjacent queries" are relevant domain terms a practitioner might use, but common natural variations are missing — e.g. "keyword grouping", "search intent", "SERP overlap". Coverage is partial rather than good, matching anchor 3 and below anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

The one-page-satisfaction test is a distinctive niche operation that separates this from generic keyword-research skills, leaving only minor overlap risk with closely related skills (keyword-opportunity, keyword-mapping). It is more distinct than anchor 3's 'could still overlap with similar skills' but lacks anchor 5's fully distinct trigger set.

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

kostja94/marketing-skills

Path

skills/keyword-clustering/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.