Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Android App Launch: From Finished Build to Google Play

    1

    This skill turns that last mile into a procedure your agent follows, with a gate at every external service and a ledger that survives restarts.

    $12.99

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Android App Launch: From Finished Build to Google Play

    Android App Launch: From Finished Build to Google Play

    Example session with this skill installed

    Take my Android app in ./NotesApp to a Google Play production release. It already builds. Set up Firebase with Crashlytics and Remote Config, add AdMob banner and interstitial, tag the build and prepare the Play submission. Ask me before you submit anything.

    • Read your context and instructions
    • Compiled the android app launch

    Launch status: NotesApp 1.4.0 (versionCode 12)

    Stage reached: Play submission prepared, waiting for your approval to send for review.

    Conformance matrix (release gate)

    AreaStatusEvidence
    Firebase bootstrapPassRelease build on device logs Firebase init; Crashlytics test crash received
    Remote ConfigPass6 keys published with in-app defaults; fetch verified on release build
    AdMobPassLive unit IDs in release only; debug uses Google test inventory
    Consent (UMP)PassForm shown on first launch in EEA test geography
    Analytics privacyPassNo user content or device identifiers in event params
    targetSdkPass36

    Release build

    • :app:testReleaseUnitTest, :app:lintRelease, :app:bundleRelease: all passed
    • AAB: 18.4 MB, SHA-256 recorded in launch-ledger.json
    • Native libraries: none, so no 16 KB page-size risk

    Git

    • Tag notes-v1.4.0-12 created on commit a41c9e2 and pushed before upload

    Play Console (prepared, not submitted)

    • Internal testing release created and AAB uploaded; versionCode 12 accepted
    • Data safety: updated for Crashlytics and AdMob (device identifiers, crash logs)
    • Advertising ID declaration: Yes, answered from the merged manifest
    • New blocker after processing: Foreground Service declaration for dataSync. Draft answer and a 30-second reviewer video script are in docs/fgs-declaration.md

    Needs you

    1. Approve sending the release for review (I have not clicked Submit).
    2. Record the reviewer video from the script, or tell me to skip FGS and remove the service.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The hard part of an Android launch usually comes after the code is finished: a version code that was already burned by an old upload, a Foreground Service declaration Play only asks for after processing, Firebase that quietly never initialised, test ad IDs left in a release build, a store listing nobody re-checked after "Save".

    This skill turns that last mile into a procedure your agent follows, with a gate at every external service and a ledger that survives restarts.

    What your agent does

    • Audits the app first. It builds a conformance matrix against your own app standard, or against the baseline standard that ships with the skill. Irreversible items must be closed before release, and every open row is reported by name.
    • Sets up the Google stack properly. Firebase project, GA4 custom definitions, Remote Config keys and defaults, Firestore rules, App Check, Cloud Messaging and AdMob, each with read-back verification.
    • Builds and proves the release. Release unit tests, lint, assembleRelease and bundleRelease, then the AAB's size and SHA-256 go into the ledger.
    • Tags before it uploads. Every build is tagged <app>-v<versionName>-<versionCode> so the version live on Play always maps to an exact commit.
    • Handles Play Console. Upload, release notes, Data safety, Advertising ID, Foreground Service and package-visibility declarations, each answered from what the merged manifest really contains.
    • Reports the real state. "Uploaded", "in review", "approved" and "live" are different things, and the skill reports the one it actually verified.

    Built-in guard rails

    • It stops before anything irreversible (submitting, publishing, rolling out) and asks you.
    • It never writes keys, keystore passwords or service-account JSON into files or chat. You sign in yourself when a service asks.
    • A launch-config validator catches placeholder values and secret-looking fields before they can reach a release.
    • Optional stages (YouTube, website, Search Console) are skipped cleanly when you don't want them.

    What's inside

    • SKILL.md with the full procedure and stage gates
    • A baseline app stack standard you can copy into your project and adapt
    • 10 more reference guides: Firebase/GA4/AdMob, Play release, git tagging, credentials and authorization, marketing assets, config schema, quick start and lessons from real launches
    • 2 Python validators (launch config and launch ledger) plus JSON schema and example files

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Mobile Development.

    Needs an Android app that already builds with Gradle. You sign in to Play Console, Firebase and AdMob yourself; the skill never handles passwords, 2FA or CAPTCHAs. Console steps work best with a browser tool such as Playwright MCP. Section numbers refer to the bundled baseline standard, so map them if you use your own.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    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 today

    Accounts
    Google Play Console developer account
    Software
    GitAndroid project that builds with GradlePython 3.9+
    Optional
    Firebase / Google Cloud projectAdMob accountPlaywright

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    No. The skill ships a baseline standard you copy into your project and adjust. If you already have one, it uses yours.

    No. Submit, publish and rollout steps always stop for an explicit yes.

    No. Signing stays in your own Gradle setup or keystore storage, and you sign in to the consoles yourself.

    New in Mobile Development