eas-app-stores
EAS app stores
eas-app-stores is the Expo team's agent skill for shipping mobile apps with EAS: build profiles, signing, version numbers, TestFlight and submissions to the App Store and Google Play.
Install EAS app stores
Install the skill with the skills CLI
npx skills add expo/skills --skill eas-app-storesOr, in Claude Code, install Expo's plugin from the official marketplace
claude plugin install expo@claude-plugins-officialOr, in Codex, install Expo's plugin from the OpenAI-curated marketplace
codex plugin add expo@openai-curatedOr paste this into your coding agent: Install the agent skill eas-app-stores from github.com/expo/skills.
A skill can include scripts that run on your computer, so read its source first.
What EAS app stores does
EAS app stores is one of the official Expo skills, in the Services group that relies on Expo Application Services. It covers building iOS and Android apps in the cloud and sending them to TestFlight, the App Store or Google Play. It works for Expo and other React Native projects, and also for native apps that use EAS only for delivery.
The agent first picks a path: a SwiftUI or UIKit app with no React Native, a native Android app, an Expo or React Native app, or a native app gaining React Native screens. For Expo projects it initializes EAS, sets build profiles in eas.json with remote app versions and auto-increment, and runs production builds with optional auto-submit. Reference files cover TestFlight, App Store review, Play Store tracks, store metadata and CI workflows.
The skill is careful about what success means. It tells the agent that a finished build or a queued submission does not prove Apple accepted the build, that testers can reach it, or that it is live in the store, and it lists checks for processing and availability. Monitoring commands show recent builds and submission status.
When to use EAS app stores
- You are publishing your first Expo app to TestFlight and Google Play.
- You want build profiles, signing and version numbers set up once in eas.json.
- You want builds that submit to the stores automatically after they finish.
- You have a native Swift app and want EAS to handle builds and submissions.
When to pick something else
- Hosting an Expo website or API routes: Expo points to its eas-hosting skill.
- Free-only setups: EAS builds count against plan limits, and store memberships cost extra.
What EAS app stores needs
- An Expo account with EAS (free tier and paid plans, see expo.dev/pricing)
- An Apple Developer membership for iOS and a Google Play Console account for Android
- EAS CLI (npm install -g eas-cli)
Which agents EAS app stores works in
Expo documents EAS app stores for Claude Code, Codex, Cursor, OpenCode, GitHub Copilot, Windsurf, Gemini CLI, Cline, Any agent that reads SKILL.md files, through the skills CLI. The open skills CLI also installs it into 78 agents, including Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode (we listed it with the CLI on October 1, 2026). See where each agent looks for skills.
EAS app stores license
EAS app stores is published under MIT. The skill is free under MIT, but the service it drives is not always free: Expo labels it an EAS paid-service skill, where cloud builds use EAS plan resources with free-tier limits.
Related skills for mobile
- Expo Router: expo-router is the Expo team's agent skill for navigation in Expo apps: file-based routes, native stacks and tabs, links with previews and context menus, modals, form sheets, headers and search bars.