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.

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

90%

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

A token-efficient, highly actionable ASO skill body driven by comparison tables, concrete examples, and copy-paste output templates. Main gaps are the absence of explicit validate→fix→retry feedback loops and a long single-file structure that could externalize reference material into bundle files.

Suggestions

Add an explicit validate→fix→retry feedback loop to the listings/experiments workflow (e.g., re-check indexed keywords after publishing and iterate), to raise workflow_clarity.

Move dense reference tables (character limits, iOS-vs-Play comparison, Appeeky API details) into bundle files under references/ and link to them, reducing the single-file body length for better progressive disclosure.

Trim the opening 'You are a Google Play ASO expert' framing line to tighten conciseness further.

Dimension	Reasoning	Score
Conciseness	Dense, table-driven reference material (char limits, indexing weights, iOS-vs-Play comparison) plus concrete ✅/❌ examples and output templates earn their tokens; only the single opener 'You are a Google Play ASO expert' is mild padding that could be trimmed.	3 / 3
Actionability	Provides copy-paste-ready scaffolds: a full-description structure block, Appeeky API calls (GET /v1/keywords/metrics...), a listing-draft template, and an audit scoring rubric (1–10 per field), matching the fully-executable anchor.	3 / 3
Workflow Clarity	The 'Initial Assessment' and ratings-strategy sections give clear numbered sequences, and experiments have a validation threshold ('minimum 7 days or 1,000 impressions'), but there is no explicit validate→fix→retry feedback loop. Not 3 because error-recovery checkpoints are absent; not 2 because sequences are explicit and a guardrail is present.	2.5 / 3
Progressive Disclosure	Well-organized into clear sections with a one-level 'Related Skills' footer and no nested references, but the ~190-line single-file body holds reference-style tables and API details that could be offloaded to bundle files for better progressive disclosure. Not 3 because of length and unsplit reference content; not 2 because organization and navigation are solid.	2.5 / 3
	Total	11 / 12 Passed

Description

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.

A strong, well-structured description that clearly states capabilities, provides explicit 'Use when' triggers with natural keyword coverage, and disambiguates from sibling iOS skills. Written in appropriate third-person voice with no vague fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete optimization targets — 'title, short description, full description, keywords, ratings' — plus 'keyword, creative, or ratings strategy', matching the level-3 anchor of several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('optimize their Google Play Store listing...') and when ('Use when the user mentions...') with explicit trigger guidance, satisfying the level-3 anchor.	3 / 3
Trigger Term Quality	Natural user phrasings are densely covered: 'Google Play', 'Android', 'Play Store', 'Play Console', 'short description', 'full description indexed', 'Google Play ASO', giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped clearly to Google Play with explicit iOS disambiguation ('For iOS App Store optimization, see aso-audit and metadata-optimization'), giving a clear niche unlikely to trigger the wrong skill.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

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: Eronred/aso-skills
Path: skills/android-aso/SKILL.md
Commit: f97c943

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.