CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-discovery

Finds long-tail search expressions from a seed, competitor sites, search suggestions and customer language. Use for keyword expansion and demand discovery.

Quality

69%

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

Quality

Content

61%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 packs genuinely expert, non-generic keyword-research methodology into a small token budget, with concrete examples, labeling rules, and fallbacks. Its weaknesses are structural: no headers or sections turn it into a wall of text, the workflow sequence and checkpoints stay implicit, and a few passages could be tightened.

Suggestions

Break the nine paragraphs into section headers (e.g., '## Seed and boundaries', '## Variant probing', '## Broader queries', '## Competitor and SERP evidence', '## Handoff and stopping'), which would address both progressive_disclosure and the implicit sequencing.

Make the workflow order explicit — a short numbered sequence for the discovery pass, with the labeling rules (observed vs. inferred, hypotheses) presented as checkpoints per step.

Move the worked domain examples (background remover, song generator) into a short '## Examples' section or a reference file so they are clearly signaled rather than interleaved mid-paragraph.

DimensionReasoningScore

Conciseness

The body is dense with domain-specific guidance — variant-probing dimensions, verbatim examples like the "generate song with ai" expansion, labeling rules (observed vs. inferred), and recording fields — with almost no explanation of concepts Claude already knows. It falls short of 5 because several tangled sentences ('For a narrow seed, identify the constraint that narrows it... Show the parent followed by the input seed and explain the difference') and hedging qualifiers ('when relevant', 'when helpful') could be tightened.

4 / 5

Actionability

For an instruction-only research skill the guidance is concrete: exact surfaces to probe (Autocomplete, People Also Ask, People Also Search For, Related, GSC queries, ad search terms), exact fields to record (URL, market, language, date, source), a worked variant example, labeling rules, and a fallback procedure via an authorized cloud browser. It is not a 5 because some guidance stays abstract — the dimension lists ('Explore alternative wording, action, input, desired output, audience...') tell Claude what to vary but not how to systematically generate or prioritize variants.

4 / 5

Workflow Clarity

A rough sequence exists in paragraph order (seed and boundaries → base expression family → broader/parent queries → competitor pages → SERP surfaces → first-party data → clustering handoff), and there are good implicit checkpoints like 'Keep unattested forms labeled as hypotheses' and 'Distinguish a module absent on an inspected page from a page that could not be inspected'. This matches anchor 3: the sequence is present but steps and checkpoints are implicit rather than clearly staged, with no explicit ordering or stop-conditions-per-step.

3 / 5

Progressive Disclosure

The body is a title followed by nine unbroken prose paragraphs with no section headers, subheadings, or lists, matching 'minimal structure' (anchor 2). While the ~30-line skill needs no external reference files, it is not 'well-organized sections' as the simple-skill exception requires, and embedded worked examples (the background-remover and song-generator cases) read as candidate reference material.

2 / 5

Total

13

/

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 concise, third-person description that clearly states what the skill does and includes an explicit use clause. Its main weaknesses are a single-action 'what' statement and a trigger clause that restates the domain rather than adding natural user phrasings like 'keyword research' or 'SEO keywords'.

Suggestions

Add the natural synonyms users actually say — e.g., 'Use for keyword research, finding keyword ideas, or SEO keyword expansion' — to strengthen trigger-term quality.

Broaden the 'what' beyond one action to cover the skill's full workflow, e.g., 'Expands a seed keyword into long-tail variants, clusters them, and validates demand from competitor pages and search suggestions.'

DimensionReasoningScore

Specificity

"Finds long-tail search expressions from a seed, competitor sites, search suggestions and customer language" names the domain and one concrete action (finding long-tail expressions) with four sources, matching the anchor for domain plus 1-2 concrete actions. It does not list several distinct actions (e.g., clustering, SERP probing, parent-query expansion), so it is not a 4.

3 / 5

Completeness

Both parts are present: the 'what' ("Finds long-tail search expressions from a seed, competitor sites, search suggestions and customer language") and an explicit 'when' ("Use for keyword expansion and demand discovery"), mirroring the anchor-4 example where the when-clause restates the domain. It falls short of 5 because the when-clause lacks concrete trigger phrases a user would actually say (e.g., 'when the user asks for keyword ideas or SEO keyword research').

4 / 5

Trigger Term Quality

Terms like "keyword expansion", "long-tail search expressions", and "search suggestions" are relevant, but the most natural user phrasings — "keyword research", "find keywords", "SEO keywords", "keyword ideas" — are absent. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

The keyword-expansion/demand-discovery niche is fairly distinct and unlikely to trigger for unrelated skills, matching 'mostly distinct; minor overlap risk'. It is not a 5 because broader SEO, competitor-analysis, or web-research skills could plausibly compete for the same requests given no sharper trigger wording.

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