CtrlK
BlogDocsLog inGet started
Tessl Logo

keyword-research

When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.

64

Quality

75%

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

Quality

Content

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, instruction-only skill with a concrete scoring model and output templates, but it lacks executable data-sourcing mechanisms and validation checkpoints for its batch workflow. It sits at the mid-anchor across all content dimensions.

Suggestions

Add explicit validation/verification checkpoints between phases (e.g., confirm competitor rankings were retrieved before scoring, or verify opportunity scores sum correctly before grouping).

Replace the descriptive data-gathering steps with executable mechanisms — a named tool/API call or a script in ./scripts/ — for pulling Apple Search Suggestions and competitor keyword rankings.

Tighten conciseness by removing the 'You are an expert...' persona line and trimming the 'Why it matters' table column where the reason restates the signal name.

DimensionReasoningScore

Conciseness

Mostly efficient with tables, a compact scoring formula, and grouped buckets, but the persona opener and the explanatory 'Why it matters' column restate points Claude could infer; could be tightened.

2 / 3

Actionability

Provides concrete templates (char-limited metadata format) and an explicit Opportunity formula, but the core data-gathering steps ('Pull keyword rankings for top 3-5 competitors', autocomplete suggestions) are described rather than given an executable mechanism.

2 / 3

Workflow Clarity

The Phase 1-4 sequence plus Initial Assessment is clearly ordered, but there are no validation/verification checkpoints for these batch keyword operations, capping clarity at 2 per the rubric.

2 / 3

Progressive Disclosure

Single self-contained file with clear section headings and no nested references, but at ~140 lines it is one monolithic inline block with no content split into bundle files.

2 / 3

Total

8

/

12

Passed

Description

100%

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, third-person description that covers what the skill does, when to invoke it via natural trigger terms, and how it differs from related skills. It hits the top anchor on every dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'discover, evaluate, or prioritize App Store keywords' — naming a specific domain and several distinct operations.

3 / 3

Completeness

Explicitly answers both what (discover/evaluate/prioritize keywords) and when ('Also use when the user mentions...'), with an explicit trigger clause.

3 / 3

Trigger Term Quality

Covers a strong set of natural phrases users would say: 'keyword research', 'find keywords', 'search volume', 'keyword difficulty', 'keyword ideas', and 'what keywords should I target'.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to App Store keywords with distinct triggers, and explicitly routes adjacent needs to sibling skills (metadata-optimization, aso-audit), reducing misfires.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Eronred/aso-skills
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.