Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Release Cadence for Many Apps (Flutter & React Native)

    1

    For one account with several Flutter, React Native or Expo apps: picks today's app for review, runs the pre-release gates on it, and paces submissions so Apple's spam rule never sees a burst.

    $15

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Release Cadence for Many Apps (Flutter & React Native)

    Release Cadence for Many Apps (Flutter & React Native)

    Example session with this skill installed

    What update should I push today?

    • Read your context and instructions
    • Compiled the release cadence

    What the skill printed

    An offline run of the queue

    workspace ~/apps  (1 local app folders, log present)
    
    ios:
      updates in flight  0/1  -
      new apps in flight 0/1  -  (clean streak 0)
      updates today      0/1  -
      last submission    -
    
    android:
      updates in flight  0/1  -
      new apps in flight 0/1  -  (clean streak 1)
      updates today      1/1  row-counter 1.0.0+3
      last submission    row-counter 1.0.0+3 (2026-10-05)
    
    (offline: App Store Connect not read; iOS slots come from the log)
      row-counter                pubspec 1.0.0+3      dirty   0  ios com.example.rowcounter
    
    Play review state is not readable without a login: confirm in Play Console > Publishing overview before using the android slot.
    

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

    About this skill

    If one developer account holds a lot of similar apps, a burst of submissions is what invites guideline 4.3 spam rejections, and a run of those puts the account at risk. Apple sets no submission limit, so the pacing is up to you.

    This skill keeps a cadence so each release gets a clean review. Defaults, all in a config file:

    • One update and one new app in review per store at a time. An approved version waiting for manual release still counts as in review.
    • At most one update submitted per store per day.
    • A second new-app slot only after 3 approvals in a row with no 4.3 rejection.
    • Never two similar apps in review together (you say which apps are alike).
    • No update for its own sake: an app with nothing user-facing since its live version is skipped.

    Each day it reads your App Store Connect state and your own release log, then says which app may take today's slot. --since-build checks whether a TestFlight build is current with the code. On the chosen app it runs the gates in order (bug-hunt, polish, perf, app-similarity, listing-accuracy) and a Firebase Test Lab Robo crawl that counts its own runs and stops at the free daily quota. It tells you to look at the crawl's screenshots, since a crawl stuck on the first screen still reports SUCCESS. Then it stops and asks before submitting anything.

    It works across Flutter, React Native and Expo apps in the same folder. It finds React Native and Expo apps by their package.json, reads bundle ids and versions from app.json or app.config, the Xcode project or Gradle, and gives the build step per stack: eas build and eas submit for Expo, Gradle and Xcode for bare React Native, flutter build for Flutter. The Test Lab crawl finds React Native build outputs and sends an app bundle when there is no APK.

    What you need: Claude Code, Python 3.9+, git, openssl, and the build tools for your stack (Flutter, Gradle and Xcode, or the EAS CLI). An App Store Connect API key for live review state (or --offline). The Firebase CLI for Test Lab crawls.

    Part of the Indie Mobile Release Pipeline (Flutter & React Native) bundle ($39 for four skills: new-app, bug-hunt, ship-ios, daily-update).

    I build small apps on my own and have a shelf of them on the App Store and Google Play. I wrote this after learning how App Review treats a burst of similar apps from one account.

    • Play review state has no public read without a login, so the Android slot comes from your log and needs a check in Play Console.
    • The Test Lab counter sees only its own runs, not runs started elsewhere on the same Firebase project.
    • The gates are other skills; without them installed, you run those checks yourself.
    • Built for several apps on one account. With one app it adds little.
    • EAS cloud builds are not downloaded for you; pass the APK or AAB with --apk for a Test Lab crawl. Expo app.config.js is read by pattern, not executed.

    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 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 1 month ago

    Requires

    Google Account
    Apple
    Googleapis
    Python

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    api.appstoreconnect.apple.com
    testing.googleapis.com
    serviceusage.googleapis.com
    storage.googleapis.com
    toolresults.googleapis.com
    console.firebase.google.com

    File Scopes

    your
    apps
    folder/**

    - Tools: Read, Write, Edit, Bash (python3, git, openssl, firebase; flutter, gradle, xcodebuild or eas depending on the app) - Files: reads your apps' folders and the workspace config; writes a release log in the workspace folder - Network: `update_queue.py` reads `api.appstoreconnect.apple.com` with your own key (read only). `testlab_robo.py` calls Google's Testing, Tool Results, Service Usage and Cloud Storage APIs with the token the Firebase CLI saved at login, sent only to `*.googleapis.com`.

    Listed1 month ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    Not much. It is built for a handful of apps or more on one account.

    It counts its own runs and stops at the free daily quota. `--dry-run` shows the plan and the quota left first.

    Yes, every limit is in the config file.

    No. It stops and asks before every submission.

    New in Mobile Development