CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

keyword-research

Use when the user asks to "find keywords", "挖词", or "搜什么词"; prioritizes search volume, keyword difficulty, intent, and topic clusters from provided or connected data. Not for competitor-relative coverage gaps — use content-gap-analysis. 关键词研究/内容选题

Quality

75%

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

Quality

Content

71%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.

A well-structured skill with a clear 8-phase workflow, concrete scoring formulas, runnable connector commands, and exemplary progressive disclosure into a real, verifiable reference bundle. The main cost is token efficiency: the Data Sources prose, funnel-stage definitions, and attribution asides restate things Claude knows or that belong in the reference files.

Suggestions

Trim the Data Sources section to the two commands plus one-line caveats; move the striking-distance GSC recipe and API rowLimit details into references/instructions-detail.md.

Delete the attribution aside '(Impact×Confidence + funnel-stage scoring adapted from an external SEO-ops competitive analysis.)' and compress the BOFU/MOFU/TOFU pattern lists, which Claude can infer from a few examples.

Keep the evidence-labeling rules but merge the two overlapping sentences in the Instructions section (line 69) that both state the Unknown-with-reason rule.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes unnecessary padding: a long prose Data Sources section ("~1,000 credits/mo, no key needed", the striking-distance paragraph), an attribution aside — "(Impact×Confidence + funnel-stage scoring adapted from an external SEO-ops competitive analysis.)" — and explanation of concepts Claude already knows (BOFU/MOFU/TOFU funnel definitions, the four standard intent categories). Not a 2 because nearly every sentence carries operational content; not a 4 because several of these passages could clearly be trimmed or moved to instructions-detail.md.

3 / 5

Actionability

The body gives concrete, runnable commands (the suggest.py/firecrawl.py/pageviews.py invocations with flags), an explicit formula — "Opportunity = (Volume × Intent Value) / Difficulty, with Intent Value 1 / 1 / 2 / 3" — a defined save path, and an enforced quality bar ("every recommendation includes at least one specific number"). Not a 5 because the eight phases themselves are one-line directives whose executable detail is deferred to references, leaving minor gaps inline.

4 / 5

Workflow Clarity

The eight phases are explicitly sequenced and announced ("run eight phases and announce each as [Phase X/8: Name]"), with a 'Done when' contract serving as an end-of-run checklist and evidence-labeling rules (Measured/Calculated/Unknown, NOT_SCORED on unknown decision-critical inputs) acting as per-field checkpoints. Not a 5 because there are no explicit per-phase validation or fix-and-retry loops; this is a read-only research workflow, so the destructive-operation cap does not apply.

4 / 5

Progressive Disclosure

The SKILL.md is a genuine overview: detail is split into five real bundle files (instructions-detail.md, example-report.md, keyword-intent-taxonomy.md, topic-cluster-templates.md, keyword-prioritization-framework.md — all present in references/), each linked one level deep with descriptive labels in the Reference Materials section, plus a dedicated example report. Cross-skill links (competitor-analysis, skill-contract.md) are clearly signaled and structural, matching the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

16

/

20

Passed

Description

73%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 strong, bilingual, well-bounded description with excellent explicit triggers and an explicit negative boundary that routes users away from a sibling skill. Its main weakness is the thin 'what' side: it says what it prioritizes rather than what it does (discover, score, cluster keywords), leaving capability coverage implicit.

Suggestions

Replace or augment the 'what' clause with explicit capability verbs, e.g. 'Discovers, scores, and clusters keywords for SEO/GEO planning; prioritizes search volume, keyword difficulty, intent, and topic clusters.'

Add one or two more natural English triggers such as 'keyword research' or 'SEO keywords' to round out the English-side coverage already present in Chinese.

DimensionReasoningScore

Specificity

The description names the domain and criteria — "prioritizes search volume, keyword difficulty, intent, and topic clusters from provided or connected data" — but 'prioritizes' is the only action verb; it never states that the skill discovers, expands, scores, or clusters keywords, so coverage of concrete actions is incomplete. Not a 4 because unlike 'Extracts text from PDF files, fills forms, converts pages to images' it does not list several specific actions; not a 2 because it is far more concrete than 'Processes PDF files'.

3 / 5

Completeness

The 'when' is explicit with concrete trigger phrases ("Use when the user asks to 'find keywords', '挖词', or '搜什么词'"), and the 'what' is present but weak — 'prioritizes search volume, keyword difficulty, intent, and topic clusters' describes the criteria, not the skill's actions or deliverable. Not a 5 because the what-side lacks explicit capability verbs; not a 3 because both halves are stated rather than one being missing.

4 / 5

Trigger Term Quality

Natural trigger phrases are present in two languages — "find keywords", "挖词", "搜什么词", "关键词研究/内容选题" — phrased as things a user would actually say. Missing common English variations such as 'keyword research', 'SEO keywords', or 'what to write about', so it falls just short of the comprehensive-synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche with an explicit exclusion — "Not for competitor-relative coverage gaps — use content-gap-analysis" — plus distinct bilingual triggers, so conflict risk with neighboring SEO skills is minimal. This matches the anchor 'Clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

16

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 9 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing, 1 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

seo-geo/survey/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.