What does this skill do, and when should you use it?
This is one focused Agent Skill in the expo/skills repository, dedicated to releasing native Expo apps through Expo Application Services. It guides users through EAS CLI setup, eas.json configuration, iOS and Android production builds, and submissions to the App Store, Google Play, and TestFlight. It also covers app and build version management, store metadata, and ASO workflows. EAS is a paid service, so build-minute limits and store-account fees may apply.
It provides commands and configuration examples for installing and logging into EAS CLI, initializing eas.json, creating iOS, Android, or cross-platform production builds, and submitting builds to App Store Connect or Google Play with --submit. It shows the npx testflight shortcut, Apple credential setup references, Google Play service-account configuration, Android release tracks, remote version management, build and submission status checks, and links to workflows and store-metadata references.
- An Expo developer is preparing an iOS production release and needs build, submission, and version-number configuration.
- An Android team is moving an Expo app through Google Play internal, closed, open, or production tracks.
- A product team needs to submit an iOS build to TestFlight for beta testing.
- A release engineer wants to manage production build and submission profiles through eas.json with automatic version increments.
- An app-operations team needs guidance for App Store metadata or ASO preparation.
How do you install this skill?
- Before running eas build, eas submit, metadata:push, or any automatic release flow, explicitly confirm the project, platform, track, version, and expected cost, and prepare a practical pause or rollback plan.
- Do not commit Apple API keys, Google service-account JSON, demo accounts, or passwords; replace example credential fields with secure Secrets or controlled environment variables.
- Core workflows depend on Expo, App Store Connect, and Google Play services; verify CLI, authentication, and upload reachability in mainland-China network environments.
- Recheck commands, field formats, quotas, and release policies against current EAS CLI, App Store Connect, and Google Play documentation.
- Shell / CLI
- Network access
- Local filesystem
Node.js/npmEAS CLIApple Developer account for iOS distributionGoogle Play account for Android distribution
The skill is located at plugins/expo/skills/eas-app-stores/SKILL.md. The README documents installation of the full Expo skills collection: for Cursor, OpenCode, and similar agents, run npx skills@latest add expo/skills --skill '*'; for Codex, run codex plugin add expo@openai-curated; for Claude Code, run claude plugin install expo@claude-plugins-official. The source does not document a standalone installation command for only eas-app-stores.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/expo/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/plugins/expo/skills/eas-app-stores" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Run npm install -g eas-cli and eas login, then initialize the Expo project with npx eas-cli@latest init to create eas.json. Build with npx eas-cli@latest build -p ios --profile production, npx eas-cli@latest build -p android --profile production, or npx eas-cli@latest build --profile production. Add --submit to build-and-submit, or use npx testflight for the iOS TestFlight shortcut. Example request: Prepare a production build for this Expo app and submit it to TestFlight.
What are this skill's strengths and limitations?
- Covers the main release flow for the iOS App Store, Google Play, and TestFlight.
- Includes copyable EAS CLI commands and an eas.json production configuration example.
- Documents versioning, build-number management, build monitoring, and submission monitoring.
- Clearly separates native app-store releases from EAS Hosting website and API deployment.
- EAS builds and submissions are subject to paid plans and free-tier limits.
- Store submission requires paid Apple Developer and Google Play accounts.
- The source provides no test suite or concrete platform-validation results.
- Detailed CI/CD, TestFlight, metadata, and store-review procedures depend on external reference files.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Expo App Store Release Assistant this page | 52 · Use with care | ★ 2.9k | 21d ago | MIT |
| Expo Development Client Builder | 54 · Use with care | ★ 2.9k | 21d ago | MIT |
| Expo Native UI Builder | 59 · Recommended | ★ 2.9k | 21d ago | MIT |
| Expo Brownfield Integrator | 58 · Recommended | ★ 2.9k | 21d ago | MIT |
| Expo Web-to-Native Migration | 52 · Use with care | ★ 2.9k | 21d ago | MIT |
For Expo websites or Expo Router API routes, use the sibling eas-hosting skill instead; eas-app-stores is focused on native app-store releases. Expo documentation, Expo CLI, and EAS CLI remain the stated sources of truth.
How did FollowSkills review this skill?
The documentation clearly discloses EAS, Apple Developer, and Google Play costs and recommends .gitignore or Secrets for service-account keys. However, examples include automatic release, production tracks, and remote version management without mandatory pre-release confirmation or rollback guidance, and credential and external-data flows are not fully disclosed, so points are deducted.
The material covers the main iOS, Android, TestFlight, metadata, versioning, and CI/CD paths and includes troubleshooting sections. However, there are no key-path tests or reproducible results, some commands and configuration formats are version-sensitive or uncertain (such as the metadata keywords example and npx testflight), and abnormal-input failure feedback is thin, so the score is limited.
Triggers, audience, and boundaries with eas-hosting and eas-workflows are relatively clear, and zh-Hans/zh-Hant locales are listed. However, there is no Chinese-language operating guidance or mainland-China reachability analysis; core functionality depends on Expo, Apple, and Google services, and non-fit boundaries remain incomplete, so points are deducted.
The SKILL.md, agent configuration, and topic-specific reference files provide clear structure, installation notes, configuration examples, troubleshooting, licensing, and version information. The skill lacks a clearly assigned maintainer, explicit update path, changelog, and systematic known-limitations disclosure, so it does not receive full marks.
Commands, eas.json examples, and platform guides can address the core tasks of production builds, store submissions, TestFlight, and metadata management. Static material does not verify representative outputs, and credentials, store-console setup, and review still require manual work; evidence for direct usability and marginal benefit over manual alternatives is limited, so points are deducted.
Evidence includes revisioned source files, detailed references, the README, and repository CI checks. There are no committed tests for this skill's key paths, real build records, or independent third-party corroboration, so conclusions rely mainly on documentation and receive only limited verifiability.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →