- Home
- Skills
- Mobile Development
- Google Play Launch Kit
More screenshots
Works with the AI Agents you already use
Google Play Launch Kit
This pack bundles 8 skills that walk your agent through all of it, in order.
$5
Google Play Launch Kit
Example session with this skill installed
My Expo game runs fine on the emulator. I want it on Google Play: testers first, then production. It has AdMob rewarded ads and should be in English and French.
- Read your context and instructions
- Compiled the google play launch
Launch plan for your Expo game
I loaded google-play-launch and checked your project first. Pre-flight before anything public:
| Check | Status | Note |
|---|---|---|
| Package name | ⚠️ com.anonymous.mygame | Permanent on Play. Suggest io.<yourbrand>.mygame now |
| Asset licences | ⚠️ 1 sound is CC BY-NC | Cannot ship with ads; replace it or remove ads |
| Developer account | ❓ | Personal account after Nov 2023 → 12 testers / 14-day closed test before production |
| Privacy policy | ❌ missing | Required for AdMob; I can publish one on Google Sites |
| Target age | 13+ | Keeps you out of the Families policy |
Steps (one commit each)
AdMob (admob-integration): UMP consent before MobileAds().initialize(), test ad units in dev, rewarded + interstitial capped at 1 per 3 min, privacy-options entry in settings.
2.
Visuals (store-screenshots): showcase save, captures EN + FR on phone and tablet, captioned mockups, 1024x500 feature graphic, 512 icon → store/.
3. Listing (store-listing-i18n): store/listing.json in en-US and fr-FR, validated:
$ node check-listing.mjs
en-US title 22/30 short 74/80 full 1912/4000 ✓
fr-FR title 22/30 short 79/80 full 2140/4000 ✓
Play Console (play-console-app-setup): create the app, then app access, ads = yes, advertising ID = yes (AdMob), IARC, target audience 13+, data safety mapped from your SDKs (AdMob → device ID, diagnostics, shared for advertising).
5. First release (android-play-release):
$ node release.mjs init && node release.mjs keystore
$ node release.mjs bump none && node release.mjs build
$ node release.mjs smoke # R8 release on emulator: launch OK, no crash
Then internal testing track,
send all changes for review (new apps stay invisible to testers until then), share the tester link.
6. Production: staged rollout after review, then link the app in AdMob and publish app-ads.txt.
Next steps
- Confirm the final package name and replace the CC BY-NC sound.
- Tell me which Google account owns the Play developer account, and I'll start with AdMob.
Connects securely to your tools. The creator never sees your data.
About this skill
Getting an Expo / React Native app onto Google Play is not one task, it is about thirty: a permanent package name, an upload key, screenshots in every language, a listing that respects Play's metadata rules, a dozen Play Console declarations (data safety, IARC, target audience, advertising ID...), AdMob with GDPR consent, then a signed AAB that does not crash once R8 is on.
This pack bundles 8 skills that walk your agent through all of it, in order. It was born from shipping a real game end to end (Brainrot Slayer, live on Google Play), and every pitfall hit along the way is written down in the skills.
What's inside
| Skill | What it does |
|---|---|
google-play-launch | The end-to-end playbook: pre-flight checks (final package name, asset licences, third-party IP, account type), then every step in order, plus a troubleshooting map |
store-screenshots | Showcase-state captures on the Android emulator (all languages, phone + tablet, clean status bar) and config-driven captioned mockups, 1024x500 feature graphic and 512 px icon |
store-listing-i18n | Multilingual title / short / full description following Play metadata rules, a validator script, and per-language entry of texts and localized graphics |
play-console-app-setup | Create the app and fill every declaration: app access, ads, advertising ID, target audience, IARC content rating, data safety (mapped from your SDKs), category, contact, testers, send for review |
google-console-browser | How to drive Play Console / AdMob / Google Sites from the browser reliably: right Google account, shadow-DOM helpers, file uploads one by one, save verification |
admob-integration | Compliant AdMob: UMP consent before init, test ads in dev, rewarded + capped interstitials, GDPR message, privacy policy template published on Google Sites, store linking |
android-play-release | Upload key + Expo signing config plugin, version bump, patch notes in every language, signed AAB, R8 release smoke test on the emulator, tag + PR, track release |
expo-android-emulator | Dev builds on the macOS emulator: JDK/NDK, Metro port conflicts, "Unable to load script", storage full, per-app locale |
Scripts included
release.mjs:init | status | bump | notes-check | keystore | build | smoke(keys live outside the repo, passwords never printed)render-mockups.mjs+android-capture.sh: config-driven store visuals from emulator capturescheck-listing.mjs: title 30 / short 80 / full 4000 limits and policy checkswith-release-signing.js: Expo config plugin for release signing- Templates: AdMob ads module, privacy policy (FR/EN)
Safe by design
The agent always asks before legal declarations, sending for review or publishing. Nothing is submitted to Google on your behalf without your OK.
Requirements
macOS with Android Studio (JBR 17/21, SDK, an emulator), Node 20+, Google Chrome, an Expo (CNG) project. Driving the Google consoles with file uploads needs a browser-automation tool such as Claude in Chrome.
MIT licensed. Source: https://github.com/lucasfanech/google-play-launch-kit
macOS only (the emulator and capture scripts rely on Android Studio's JBR 17/21 and macOS tools such as sips). Built for Expo (CNG) projects; bare React Native works but some steps need adapting. Uploading files to the Google consoles needs a browser-automation tool that supports uploads, such as Claude in Chrome. The final AAB upload and every legal declaration stay a human decision: the agent prepares and asks, it never submits on its own.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 17 days ago
Requires
Permissions
Allowed Hosts
File Scopes
Shell runs the Android emulator, adb, Gradle and the bundled Node scripts. File read/write edits the Expo project (app.json, plugins, store/). Browser drives Google Play Console, AdMob and Google Sites; the agent asks before any declaration, review submission or publish. The upload key is stored outside the repo (~/.android-keys) and its passwords are never printed.