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).
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionandroid-asoExecute the skills CLI command in your project's root directory to begin installation:
Fetches android-aso from eronred/aso-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate android-aso. Access via /android-aso in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
696
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
696
stars
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).
| 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 |
| Field | Limit | Indexed | Weight |
|---|---|---|---|
| Title | 30 chars | ✓ | Highest |
| Short description | 80 chars | ✓ | High |
| Full description | 4000 chars | ✓ | Medium |
| Developer name | — | ✓ | Low |
app-marketing-context.mdBrand – Keyword DescriptorStructure 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.
Google Play indexes descriptions per language. Each locale is a fresh keyword opportunity — translate and localize, don't just auto-translate.
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:
Required for Play Store. Appears at the top of your listing when no video is present.
Unlike iOS, Play ratings are never reset — every rating ever given counts.
To improve your rating:
review-management skill for response templatesRating prompt timing (see also rating-prompt-strategy skill):
ReviewManager.requestReviewFlow()Native A/B testing for:
Access: Play Console → Store listing experiments
Test one element at a time. Run for minimum 7 days or 1,000 impressions.
Use Early Access to:
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]
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]
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 optimizationMake data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
android-aso has been reliable in day-to-day use. Documentation quality is above average for community skills.
android-aso fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added android-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
android-aso reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: android-aso is focused, and the summary matches what you get after install.
Registry listing for android-aso matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend android-aso for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in android-aso — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
android-aso has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added android-aso from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 45