CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

aso

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

92%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 well-engineered audit skill: an actionable phased workflow with fallbacks, concrete platform-specific data, and a clean one-level reference structure. The only improvement opportunity is consolidating facts duplicated between the Phase 1 field lists and the Key Facts sections.

DimensionReasoningScore

Conciseness

Nearly all content is non-redundant, hard domain data Claude cannot be assumed to know (byte-vs-char keyword field, Vitals thresholds, per-store limits, tier rules); minor trimming is possible where the Phase 1 field lists and "Key Facts" sections repeat limits (30-char title, 170-char promo text). Anchor 4 rather than 3 because the padding is incidental duplication, not explanation of known concepts.

4 / 5

Actionability

Fully concrete instruction-only guidance: exact URL patterns, ready-to-use search strings, explicit tier thresholds and examples, dimension weights, grade bands, tier-aware checklist, and report rules ("Change subtitle from X to Y" not "Improve subtitle"). Matches anchor 5's fully executable coverage.

5 / 5

Workflow Clarity

Clear phased sequence (identify/fetch → tier assessment → score → optional competitors → report) with explicit fallback checkpoints ("If WebFetch returns incomplete data… note gaps", "If browser tools are unavailable, ask the user to share a screenshot", "If you cannot confirm its presence, note this"). No destructive or batch operations, so the validation cap does not apply; anchor 5.

5 / 5

Progressive Disclosure

The body is an overview that clearly signals five one-level-deep reference files, each annotated with its purpose; verified the referenced files exist and contain no nested references. Appropriate content split with easy navigation — anchor 5.

5 / 5

Total

19

/

20

Passed

Description

81%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, trigger-rich description with excellent natural-language coverage and explicit use conditions. Its only weakness is a thin "what" — it says the skill audits/optimize listings but not what that involves or delivers.

Suggestions

Add one sentence stating what the audit does and delivers, e.g. "Fetches live listing data, scores it across 6 dimensions, and produces a prioritized action plan" — this would lift specificity and completeness toward 5.

Mention the competitor-comparison and platform (Apple vs Google) coverage as part of the "what", not only as triggers, so the description's capability statement matches the skill's full scope.

DimensionReasoningScore

Specificity

"audit or optimize an App Store or Google Play listing" names the domain with 1-2 concrete actions, matching anchor 3; it omits what the audit produces (scoring dimensions, report, action plan), so it is not the several-action coverage of anchor 4.

3 / 5

Completeness

Both "what" (audit/optimize a store listing) and a highly explicit multi-clause "when" are present; the "what" is a single thin clause that never states the scoring or deliverables, so it falls short of anchor 5's concrete what-plus-when but exceeds anchor 3's weak implied when.

4 / 5

Trigger Term Quality

Comprehensive natural triggers including user-voice phrasing ("why aren't people downloading my app", "improve my app conversion"), synonyms ("ASO audit", "app store optimization"), competitor comparison, and URL sharing — clearly anchor 5.

5 / 5

Distinctiveness Conflict Risk

Clear niche (mobile store listing optimization) with distinct, unambiguous triggers; no realistic overlap with generic marketing or web-landing-page skills, matching anchor 5.

5 / 5

Total

17

/

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

coreyhaines31/marketingskills

Path

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