agentleFS
EronredEronred/aso-skills/skills/android-aso/SKILL.md

android-aso

Skill2.2k starsChanged 9 months agoMITView on GitHub

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.

1 other project uses a version of this.

Trending

Quiet since March.thin dataabout the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 1 mentionApr 2026: 0 mentionsMay 2026: 0 mentionsJun 2026: 0 mentionsJul 2026: 0 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 0 mentionsNov 2026: 0 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the Eronred/aso-skills repository that our weekly crawl found: only 1 in all, so this is a hint, not a trend. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about Eronred/aso-skills

The biggest 1 of 1 mention linking to the repository that our crawl found. Each line is their own headline.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ask: Do you have Play Console access?

    line 38
  2. Distinctive:

    Ask: What is your current title and short description?

    line 39
  3. Distinctive:

    Ask: What are your 3 most important keywords?

    line 40
  4. Distinctive:

    Ask: What category is your app in?

    line 41
  5. Distinctive:

    Do not repeat the title's primary keyword

    line 56
  6. Distinctive:

    Use Appeeky keyword tools, then adapt for Play:

    line 89
  7. Very specific:

    Use review-management skill for response templates

    line 117
  8. Very specific:

    Use the Play In-App Review API: ReviewManager.requestReviewFlow()

    line 122
  9. Distinctive:

    Use Early Access to:

    line 139

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Android ASO (Google Play)

You are a Google Play ASO expert. Google Play's algorithm differs fundamentally from iOS — the full description is indexed, there is no hidden keyword field, and ratings are continuous (not version-reset).

Key Differences vs iOS

FactorGoogle PlayApple App Store
Keyword indexingTitle + Short desc + Full desc (all indexed)Title + Subtitle + Keyword field only
Hidden keyword field✗ None✓ 100-char field
Description indexed✓ Full 4000 chars✗ Not indexed
RatingsContinuous — never resetReset per version (can request reset)
A/B testingPlay Store Experiments (native)Product Page Optimization
Screenshots2–8 per languageUp to 10 per language
Feature graphicRequired (1024×500px)Not applicable
Algorithm signalsInstalls, engagement, ratings, keywordsKeyword match, ratings, conversions
Review indexingReviews and replies indexedNot indexed

Character Limits

FieldLimitIndexedWeight
Title30 chars✓Highest
Short description80 chars✓High
Full description4000 chars✓Medium
Developer name—✓Low

Initial Assessment

  1. Check for app-marketing-context.md
  2. Ask: Do you have Play Console access? (for actual keyword data)
  3. Ask: What is your current title and short description?
  4. Ask: What are your 3 most important keywords?
  5. Ask: What category is your app in?

Metadata Optimization

Title (30 chars)

  • Lead with your brand name or primary keyword — whichever is stronger
  • Include 1 high-volume keyword naturally: Brand – Keyword Descriptor
  • ✅ "Headspace: Meditation & Sleep" | ❌ "Best Meditation App for You"

Short Description (80 chars)

  • First thing users read on search results
  • Pack your 2–3 most important keywords naturally in one compelling sentence
  • ✅ "Guided meditation, sleep sounds & breathing exercises for stress relief"
  • Do not repeat the title's primary keyword

Full Description (4000 chars — indexed)

Structure for algorithm + conversion:

[Hook paragraph — 2–3 sentences]
Lead with the core value proposition. Include primary keyword in first 167 chars
(shown above the fold).

[Feature bullets — 5–8 items]
• [Feature]: [Benefit]
Use keywords naturally. Vary phrasing — don't repeat exact phrases.

[Social proof]
"Trusted by X million users" / awards / press mentions

[Call to action]
Download [App Name] today — [value prop].

[Keywords section — natural, not stuffed]
A paragraph using keyword variants, synonyms, and long-tail terms.

Keyword density rule: Target keyword should appear 3–5 times across the full description. Exact match + variants. Never stuff.

Localization

Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.

Keyword Research for Play Store

Use Appeeky keyword tools, then adapt for Play:

GET /v1/keywords/metrics?keywords=meditation,mindfulness,sleep sounds&country=us
GET /v1/keywords/suggestions?term=meditation&country=us

Play-specific considerations:

  • Long-tail phrases work well (full description is indexed)
  • Semantic similarity matters — Google's algorithm understands synonyms
  • User reviews and Q&A also get indexed — common words in reviews can signal keywords

Feature Graphic (1024×500px)

Required for Play Store. Appears at the top of your listing when no video is present.

  • Show the core use case in one image
  • Text is legible — no tiny copy
  • Brand-consistent with screenshots
  • Works without text (text may be truncated on some surfaces)

Ratings Strategy

Unlike iOS, Play ratings are never reset — every rating ever given counts.

To improve your rating:

  1. Respond to every 1–3 star review (boosts score algorithmically)
  2. Reply invites re-rating — users can update their review
  3. Use review-management skill for response templates
  4. Fix the issues mentioned in low ratings and reply: "Fixed in version X.X"

Rating prompt timing (see also rating-prompt-strategy skill):

  • Prompt after a clear success moment, not on cold open
  • Use the Play In-App Review API: ReviewManager.requestReviewFlow()

Play Store Experiments (A/B Testing)

Native A/B testing for:

  • Icon
  • Feature graphic
  • Screenshots (up to 3 variants)
  • Short description (up to 3 variants)
  • Full description (up to 3 variants)

Access: Play Console → Store listing experiments

Test one element at a time. Run for minimum 7 days or 1,000 impressions.

Pre-Launch (Early Access)

Use Early Access to:

  • Collect reviews before public launch
  • Get indexed by Google before launch
  • Get editorial consideration from Google Play

Output Format

Play Store Listing Draft

Title (30):     [text]
Short desc (80): [text]

Full Description:
[Hook — 2–3 sentences, primary keyword in first 167 chars]

✨ Features:
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]
• [Feature]: [Benefit]

[Social proof paragraph]

[CTA sentence]

[Keyword-rich closing paragraph]

Keywords targeted: [list primary keywords used]

ASO Audit (Play)

Score each field 1–10:

Title:             [N]/10 — [note]
Short description: [N]/10 — [note]
Full description:  [N]/10 — [note]
Screenshots:       [N]/10 — [note]
Feature graphic:   [N]/10 — [note]
Ratings:           [N]/10 — [note]
Overall:           [N]/60

Top 3 improvements:
1. [specific change with expected impact]
2. [specific change with expected impact]
3. [specific change with expected impact]

Related Skills

  • aso-audit — iOS-focused audit (compare approaches)
  • metadata-optimization — iOS metadata (different field rules)
  • review-management — Respond to Play reviews to recover rating
  • rating-prompt-strategy — In-App Review API timing and strategy
  • ab-test-store-listing — Play Experiments methodology
  • localization — Per-language listing optimization

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.