mobile-store-upload-cli

Automate iOS TestFlight and Android Play Store uploads via CLI.

6|Updated Apr 23, 2026
One-click install
npx skills add https://github.com/ImL1s/flutter-claude-skills --skill mobile-store-upload-cli
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mobile-store-upload-cli
Source: https://github.com/ImL1s/flutter-claude-skills/tree/main/skills/mobile-store-upload-cli
Command: npx skills add https://github.com/ImL1s/flutter-claude-skills --skill mobile-store-upload-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides command-line, manual release workflows for iOS TestFlight and Google Play uploads, enabling teams to perform builds, archiving, validation, and publishing without GUI reliance.

Core Features & Use Cases

  • Deterministic CLI-driven release steps for iOS and Android
  • Secure handling of credentials and sensitive data with guardrails
  • Flexible integration with App Store Connect and Play Console APIs or keys
  • Post-upload verification and status tracking for faster feedback

Quick Start

Run the mobile-store-upload-cli to prepare, validate, and upload your IPA or AAB from the terminal.

Frequently Asked Questions about mobile-store-upload-cli

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

FAQPage Schema
How do I upload an iOS app to TestFlight using the command line?

To upload an iOS app to TestFlight via the command line, you run the mobile-store-upload-cli to archive, validate, and publish your IPA build directly to App Store Connect without needing a GUI.

What is the best way to automate Google Play Store uploads from the terminal?

Automating Google Play Store uploads from the terminal is done by running the CLI to validate and upload your AAB build, requiring Play Console API keys and configured credentials to publish without GUI reliance.

Do I need API keys to automate Android Play Store uploads via CLI?

Yes, automating Android Play Store uploads via CLI requires API keys or user accounts for Play Console access, a configured project, and proper credentials to securely handle validation and publishing steps.

Can I validate builds before publishing to TestFlight and Google Play?

Yes, you can validate builds before publishing to TestFlight and Google Play, as the CLI workflow performs post-upload verification, archiving, and status tracking to provide faster feedback on your IPA or AAB.

Why use a manual CLI release workflow instead of a GUI for mobile app uploads?

Using a manual CLI release workflow instead of a GUI provides deterministic, command-line driven release steps for iOS and Android, enabling teams to securely perform archiving and publishing with guardrails for sensitive data.

Are there limitations to manual CLI release management for iOS and Android?

Limitations of manual CLI release management for iOS and Android include the strict requirement for prerequisite credentials, App Store Connect and Play Console access, and a fully configured project to successfully execute the end-to-end upload workflows.