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
Most recently taken up by
- appeeky/aso-skillsword for word, first seen Feb 27, 2026
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.
Other versions1 project uses a version of this.
Word for word · 1
- appeeky/aso-skills★ 2.2k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- ab-test-store-listingSkill
- app-analyticsSkill
- app-clipsSkill
- app-icon-optimizationSkill
- app-launchSkill
- apple-search-adsSkill
- app-marketing-contextSkill
- app-preview-videoSkill
- app-rejection-recoverySkill
- app-store-featuredSkill
- asc-metricsSkill
- aso-auditSkill
- aso-routerSkill
- attribution-setupSkill
- category-positioningSkill
- competitor-analysisSkill
- competitor-trackingSkill
- crash-analyticsSkill
- creator-ugc-marketingSkill
- custom-product-pagesSkill
- in-app-eventsSkill
- keyword-researchSkill
- localizationSkill
- market-moversSkill
- market-pulseSkill
- metadata-optimizationSkill
- monetization-strategySkill
- onboarding-optimizationSkill
- paywall-optimizationSkill
- press-and-prSkill
- rating-prompt-strategySkill
- referral-programSkill
- retention-optimizationSkill
- review-managementSkill
- screenshot-optimizationSkill
- seasonal-asoSkill
- subscription-lifecycleSkill
- ua-campaignSkill
- web-to-app-funnelSkill
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
- Distinctive: line 38
Ask: Do you have Play Console access?
- Distinctive: line 39
Ask: What is your current title and short description?
- Distinctive: line 40
Ask: What are your 3 most important keywords?
- Distinctive: line 41
Ask: What category is your app in?
- Distinctive: line 56
Do not repeat the title's primary keyword
- Distinctive: line 89
Use Appeeky keyword tools, then adapt for Play:
- Very specific: line 117
Use review-management skill for response templates
- Very specific: line 122
Use the Play In-App Review API: ReviewManager.requestReviewFlow()
- Distinctive: line 139
Use Early Access to:
≈ “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.
Files
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
| Factor | Google Play | Apple App Store |
| Keyword indexing | Title + 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 |
| Ratings | Continuous — never reset | Reset per version (can request reset) |
| A/B testing | Play Store Experiments (native) | Product Page Optimization |
| Screenshots | 2–8 per language | Up to 10 per language |
| Feature graphic | Required (1024×500px) | Not applicable |
| Algorithm signals | Installs, engagement, ratings, keywords | Keyword match, ratings, conversions |
| Review indexing | Reviews and replies indexed | Not indexed |
Character Limits
| Field | Limit | Indexed | Weight |
| Title | 30 chars | ✓ | Highest |
| Short description | 80 chars | ✓ | High |
| Full description | 4000 chars | ✓ | Medium |
| Developer name | — | ✓ | Low |
Initial Assessment
- Check for
app-marketing-context.md - Ask: Do you have Play Console access? (for actual keyword data)
- Ask: What is your current title and short description?
- Ask: What are your 3 most important keywords?
- 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=usPlay-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:
- Respond to every 1–3 star review (boosts score algorithmically)
- Reply invites re-rating — users can update their review
- Use
review-managementskill for response templates - 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 ratingrating-prompt-strategy— In-App Review API timing and strategyab-test-store-listing— Play Experiments methodologylocalization— Per-language listing optimization
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
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.

