CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-store-optimization

Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance on Apple App Store and Google Play Store

1.18x
Quality

56%

Does it follow best practices?

Impact

91%

1.18x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/app-store-optimization/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

32%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 is a well-organized but bloated catalog: it contains genuinely valuable ASO-specific facts (character limits, JSON I/O schemas, scoring weights) buried in padding (repeated example prompts, generic best-practice advice, duplicated capability/script listings). Its two structural failures are the absence of any executable workflow — no step sequences or validation checkpoints per task — and a complete mismatch with its bundle, documenting eight scripts and detailed reference material while providing no supporting files.

Suggestions

Actually ship the eight documented scripts in a scripts/ directory (or delete the Scripts section) — every documented function such as analyze_keyword() or validate_character_limits() currently points to a nonexistent file, making the documented API misleading.

Add per-task step sequences with explicit validation checkpoints, e.g. for metadata optimization: draft metadata → run character-count validation → fix over-limit fields → re-validate → emit package; this would also fix the missing feedback loop for the batch/destructive-style operation of overwriting a live store listing.

Cut the seven 'How to Use' example prompts (~30 lines) and move the best-practice lists and platform requirement tables into references/ files linked one level deep from a concise SKILL.md overview, reclaiming a large share of the token budget.

DimensionReasoningScore

Conciseness

The ~400-line body contains several padded sections: seven near-identical 'Hey Claude—I just added the skill...' example prompts that teach Claude nothing, generic advice it already knows ('Professional Tone: Always courteous', 'Natural Language: Write for humans first, SEO second', 'Thank Supporters: Acknowledge positive reviews'), and a Scripts section that largely restates the Capabilities section. Time-sensitive trivia like 'formerly 30, increased in 2021' and 'as of November 2025' adds token cost without being placed in a deprecation/old-patterns framing. This matches the score-2 anchor ('noticeably verbose; several unnecessary explanations or padded sections'); it is not a 3 because the padding is extensive rather than incidental, though the platform character limits and JSON schemas are genuinely non-obvious facts that earn their place.

2 / 5

Actionability

There is real concrete material — exact JSON input schemas for each task, precise platform character limits, a fully specified ASO scoring breakdown (0-25 per category) — but it is not executable: no commands or invocation examples are given anywhere, and the eight documented scripts (keyword_analyzer.py, aso_scorer.py, etc.) do not exist in the bundle (no scripts/ directory), so the documented API is a phantom. This sits at the score-3 anchor ('some concrete guidance but incomplete... missing key details') rather than 2, since the guidance is substantial and specific, not minimal high-level hints.

3 / 5

Workflow Clarity

The body is a capability catalog with no task-level step sequences at all — there is no 'to do keyword research: 1... 2... 3...' anywhere, no validation checkpoints (e.g., no explicit character-count validation step before emitting optimized metadata, despite 'character count validation' being listed as an output), and no error-recovery guidance. The implicit structure (capabilities → inputs → outputs → scripts) provides a rough order, matching the score-2 anchor ('rough sequence present but many gaps; steps poorly defined; validation absent').

2 / 5

Progressive Disclosure

Despite having section headers (so not a score-1 structureless wall), all content is inlined in SKILL.md: eight script API reference blocks, six best-practice lists, platform requirement tables, and full I/O schemas — material that clearly belongs in separate reference files per the score-2 anchor ('content that clearly belongs in separate files is inlined'). The bundle contains no references/, scripts/, or assets/ directories at all, so every script path named in the body is a dangling reference, leaving no progressive disclosure structure to evaluate positively.

2 / 5

Total

9

/

20

Passed

Description

61%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 identifies a clear, distinctive niche and reasonably natural trigger terms, but it reads as a capability summary rather than a trigger description: the actions are generic verbs, and — most importantly — it contains no 'Use when...' clause telling Claude when to activate it. Adding explicit trigger guidance and concrete artifact-level actions would lift it substantially.

Suggestions

Append a trigger clause such as: 'Use when the user mentions app store optimization, ASO, app keywords, store rankings, app listings, or launching/optimizing an app on the Apple App Store or Google Play Store.'

Replace the generic verbs ('researching, optimizing, and tracking') with concrete actions, e.g., 'Research app keywords, optimize titles/descriptions/keyword fields, analyze competitors and reviews, and track keyword rankings and conversion rates.'

Include natural synonyms users would say — 'app keywords', 'store listing', 'app ranking', 'app visibility' — to strengthen trigger term coverage toward a 5.

DimensionReasoningScore

Specificity

The description names a precise domain ("App Store Optimization (ASO)... on Apple App Store and Google Play Store") and three actions — "researching, optimizing, and tracking mobile app performance" — but those verbs are broad categories rather than concrete operations; it never mentions the skill's actual artifacts (keywords, metadata, screenshots, store listings). This matches the score-3 anchor ('names domain and 1-2 concrete actions, but not comprehensive') and falls short of score 4, which requires several specific actions like 'extracts text, fills forms, converts pages to images'.

3 / 5

Completeness

The 'what' is clearly stated ("Complete App Store Optimization (ASO) toolkit for researching, optimizing, and tracking mobile app performance") but there is no 'Use when...' clause or any equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' half is specific and well-formed, not vague.

3 / 5

Trigger Term Quality

"App Store Optimization (ASO)", "Apple App Store", "Google Play Store", and "mobile app performance" are natural phrases users would actually say, giving good keyword coverage with the acronym synonym included. It is not a 5 because common variations users would naturally use — "app keywords", "app ranking", "store listing", "app visibility", "app downloads" — are absent, matching the score-4 anchor ('good keyword coverage; a few natural terms missing').

4 / 5

Distinctiveness Conflict Risk

ASO on the two specific stores is a clear niche with distinctive terminology, so it is unlikely to trigger the wrong skill. It stops short of 5 because "tracking mobile app performance" overlaps with general mobile-analytics and app-marketing skills, matching the score-4 anchor ('mostly distinct; minor overlap risk with closely related skills').

4 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

agent-skills-hub/agent-skills-hub

Path

skills/app-store-optimization/SKILL.md

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.