CtrlK
BlogDocsLog inGet started
Tessl Logo

android-aso

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

72

Quality

88%

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

82%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 dense, actionable ASO reference that leads with tables, concrete limits, examples, executable API calls, and copy-paste output templates rather than concept explanation. Main weaknesses are minor over-explanation in a few framing lines and the absence of an explicit validate/retry feedback loop in the workflow.

Suggestions

Trim framing fluff (e.g., "You are a Google Play ASO expert..." and "First thing users read on search results") to lift conciseness toward anchor 5.

Add an explicit validation/retry loop for Play Store Experiments — e.g., after the 7-day/1,000-impression run, check significance and iterate — to strengthen workflow_clarity.

Consider splitting the per-field optimization detail (Title/Short/Full description guidance) and output templates into a reference bundle file so SKILL.md reads as a tighter overview, improving progressive_disclosure.

DimensionReasoningScore

Conciseness

Mostly lean and dense with tables, char limits, and templates rather than padded prose, but includes minor over-explanation such as the "You are a Google Play ASO expert" opener and "First thing users read on search results" that could be trimmed; not quite the every-token-earns-its-place anchor 5.

4 / 5

Actionability

Highly concrete and executable: exact char limits (30/80/4000), ✅/❌ copy examples, API calls (GET /v1/keywords/metrics...), a named Play API (ReviewManager.requestReviewFlow()), and copy-paste-ready output templates covering the common listing and audit cases.

5 / 5

Workflow Clarity

Clear sequenced intake ("Initial Assessment" 1–5) and ratings steps with implicit checkpoints (keyword density 3–5×, "minimum 7 days or 1,000 impressions", per-field audit scoring), but lacks an explicit validate-then-fix feedback loop, keeping it just below anchor 5.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with a "Related Skills" block pointing to sibling skills at one level; however the body is a ~190-line single file with no bundle files to split detail into, so it does not reach the appropriately-split anchor 5.

4 / 5

Total

17

/

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-scoped description that clearly states what the skill does, when to use it via natural trigger terms, and how it differs from sibling iOS skills. The only minor gap is that concrete actions are expressed as one verb applied to many objects rather than several distinct action verbs.

DimensionReasoningScore

Specificity

Lists several concrete optimization targets — "title, short description, full description, keywords, ratings, or Play Store-specific features" plus "keyword, creative, or ratings strategy" — but uses a single verb ("optimize") rather than multiple distinct concrete actions, so it sits just below the comprehensive multi-action anchor 5.

4 / 5

Completeness

Explicitly answers both what ("optimize their Google Play Store listing — title, short description, full description, keywords, ratings...") and when ("Use when the user mentions 'Google Play', 'Android'...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger coverage including synonyms users actually say: "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", and "Google Play ASO".

5 / 5

Distinctiveness Conflict Risk

Clear niche (Google Play ASO) with distinct triggers and active disambiguation from iOS skills — "For iOS App Store optimization, see aso-audit and metadata-optimization" — minimizing conflict risk.

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.