I
Google Play Store
Verified@ivangdavila
npx machina-cli add skill @ivangdavila/play-store --openclawFiles (1)
SKILL.md
3.5 KB
When to Use
User needs to prepare, publish, or optimize an Android app for Google Play. Agent handles listing content, screenshots specs, ASO strategy, policy checks, and release planning.
Quick Reference
| Topic | File |
|---|---|
| Listing requirements | listing.md |
| ASO strategy | aso.md |
| Policy compliance | policies.md |
Core Rules
1. Listing Content Essentials
| Field | Limits | Tips |
|---|---|---|
| Title | 30 chars | Primary keyword + brand |
| Short description | 80 chars | Hook + main value prop |
| Full description | 4000 chars | Keywords natural, features, social proof |
| Screenshots | 2-8 per device | First 2 visible in search, make them count |
| Feature graphic | 1024x500 px | Required, no text smaller than 24pt |
2. Screenshot Specifications
| Device | Min dimensions | Aspect ratio |
|---|---|---|
| Phone | 320-3840 px | 16:9 or 9:16 |
| Tablet 7" | 320-3840 px | 16:9 |
| Tablet 10" | 1080-7680 px | 16:9 |
| Wear | 384-3840 px | 1:1 |
| TV | 1920x1080 | 16:9 |
Max 8 screenshots per device type. First 2 are hero shots.
3. ASO Keyword Strategy
- Title: Most weight, 1-2 primary keywords
- Short description: Supporting keywords, action-oriented
- Full description: Long-tail variations, 3-5 natural mentions
- Never: Keyword stuffing, competitor names, misleading claims
- Track: Organic installs, search visibility, keyword rankings
4. Policy Red Flags
Avoid these or face rejection/removal:
- Misleading functionality claims
- Sexual content or nudity
- Violence beyond ESRB T equivalent
- User data collection without privacy policy
- Deceptive install tactics
- Impersonation of other apps/brands
- Gambling without proper licensing
5. Release Strategy
| Release type | When to use |
|---|---|
| Internal testing | Team only, immediate |
| Closed testing | Invited testers, 12hr review |
| Open testing | Public beta, indexed in store |
| Production | Full release, staged rollout recommended |
Staged rollout: Start 5-10%, monitor crashes/ANRs, expand gradually.
6. Content Ratings
- Fill IARC questionnaire honestly
- Ratings affect visibility in some regions
- Under-rating = policy violation
- Re-submit if content changes significantly
7. Pre-Launch Checklist
Before any release:
- All store listing fields complete
- Privacy policy URL valid and accessible
- Content rating applied
- Target API level meets current requirements (API 33+)
- 64-bit support included
- App bundle format (.aab), not APK
- Deobfuscation files uploaded
Common Traps
- Generic screenshots → Low conversion. Show actual UI with value props overlaid.
- Ignoring tablet screenshots → Missed visibility on tablets and Chromebooks.
- Keyword in developer name → Policy violation, can get suspended.
- Missing privacy policy → Instant rejection if app requests any permissions.
- Low target API → Apps must target API 33+ for new submissions.
- APK instead of AAB → Required since 2021, AAB enables dynamic delivery.
- Ignoring ANR rate → >0.47% ANR rate triggers bad quality warnings.
- Changelog copy-paste → Users notice, hurts trust. Be specific about changes.
Overview
This skill helps you publish and optimize Android apps on Google Play, covering listing optimization, ASO keywords, and policy compliance. It guides you through preparing listing content, screenshots, and release planning to maximize visibility and installs.
How This Skill Works
The skill analyzes listing fields (title, short and full descriptions, screenshots, and feature graphic), applies an ASO keyword strategy, and runs policy checks. It then plans the release path (internal, closed, open, production) with a staged rollout and release timing to optimize visibility and compliance.
When to Use It
- When you need to prepare, publish, or optimize an Android app for Google Play.
- When you must optimize listing fields (title, descriptions, screenshots) and ASO keywords.
- When ensuring policy compliance and privacy requirements before submission.
- When planning a staged release or rollout (internal, closed, open, production).
- When addressing common listing pitfalls and compliance gaps.
Quick Start
- Step 1: Prepare listing assets (listing.md), ASO plan (aso.md), and policies (policies.md).
- Step 2: Validate assets against guidelines (title length, descriptions, screenshots, privacy policy).
- Step 3: Publish using a staged rollout (internal/closed/open) and monitor performance.
Best Practices
- Anchor the title with the primary keyword and brand.
- Craft a hooky short description that conveys the main value prop.
- Write a natural full description with 3-5 long-tail keyword mentions.
- Use 2-8 device-specific screenshots and make the first two hero shots count.
- Ensure policy and technical readiness: API 33+, AAB format, privacy policy, and honest claims.
Example Use Cases
- Launch a productivity app with a refreshed title, updated ASO keywords, and 3 new screenshots plus a 1024x500 feature graphic.
- Update an e-commerce app to target API 33+ and submit as an AAB, with a compliant privacy policy added.
- Run a public beta (open testing) before production to gather feedback and adjust listings.
- Remove keyword stuffing, replacing with natural long-tail mentions in the full description.
- Improve listing through enhanced hero shots and social proof in the description to boost conversions.
Frequently Asked Questions
Add this skill to your agents
