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

94%

Does it follow best practices?

Impact

95%

1.18x

Average score across 6 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

The canonical home for this skill is app-store-optimization in alirezarezvani/claude-skills

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable skill body with explicit validation checkpoints on every workflow and concrete commands. The main weaknesses are length that could be trimmed and referenced bundle files that are missing from the reviewed package.

Suggestions

Move most of the Before/After Examples section into a reference file (e.g. references/optimization-examples.md), keeping one canonical title and description example inline, to reduce SKILL.md footprint and improve conciseness.

Ensure the referenced bundle files ship with the skill — references/keyword-research-guide.md, references/platform-requirements.md, references/aso-best-practices.md, the eight scripts/*.py, and assets/aso-audit-template.md are cited via 'See:' links but are absent from the reviewed bundle, leaving navigation broken.

Tighten the Keyword Placement Priority and Platform Character Limits tables where they duplicate information already implied by the workflow steps, to further earn their token cost.

DimensionReasoningScore

Conciseness

Content is dense with ASO-specific domain knowledge (character limits, scoring weights, before/after examples) rather than concepts Claude already knows, but the body runs ~470 lines and the Before/After Examples section could be trimmed or moved to keep the overview lean. It sits above the midpoint because almost every token is domain-useful, not padded.

4 / 5

Actionability

Provides copy-paste-ready script invocations ('python keyword_analyzer.py --keywords "todo,task,planner"'), a title formula, character-limit tables, and concrete before/after examples covering the common cases.

5 / 5

Workflow Clarity

Each of the five workflows is a numbered sequence ending in an explicit '**Validation:**' checkpoint (e.g. step 8 in keyword research, metadata, competitor, launch, and A/B workflows), plus a pre-launch checklist — matching the explicit-validation-and-feedback-loop anchor.

5 / 5

Progressive Disclosure

Structure is well designed: clearly signaled one-level-deep 'See: [references/...]' links and a Tools/References/Assets table point outward from an overview. However, the referenced bundle files (references/*.md, scripts/*.py, assets/aso-audit-template.md) are not present in the reviewed bundle, so those links are currently dead, keeping it below a 5.

4 / 5

Total

18

/

20

Passed

Description

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

An exemplary description: concrete capabilities, comprehensive natural trigger terms, and explicit what/when guidance all in third person. No fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'researching keywords, analyzing competitor rankings, generating metadata suggestions' plus 'keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklists, and tracking ranking changes' — giving comprehensive, third-person coverage of capabilities.

5 / 5

Completeness

Explicitly states what it does ('toolkit for researching keywords...') and when to use it ('Use when the user asks about ASO, app store rankings...') with concrete trigger phrases, satisfying both halves.

5 / 5

Trigger Term Quality

Natural trigger terms include 'ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, mobile app marketing on iOS or Android' — broad coverage with synonyms and platform variants users actually say.

5 / 5

Distinctiveness Conflict Risk

Scoped to 'Apple App Store and Google Play Store' with app-store-specific triggers, carving a clear niche with minimal overlap risk against generic SEO or marketing skills.

5 / 5

Total

20

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 15 missing, 3 suspicious

Warning

referenced_paths_exist

Referenced path issues: 18 missing

Warning

Total

13

/

16

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.