Play Store Kit — Development skill for Claude Code
Claude Code skill: take an Android app to Google Play and keep it there.
How to install Play Store Kit
This entry records only its repository, not the path inside it, so there is no
exact command to give. Open allexp1/play-store-kit and copy the folder into
~/.claude/skills/, or the file into ~/.claude/agents/.
What Play Store Kit does
Claude Code skill: take an Android app to Google Play and keep it there. Pre-check, App Bundle upload, review, staged rollout and recovery through the official Play Developer API, every live effect behind its own approval.
Alternatives in Development
- Implement Review — Run the implement-review staged-change review loop 239 ★
- Position Ladder — Position Ladder — Staged Entry & Cost-Basis Management 192 ★
- Learn Approve — Approve a staged learning change by ID 172 ★
README
Play Store kit
A skill for Claude Code that takes an Android app to Google Play, and keeps it there.
You say one sentence. It works step by step through the official Google Play Developer API, asks for a yes before each live effect, and stops only where Google needs you.
| You say | What happens |
|---|---|
| "Connect my Play account" | Walks you through a service account with app-scoped permissions, then records what it can actually do |
| "Put my app on Google Play" | Checks the built App Bundle against Play's current requirements, guides the first Console upload, then takes over through the API |
| "Manage my existing Play app" | Imports tracks and releases read-only and marks what the kit may touch |
| "Ship 1.4 to internal testing" | Uploads the signed AAB as a draft, sends it for review after your yes, and waits on Google's lifecycle state |
| "Roll out to 20 %", "halt", "promote" | One approved transition at a time, built from the live track so nothing else changes |
| "Did the commit go through?" | Reconciles a lost response from Google's own state before anything is retried |
| "Get production access" | Tracks the closed-test requirement from dated evidence and tells you the earliest day to apply |
| "Will Google accept my app?" | Target API per form factor, 64-bit, 16 KB alignment of every native library, signer, versionCode, download size, Billing Library, permissions, Data safety, GenAI rules |
Safety
- Approvals by effect. Uploading, distributing to testers, submitting to production and each rollout step are separate questions. Your reply is stored as a receipt bound to the exact plan; a changed plan needs a new yes.
- One edit owner. A lock, a persisted edit id with its expiry, and no edit is ever opened just to look at status.
- Commits never cancel a review in progress (
ERROR_IF_IN_REVIEW; Google's default would). - Nothing is retried blind. Every write is journaled; an unknown outcome is reconciled first.
- **Your keys
Related Skills
App Store Review Playbook
Everything learned shipping 8 apps to the App Store and Google Play - 15 rejections with root causes, build an
Plan Run
Execute one stage of a staged-rollout .plan/ — locate the stage, follow the project's own PLAN.md protocol, ve
Fusebase Health
Run the read-only health check. Reports CLI_LAYER_DRIFT, FLOW_LAYER_DRIFT, SHARED_MERGE_DRIFT, EXCEPTION_IN_EF
Rollout Compatibility
Keep a contract change safe while old and new versions run side by side
Beta
Upload a beta build (TestFlight / Play internal) after explicit confirmation
Elsewhere
Play Elsewhere — tick the world, deliver the briefing, take your orders
Related Agents
Flutter Android Deployment
Use this agent when deploying Flutter apps to Google Play Store. Specializes in Android app signing, Google Pl
Android Specialist
Top-level Android authority. Owns app architecture on Android, scoped storage, foreground services, Doze and A
07 React Native Deploy
React Native deployment expert - iOS/Android builds, App Store, Play Store, EAS, Fastlane, CodePush OTA