What problem does it solve? Once an Expo app has passed validation and QA, teams still face the error-prone mechanics of choosing build profiles, sequencing platform builds, and uploading binaries to App Store Connect or Google Play. This Skill standardizes that final build-and-submit step so uploads happen with explicit profiles and clear tracking. ## Core Features & Use Cases - Profile-driven builds: Runs eas build with explicit iOS and Android profiles rather than opaque all-at-once scripts. - Store upload sequencing: Executes eas submit per platform for TestFlight, App Store Connect, or Play internal/beta/production tracks. - Readiness gating: Confirms validation, QA, and App Store review prep are complete before any upload begins. - Use Case: After QA signs off on a release candidate, ask the agent to submit the validated Expo app to TestFlight; it confirms the iOS profile and credentials, builds with the production profile, submits, and reports the build ID plus remaining review handoff items. ## Quick Start Submit this validated Expo app to TestFlight using the production profile and report the build and upload status.