CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-research

Coordinates keyword research from a seed or existing keyword data through discovery, intent clustering, opportunity assessment and page mapping.

Quality

80%

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-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 a lean, well-structured orchestrator document: it sequences a multi-step workflow with an explicit completion checklist and feedback loops, and keeps detail appropriately in a single verified one-level reference. Its only weaknesses are mild repetition of stop/scope conditions and a few abstract directives where concrete criteria would help.

DimensionReasoningScore

Conciseness

The body is dense and declarative with no explanations of concepts Claude already knows — every section is instructional. It is not a 5 because stop/scope conditions are stated in three separate places ("Stop when additional sources yield no material new tasks", "Stop at its agreed node", "Stop at the requested deliverable") and could be consolidated.

4 / 5

Actionability

Concrete guidance is present: a handoff table naming four sibling skills with their handoff artifacts, an explicit report format ("one row per candidate page cluster with a primary term, same-page variants, intent, landing page / blog / other type, proposed URL, decision and evidence or gap"), and concrete defaults ("skip US search volume and keyword prioritization"). It falls short of anchor 5 because some direction remains abstract ("Establish the decision, product capabilities, market, language and channel") and execution details are delegated to sibling skills.

4 / 5

Workflow Clarity

A six-step numbered sequence covers the full pipeline, backed by a dedicated "Completion check for a full study" checklist requiring each node be accounted for as "observed, inferred, blocked or outside the requested scope", with explicit feedback loops ("Send ambiguous high-impact branches back for targeted research", "Return to discovery for a specific unresolved branch") and a resume rule. This matches anchor 5's explicit validation, recovery loops, and checklist; it is not a 4 because checkpoints are explicit rather than implicit.

5 / 5

Progressive Disclosure

The ~40-line body is a clear overview: well-organized sections, a single clearly-signaled one-level-deep reference ([category research](references/category-research.md)) that exists in the bundle, and no nested references. Per the simple-skill guidance, a short skill with no need for additional external references scores 5 with well-organized sections.

5 / 5

Total

18

/

20

Passed

Description

66%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 communicates a clear, specific orchestration pipeline for keyword research with natural domain terminology, but it entirely lacks a "when to use" trigger clause, capping its completeness. Adding explicit trigger guidance and common synonyms like "SEO" or "search terms" would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks for keyword research, SEO keyword ideas, search-term analysis, or deciding which keywords to target and which pages to map them to."

Include natural user-facing synonyms such as "SEO", "search terms", and "keyword ideas" alongside the domain jargon to broaden trigger-term coverage.

Clarify the coordinator role versus the sibling keyword-discovery/clustering/opportunity/mapping skills to reduce overlap risk with those closely related skills.

DimensionReasoningScore

Specificity

The description lists several concrete pipeline actions — "discovery, intent clustering, opportunity assessment and page mapping" — going beyond naming the domain. It falls short of anchor 5 because the leading verb "Coordinates" is soft and the actions are workflow stages rather than fully concrete operations with comprehensive output coverage.

4 / 5

Completeness

The "what" is clearly and specifically stated (coordinates keyword research through four named stages), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the "what" is present and concrete rather than vague.

3 / 5

Trigger Term Quality

"keyword research", "seed", "discovery", "intent clustering" and "page mapping" are natural phrases users would say in this domain. A few natural terms are missing — no "SEO", "search terms", "keyword ideas" or "rankings" — so it does not reach the comprehensive synonym coverage of anchor 5, but it clearly exceeds the partial coverage of anchor 3.

4 / 5

Distinctiveness Conflict Risk

"keyword research" with intent clustering and page mapping is a clear niche with distinct vocabulary, giving minimal conflict with unrelated skills. However, it shares its domain with the sibling keyword-discovery/clustering/opportunity/mapping skills it coordinates, creating minor overlap risk with closely related skills — anchor 4 rather than 5.

4 / 5

Total

15

/

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-research/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.