CtrlK
BlogDocsLog inGet started
Tessl Logo

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.

94

1.18x
Quality

92%

Does it follow best practices?

Impact

95%

1.18x

Average score across 6 eval scenarios

SecuritybySnyk

Advisory

Suggest reviewing before use

SKILL.md
Quality
Evals
Security

Quality

Discovery

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.

This is an excellent skill description that hits all the marks. It provides specific concrete actions, comprehensive trigger terms covering natural user language, an explicit 'Use when...' clause, and a clearly distinctive niche in App Store Optimization. The description is well-structured with a summary, trigger guidance, and detailed capability list.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: researching keywords, analyzing competitor rankings, generating metadata suggestions, keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes.

3 / 3

Completeness

Clearly answers both 'what' (ASO toolkit for researching keywords, analyzing competitors, generating metadata, etc.) and 'when' (explicit 'Use when...' clause listing multiple trigger scenarios). Also includes a supplementary sentence detailing supported capabilities.

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say: 'ASO', 'app store rankings', 'app metadata', 'app titles and descriptions', 'app store listings', 'app visibility', 'mobile app marketing', 'iOS', 'Android', 'Apple App Store', 'Google Play Store'. These are all terms a user would naturally use.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive niche focused specifically on App Store Optimization with clear domain-specific triggers like 'ASO', 'app store rankings', 'app store listings', and platform-specific terms (Apple App Store, Google Play Store). Unlikely to conflict with general marketing or SEO skills.

3 / 3

Total

12

/

12

Passed

Implementation

85%

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

This is a well-structured, highly actionable ASO skill with excellent workflow clarity including explicit validation checkpoints for each process. The progressive disclosure is strong with clear navigation to reference materials and scripts. The main weakness is verbosity—the document is quite long and some tables/sections could be consolidated or trimmed without losing actionable value, particularly given that Claude can infer standard ASO concepts.

Suggestions

Consolidate the before/after examples section—keep 2-3 strongest examples and cut the rest to reduce overall length by ~30 lines

Trim the 'Communication' section at the bottom which describes generic output formatting conventions that don't add ASO-specific value

DimensionReasoningScore

Conciseness

The skill is quite lengthy (~350+ lines) with some sections that could be tightened. Tables like 'Keyword Evaluation Criteria' weights and 'Launch Timing Considerations' add moderate value but the overall document is verbose for what Claude needs. The before/after examples section is valuable but could be more compact. Some sections like 'Communication' at the end explain output formatting conventions that feel padded.

2 / 3

Actionability

The skill provides highly concrete, actionable guidance throughout: specific character limits per platform, exact keyword field optimization techniques (remove spaces after commas, remove plurals), formula templates for titles, hypothesis templates for A/B tests, sample size tables, and executable script commands with flags. The before/after examples are particularly actionable with specific analysis of what changed and why.

3 / 3

Workflow Clarity

Each workflow has clearly numbered sequential steps with explicit validation checkpoints at the end (marked with **Validation:**). The validation steps include specific criteria like 'no competitor brand names included; no plurals in iOS keyword field' and 'significance reached (95%); results documented; winner implemented.' The A/B testing workflow includes a feedback loop (run until significance reached). Multi-step processes are well-sequenced with clear dependencies.

3 / 3

Progressive Disclosure

The skill is well-structured with clear sections, each workflow self-contained with summary tables, and references to deeper materials are one level deep and clearly signaled (e.g., 'See: [references/keyword-research-guide.md]'). Scripts, references, and assets are organized in dedicated tables at the end. Related skills are cross-referenced appropriately.

3 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
alirezarezvani/claude-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.