CtrlK
BlogDocsLog inGet started
Tessl Logo

keyword-research

Find high-value SEO keywords: search volume, difficulty, intent classification, topic clusters. 关键词研究/内容选题

61

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/keyword-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 delivers a well-sequenced, validated 8-phase workflow with good progressive disclosure to real reference files, but it carries notable verbosity in inline templates and taxonomy tables that Claude already knows. Trimming those into references would materially improve conciseness.

Suggestions

Move the full modifier list (Phase 3) and difficulty-tier table (Phase 5) into a reference file, keeping only a few illustrative examples inline.

Replace the generic intent taxonomy table in Phase 4 with a pointer to references/keyword-intent-taxonomy.md, since that file already exists.

Cut the "Tips for Success" section, which restates guidance already covered in the phases.

DimensionReasoningScore

Conciseness

The body is mostly efficient but includes padded templates Claude largely already knows (full modifier lists, difficulty-tier tables, intent taxonomy), which could be moved to references or trimmed.

3 / 5

Actionability

Provides concrete phases, a scoring formula `Opportunity = (Volume × Intent Value) / Difficulty`, intent-value weights, and a specific quality-bar table; mostly executable with minor gaps since live tool commands are optional.

4 / 5

Workflow Clarity

An explicit 8-phase sequence with `[Phase X/8]` announcements, a dedicated Validation Checkpoints section, and a quality-bar rewrite loop give clear sequencing with explicit validation and feedback.

5 / 5

Progressive Disclosure

References are one level deep, clearly signaled via a "Reference Materials" section, and all four referenced files (example-report, keyword-intent-taxonomy, keyword-prioritization-framework, topic-cluster-templates) exist in ./references/.

5 / 5

Total

17

/

20

Passed

Description

70%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 specific and distinctive, naming concrete SEO deliverables and a multilingual trigger, but it omits an explicit "Use when..." clause, which caps its completeness. Adding trigger guidance would lift it from good to excellent.

Suggestions

Append an explicit "Use when..." clause to the description, e.g. "Use when starting keyword research for a new page, topic, or campaign, or when the user asks about search volume or keyword difficulty."

Add a couple of natural-language trigger phrases (e.g. "what to write about", "keyword ideas") alongside the technical terms to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Find high-value SEO keywords: search volume, difficulty, intent classification, topic clusters" names several concrete actions, but lacks full coverage of outputs like clustering deliverables to reach 5.

4 / 5

Completeness

Has a clear "what" but no explicit "Use when..." clause inside the description field itself, so completeness is capped at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms ("SEO keywords", "search volume", "difficulty", "topic clusters") plus the multilingual synonym "关键词研究/内容选题", but is missing a few common phrasings like "what to write about".

4 / 5

Distinctiveness Conflict Risk

"SEO keyword research" with specific deliverables (volume, difficulty, intent, clusters) is a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation14 / 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

Total

14

/

16

Passed

Repository
MODSetter/SurfSense
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.