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.

70

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

75%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 clear, well-sequenced ASO keyword research workflow with a concrete scoring formula and ready-to-use output templates. Its main weakness is that the data-acquisition steps assume a tool/API without naming one, and it lacks a final validation checkpoint on the generated report.

Suggestions

Name the concrete tool or API for each data-gathering step (e.g., how to fetch Apple Search Suggestions and competitor keyword rankings) so the guidance is fully executable rather than intent-only.

Trim the persona opener and the "Why it matters" column to remove explanations of cause-and-effect Claude already knows, tightening token efficiency.

Add a short validation/review checkpoint before emitting the report (e.g., confirm every Primary keyword has a non-zero Opportunity score and that title/subtitle/keyword-field character limits are respected).

DimensionReasoningScore

Conciseness

Mostly lean with well-organized phases, tables, and a concrete formula, but the persona opener ("You are an expert ASO keyword researcher with deep knowledge…") and the "Why it matters" column over-explain cause-and-effect Claude already knows; sits above the 3 anchor yet short of fully lean at 5.

4 / 5

Actionability

Provides concrete guidance — an explicit Opportunity formula with weights, scored signals, grouping counts (Primary 3-5, Secondary 5-10), and copy-ready output templates — but data-gathering steps like "get autocomplete suggestions" and "pull keyword rankings for competitors" name no tool, API, or command, leaving a minor executable gap.

4 / 5

Workflow Clarity

Cleanly sequenced Initial Assessment → Phase 1-4 → Output Format pipeline with specific per-phase deliverables; this is a non-destructive analysis task so the validation cap does not apply, and it earns 4 rather than 5 because no explicit verification or review checkpoint closes the loop before producing the report.

4 / 5

Progressive Disclosure

Well-structured single-file skill with clear section headers and a self-contained body; no bundle files exist and references ("Related Skills", app-marketing-context.md) are one level deep and clearly signaled, so it lands at 4 rather than 5 because nothing is split into load-on-demand bundle materials.

4 / 5

Total

16

/

20

Passed

Description

95%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, well-structured description that clearly states the skill's purpose, supplies natural trigger terms, and disambiguates from neighboring ASO skills. It uses third-person framing ("the user wants") and avoids fluff.

DimensionReasoningScore

Specificity

Names the App Store keyword domain and three concrete actions — "discover, evaluate, or prioritize" — comparable to the anchor listing several specific actions with minor coverage gaps; not a 5 because it stops at three verbs without richer sub-actions.

4 / 5

Completeness

Explicitly answers both what ("discover, evaluate, or prioritize App Store keywords") and when ("Also use when the user mentions…" with concrete trigger phrases), matching the top anchor; not below because neither half is missing or merely implied.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases a user would actually say — "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", "what keywords should I target" — matching the anchor for full coverage including synonyms.

5 / 5

Distinctiveness Conflict Risk

Clear ASO-keyword niche with distinct triggers and explicit disambiguation from sibling skills ("see metadata-optimization", "see aso-audit"), giving minimal conflict risk per the top anchor.

5 / 5

Total

19

/

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.

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.