Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Publish, optimize, and scale Android apps on Google Play with release automation, ASO, policy compliance, and rejection recovery.
Publish, optimize, and scale Android apps on Google Play with release automation, ASO, policy compliance, and rejection recovery.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines.
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.
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
TopicFileSetup processsetup.mdMemory templatememory-template.mdRelease tracks and rolloutstracks.mdApp Store Optimizationaso.mdPolicy compliancepolicies.mdRejection recoveryrejections.mdAutomation with Fastlanefastlane.md
TrackPurposeReviewUsersInternalDaily builds, QANone100 maxClosedBeta testers2-6hEmail listOpenPublic beta2-6hAnyone joinsProductionFull release2-24hEveryone Mandatory progression for new apps: Internal โ Closed (20+ testers, 14+ days) โ Production Skip this = instant rejection. Start closed testing on day one.
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%
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.
ModelControlRecoveryBest ForGoogle-managedGoogle holds keyEasyNew appsUpload keyYou sign, Google re-signsMediumMost appsSelf-managedFull controlHardEnterprise Recommendation: Google-managed for new apps. Upload key for updates. Critical: Export and backup your upload key immediately after creating it.
Stage%DurationGateCanary1%24-48hCrashes < 0.1%Early5%48-72hANRs < 0.5%Mid20%72-96hRatings stableLate50%96-120hNo regressionsFull100%โAll clear Halt triggers: Crash spike, ANR spike, 1-star surge, critical bug reports.
ElementLimitImpactTitle30 charsHighestShort description80 charsHighFull description4000 charsMediumScreenshots8 per typeHighFeature graphic1024x500Medium Keyword strategy: Title: Primary keyword + brand Short desc: Top 3 keywords naturally Full desc: Long-tail throughout Update quarterly based on Search Console
ActionGoogle ResponseYour DeadlinePolicy email7 days to fixRespond in 3Appeal3-7 daysSubmit in 24hData request30 daysComplete in 14Critical issue24h suspensionImmediate Rule: Never ignore policy emails. Silence = admission.
Skipped closed testing โ Cannot release to production. 20 testers + 14 days mandatory for new apps. Data safety incomplete โ Instant rejection. Fill EVERY field even if "no data collected." Screenshots with mockups โ Rejection for misleading. Use real app screenshots only. Privacy policy 404 โ Rejection. Verify URL works before every submission.
versionCode not incremented โ Upload rejected. Even rejected uploads burn codes. Target SDK too old โ Rejection. Check current requirement before building. Forgot upload key password โ Cannot update app. Store password in password manager. ProGuard broke app โ Crashes after release. Always test release build.
Undeclared permissions โ Policy violation. Justify EVERY sensitive permission. Background location without need โ Rejection + strike. Remove or justify with video. Kids content undeclared โ Policy violation. If ANY appeal to children, declare it. Deceptive ads โ Suspension risk. Follow interstitial timing and close button rules.
No staged rollout โ Bad update hits everyone. Always start at 1%. Ignored policy email โ Escalation to strike. Respond within 3 days. Multiple accounts to evade โ Termination. One violation becomes account death.
Data that stays local: Package names and app status in ~/google-play-store/ Submission checklists and workflow notes Release history and lessons learned This skill stores ONLY non-sensitive metadata: App names and package identifiers Track status (internal/closed/production) Workflow preferences (manual vs CI/CD tool names) Checklist progress This skill does NOT store and will refuse: API keys, service account JSON content Keystore files or passwords OAuth tokens or Play Console credentials Any secret or credential material This skill does NOT: Upload apps or make network requests Access signing keys or certificates Execute Fastlane commands directly User manages all credentials in their CI/CD system and runs commands themselves. The Fastlane examples are documentation only.
Install with clawhub install <slug> if user confirms: android โ Android development app-store โ iOS and Android publishing mobile โ Cross-platform mobile
If useful: clawhub star google-play-store Stay updated: clawhub sync
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.