mobile-store-orchestrator

Orchestrates Expo/React Native release pipelines for iOS and Android store submissions.

8|7|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/keep-starknet-strange/starkclaw --skill mobile-store-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-store-orchestrator
Source: https://github.com/keep-starknet-strange/starkclaw/tree/main/.claude/skills/mobile-store-orchestrator
Command: npx skills add https://github.com/keep-starknet-strange/starkclaw --skill mobile-store-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end release orchestration for mobile apps (Expo/React Native) targeting Apple App Store and Google Play, providing a repeatable process to prepare submissions, metadata, screenshots, and release checklists with minimal manual steps.

Core Features & Use Cases

  • Release orchestration: Automates the full store submission pipeline for iOS and Android, including readiness audits, metadata generation, and screenshot generation.
  • ASO and metadata: Generates app-store metadata drafts and localized assets to streamline store listing creation.
  • Submission readiness: Produces a complete submission packet and artifact set ready for review and upload in the stores.

Quick Start

Use the mobile-store-orchestrator to run a full release flow that audits readiness, builds metadata, generates screenshots, and compiles the submission packet for your app.

Frequently Asked Questions about mobile-store-orchestrator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate React Native app store submission for iOS and Android?

Automating app store submission involves running an orchestrated release pipeline that performs readiness audits, generates metadata, creates screenshots, and compiles a complete submission packet for both Apple App Store and Google Play.

What is the best way to generate ASO metadata for an Expo mobile app release?

Generating ASO metadata for an Expo release is handled by an orchestration pipeline that automatically drafts app-store metadata and localized assets, streamlining the store listing creation process for your mobile app.

Can I use this release orchestration workflow for existing app updates, or only new submissions?

Yes, this release orchestration workflow is applicable to both new app submissions and existing app updates across iOS and Android, performing readiness audits and building submission packets for either scenario.

How do I run a readiness audit before submitting my Expo app to the app store?

Running a readiness audit is part of the end-to-end release pipeline, which evaluates your Expo app's submission readiness and generates the necessary documentation, metadata, and screenshots before you upload to the stores.

Does this mobile release pipeline require specific dependencies to compile the submission packet?

No specific external dependencies are required to compile the submission packet; the pipeline uses internal Python scripts to generate store assets, metadata, and submission documentation for your mobile app.