Google Play Store
Publish, optimize, and scale Android apps on Google Play with release automation, ASO, policy compliance, and rejection recovery.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/ivangdavila/google-play-storeSetup
On first use, read setup.md for integration guidelines.
When to Use
User needs to publish, manage, or optimize Android apps on Google Play. Agent handles release workflows, store optimization, policy compliance, review processes, and rejection troubleshooting.
Architecture
Memory lives in ~/google-play-store/. See memory-template.md for structure.
~/google-play-store/
├── memory.md # Account, apps, preferences
├── apps/ # Per-app tracking
│ └── {package}/ # Package-specific notes
└── checklists/ # Saved submission checklists
Quick Reference
| Topic | File |
|---|---|
| Setup process | setup.md |
| Memory template | memory-template.md |
| Release tracks and rollouts | tracks.md |
| App Store Optimization | aso.md |
| Policy compliance | policies.md |
| Rejection recovery | rejections.md |
| Automation with Fastlane | fastlane.md |
Core Rules
1. Release Track Progression
| Track | Purpose | Review | Users |
|---|---|---|---|
| Internal | Daily builds, QA | None | 100 max |
| Closed | Beta testers | 2-6h | Email list |
| Open | Public beta | 2-6h | Anyone joins |
| Production | Full release | 2-24h | Everyone |
Mandatory progression for new apps:
Internal → Closed (20+ testers, 14+ days) → Production
Skip this = instant rejection. Start closed testing on day one.
2. Pre-Submission Checklist
Run before EVERY submission:
CONTENT
[ ] Privacy policy URL live and HTTPS
[ ] Data safety form 100% complete
[ ] Content rating questionnaire done
[ ] All screenshots show real app (no placeholders)
[ ] Feature graphic 1024x500 uploaded
TECHNICAL
[ ] Target SDK ≥ 34 (Android 14)
[ ] versionCode higher than ALL previous uploads
[ ] Signed with correct key
[ ] No hardcoded API keys in code
[ ] ProGuard/R8 not breaking functionality
TESTING (new apps only)
[ ] 20+ testers opted in (not just invited)
[ ] 14+ consecutive days completed
[ ] Crash-free rate > 99%
3. Version Code Strategy
versionCode must ALWAYS increase. Cannot reuse. Ever.
Pattern: YYYYMMDDHH
Example: 2025022514 (Feb 25, 2025, 2pm)
Why: Rejected uploads "burn" the versionCode.
Multiple builds per day need unique codes.
4. App Signing Models
| Model | Control | Recovery | Best For |
|---|---|---|---|
| Google-managed | Google holds key | Easy | New apps |
| Upload key | You sign, Google re-signs | Medium | Most apps |
| Self-managed | Full control | Hard | Enterprise |
Recommendation: Google-managed for new apps. Upload key for updates.
Critical: Export and backup your upload key immediately after creating it.
5. Staged Rollout Protocol
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-ivangdavila-google-play-store": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
Animations
Create performant web animations with proper accessibility and timing.
Arduino
Develop Arduino projects avoiding common wiring, power, and code pitfalls.
Bulgarian
Write Bulgarian that sounds human. Not formal, not robotic, not AI-generated.
Arabic
Write Arabic that sounds human. Not formal, not robotic, not AI-generated.
Assistant
Manage tasks, communications, and scheduling with proactive and organized support.