eas-app-stores skill: build your app with EAS and send it to TestFlight, the App Store or Google Play
Makes your agent set up EAS and build and submit your iOS or Android app to TestFlight, the App Store or Google Play.
- Installs
- 24.8K
- on skills.sh
- Stars
- 4K
- on GitHub
- Files
- 7
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
eas-app-stores is an official skill from the Expo team. It guides your agent through eas.json, signing credentials, app versions, store metadata and the eas build and eas submit commands. It covers Expo and other React Native apps, and also existing SwiftUI/UIKit and native Android apps.
EAS cloud builds use EAS plan resources and SKILL.md opens with a warning that costs apply. Apple Developer and Google Play memberships are separate. The agent runs EAS CLI commands that sign in to Expo and, with --auto-submit, upload builds to the stores.
Good for
- Mobile developers shipping an Expo or React Native app for the first time
- Teams setting up a repeatable TestFlight and Play Store release
- Native Swift or Android developers who want EAS for delivery only
- Anyone debugging a rejected upload or a duplicate build number
Install eas-app-stores
Claude Code
- 1
Copy this prompt.
Install the eas-app-stores skill in Claude Code. Run this command: claude plugin install expo@claude-plugins-official Then check that it loaded and tell me how to use it.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Pick one route, not both. The README recommends the plugin for Claude Code. It installs all of the Expo skills and also adds a connection to the Expo MCP server at https://mcp.expo.dev/mcp, which lets your agent read Expo docs and work with EAS builds. The skills CLI route installs only eas-app-stores.
From the project README. Source.
What's in the skill
When it loads
Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play. Supports Expo and other React Native projects, plus existing native apps. Use for eas.json setup, release pipelines, signing, app versions and build numbers, store submissions, and listing metadata. For Expo websites and API routes, use eas-hosting; for adding React Native screens to a native app, use expo-brownfield.
Sections in SKILL.md
- Choose the project path
- References
- Expo / React Native Quick Start
- Install EAS CLI
- Initialize EAS
- Build Commands
- Production Builds
- Submit to Stores
- Web & API Route Hosting
- EAS Configuration
- Platform-Specific Guides
- iOS
- Android
- Automated Releases
- Version Management
- Monitoring
Key facts
- Installs on skills.sh
- 24,846 (data from 2026-11-02)
- License
- MIT (frontmatter and README)
- Last repo commit
- 2026-11-01
What it includes
Picks Expo/React Native, native iOS, native Android or brownfield
The agent first decides which kind of app you have. Native Swift apps get the native-ios guide, native Android apps get the Play Store guide, and adding React Native screens to a native app goes to expo-brownfield.
Read ·
Choose the project pathInstalls EAS CLI, signs in, links the project
Runs npm install -g eas-cli, eas login, then npx eas-cli@latest init and eas build:configure to create build profiles in eas.json.
Try: “Set up EAS builds for this Expo app and make an eas.json with a production profile.”
Runs code ·
Quick start: eas login and initeas build for iOS, Android or both on a production profile
Starts cloud builds with npx eas-cli@latest build. These use your EAS plan resources.
Runs code ·
Build commands--auto-submit sends the build to App Store Connect or Play
Builds and submits in one step. For Expo and React Native iOS apps it also names npx testflight as a quick TestFlight route.
Try: “Build the iOS app and submit it to TestFlight.”
Runs code ·
Submit to the storesSubmit an identified build and read its status
Uses eas build --no-wait and eas submit --id with --non-interactive, then eas submit:list and submit:view to read status.
Runs code ·
references/testflight.mdCredentials, submission and the public release steps
Covers eas credentials, an App Store Connect API key or Apple ID with an app-specific password, and the steps in App Store Connect to add a build for review. It says to do publication steps only within the scope you asked for.
Runs code ·
references/ios-app-store.mdService account, tracks and staged rollout
Covers the Google service account JSON, eas secret:create, release tracks and eas submit for Android.
Runs code ·
references/play-store.mdeas metadata:pull and push, plus ASO tips
Manages App Store listing text with a config file, and gives limits for title, subtitle and keywords.
Runs code ·
references/app-store-metadata.mdNative Swift iOS apps on EAS with archive checks
Keeps the Xcode project as the source of truth and checks the archived build number with plutil.
Runs code ·
references/native-ios.mdEAS Workflows for PR previews and store releases
CI/CD examples. To write or validate workflow YAML, the skill sends you to eas-workflows.
Write ·
references/workflows.mdeas build:version:get and set, build:list, submit:list
Uses remote app versioning and lists builds and submissions.
Runs code ·
Version management and monitoringCan send feedback about the skill to Expo
SKILL.md tells the agent to run npx --yes @expo/agent-cli@latest feedback when it finds a specific, actionable problem with the skill, or when it fails repeatedly at an Expo task.
Runs code ·
Feedback command
From the official docs
Permissions
Medium risk
The skill runs EAS commands against your Expo, Apple and Google accounts, so a wrong command could use build credits or upload a build you did not mean to send. Read each build and submit command before you approve it.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
The plugin route adds a remote MCP server
The Expo plugin the README recommends for Claude Code and Codex ships a .mcp.json that registers an http MCP server at https://mcp.expo.dev/mcp, on top of the 23 skills in plugins/expo/skills. Its plugin.json lists a name, version (1.14.3), description and author. The skills CLI route installs only this one skill and adds no MCP server. github.com
Builds cost EAS plan resources
SKILL.md opens with a warning that EAS cloud builds use plan resources and that paid plans exist. Check your plan and ask the agent before it starts repeat builds.
Submit commands upload to your store accounts
build --auto-submit and eas submit send binaries to App Store Connect or Google Play. Check the profile and track before you approve, and do the public App Review step yourself.
Store keys and passwords are involved
The guides use an App Store Connect .p8 key, an Apple app-specific password and a Google service account file. Keep them out of version control and out of chat.
It can send feedback to Expo
SKILL.md tells the agent to run npx --yes @expo/agent-cli@latest feedback with a short report on skill problems. It only does so for something specific, so read the text it proposes first.
It installs and runs tools through npx
The quick start uses npm install -g eas-cli and npx eas-cli@latest. Review the commands before approving.
Technical details
| Talks to | Expo EAS services. App Store Connect. Google Play. mcp.expo.dev (plugin route only) |
|---|---|
| Sign-in and keys | EAS CLI and the store credentials you configure; the guides mention an App Store Connect API key (.p8 file), an Apple app-specific password and a Google service account JSON. |
| Scopes |
|
Questions
What does the eas-app-stores skill do?
It teaches your agent to build and submit iOS and Android apps with EAS. That covers eas.json, signing, versions, TestFlight, the App Store, Google Play and store metadata.
How do I install it in Claude Code?
Use the install box at the top of this page. The Expo README recommends its plugin for Claude Code, and the box also shows the skills CLI route for this skill only.
Does it cost money?
Possibly. SKILL.md warns that EAS cloud builds use EAS plan resources with free-tier and paid-plan limits. Apple Developer and Google Play memberships are separate. Check expo.dev/pricing.
Does it work with a native Swift app?
Yes. SKILL.md has a path for SwiftUI/UIKit apps with no React Native runtime, using the native-ios guide. A native Android app keeps its own build setup and uses the Play Store guide for submission.
Will it publish my app to the public?
The skill says to perform publication steps only within the scope you asked for, and that a TestFlight upload alone is not a public launch. Public release goes through App Review in App Store Connect.
Does it need API keys?
It needs store credentials. The guides cover an App Store Connect API key or an Apple ID with an app-specific password for iOS, and a Google service account key for Android. Keep these out of version control.
Is it safe?
It runs EAS CLI commands that use your Expo account, your signing credentials and your store accounts. Read each build and submit command before you approve it, and keep key files out of git. It may also send feedback to Expo with the feedback command.
Does it work in the Claude app, Codex or Cursor?
The Expo README documents Claude Code and Codex plugins and the skills CLI for Cursor, OpenCode, Copilot and others. It documents no Claude app route, and the skill relies on commands run on your machine.
Information
updated Nov 2, 2026
- Repository
- expo/skills
- Folder
plugins/expo/skills/eas-app-stores
Sources
Docs, issue trackers and discussions this page is built from.
Show all 7Hide
- expo/skills README · github.com
- Expo plugin .mcp.json · github.com
- skills CLI commands · github.com
- eas-app-stores SKILL.md · github.com
- ios-app-store reference · github.com
- testflight reference · github.com
- Expo plugin plugin.json · github.com