Expo Dev Client skill for Claude Code: build and distribute Expo development clients
Expo's skill that makes Claude build and distribute Expo development clients, for React Native developers who outgrew Expo Go.
- Installs
- 72.5K
- on skills.sh
- Stars
- 4K
- on GitHub
- Files
- 1
- besides SKILL.md
- Updated
- Nov 2026
- last repo commit
Claude first decides whether you need a development client at all. The SKILL.md says you need one only for local Expo modules, Apple targets such as widgets, third-party native modules not in Expo Go, config plugins, or testing remote push notifications and links. It then sets up a development profile in eas.json, builds on Expo's cloud or on your machine, and connects the app to your Metro bundler.
Cloud builds use your EAS plan's build minutes, and device or TestFlight distribution needs a paid Apple Developer account. The skill says: "Free locally; cloud builds are paid." It bundles one small file, agents/openai.yaml (a display name, short description and default prompt), and no scripts.
Good for
- React Native developers using native modules or config plugins that Expo Go lacks
- Developers sending test builds to TestFlight
- Teams testing push notifications or universal links on a real device
Install expo-dev-client
Claude Code
- 1
Copy this prompt.
Install the expo-dev-client 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.
The README recommends the plugin for Claude Code: it installs all Expo skills, bundles the Expo MCP server configuration and updates through the marketplace. This skill points to expo-overview for the exact launch-without-dev-menu commands, which the plugin includes. Pick one route, not both. Restart or refresh the session afterwards.
From the project README. Source.
What's in the skill
When it loads
Build and distribute Expo development clients locally or via TestFlight for internal testing. For production TestFlight releases and store submission, use the eas-app-stores skill.
Sections in SKILL.md
- Important: When Development Clients Are Needed
- EAS Configuration
- Building for TestFlight
- Building Locally
- Installing Local Builds
- Building for Specific Platform
- Checking Build Status
- Using the Dev Client
- Troubleshooting
- Submitting Feedback
Key facts
- Author
- Expo
- Repository
- expo/skills
- Installs on skills.sh
- 72,519 (2 Nov 2026)
- GitHub stars (repo)
- 4,005 (2 Nov 2026)
- License
- MIT
- Last commit (repo)
- 1 Nov 2026
- skills.sh audits
- Gen Agent Trust Hub pass, Socket pass, Snyk pass
What it includes
Decide between Expo Go and a development client
Claude checks whether you use custom native code, Apple targets, native modules outside Expo Go, config plugins or push notification tests.
Read ·
Do you need a dev client?Add a development profile to eas.json
Claude makes sure eas.json has a `development` profile with `developmentClient: true`, auto-increment and remote version source.
Write ·
EAS configurationeas build -p ios --profile development --submit
A cloud build that is submitted to App Store Connect. Expo emails you when it is ready in TestFlight.
Try: “Build an iOS dev client and send it to TestFlight.”
Runs code ·
Build for TestFlighteas build ... --local for iOS or Android
Builds on your machine and outputs an .ipa for iOS (needs Xcode) or an .apk or .aab for Android.
Runs code ·
Build locallysimulator, device or Android install commands
Uses xcrun simctl for the iOS simulator, ideviceinstaller for a device, and adb install for Android.
Runs code ·
Install local buildseas build:list and eas build:view
Lists recent builds and shows details of one.
Runs code ·
Check build statusnpx expo start --dev-client, then scan the QR code
Starts Metro, then the dev client connects by QR code or URL. The skill also gives launch URLs that skip onboarding and the dev menu.
Runs code ·
Use the dev clienteas credentials, --clear-cache, eas --version
Commands for signing errors (eas credentials), stale build caches (--clear-cache) and checking the EAS CLI version.
Runs code ·
Troubleshootingnpx --yes @expo/agent-cli@latest feedback
Sends a short report about the skill to Expo when something is wrong or outdated.
Runs code ·
Submit feedback
From the official docs
Permissions
Medium risk
Claude runs build, install and submit commands that can use paid build minutes and send a build to TestFlight. Approve each command yourself and prefer local builds when you are testing.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
Cloud builds use paid build minutes
The skill says cloud builds use your EAS plan's build minutes and need a paid Apple Developer account for TestFlight. Prefer local builds when you can, and check your plan first. expo.dev
The submit flag sends a build to App Store Connect
The TestFlight command builds in the cloud and submits automatically. Confirm the profile and app before you let Claude run it.
Feedback runs a freshly downloaded package
The feedback command uses npx --yes with the latest @expo/agent-cli and may include task context. Read the text before you approve it.
The plugin install adds the Expo MCP server
The README says the expo plugin bundles the Expo MCP server configuration, which can trigger and monitor EAS builds and workflows. The skills CLI route installs the skill without it. Check which route you use. github.com
Security advisories
No published security advisories as of Nov 2, 2026.
Technical details
| Turning on read-only | The skill defines no read-only switch. |
|---|---|
| Talks to | Expo EAS servers for cloud builds. App Store Connect and TestFlight when you use the submit option. npm, for npx --yes @expo/agent-cli@latest when feedback is sent. Expo MCP server, if you install the expo plugin |
| Scopes |
|
Questions
What does the Expo Dev Client skill do?
It makes Claude set up and build Expo development clients. These are custom builds of your app that include your native code, used instead of Expo Go. It covers the eas.json profile, cloud and local builds, TestFlight, and connecting to Metro.
Do I need a development client?
Only in some cases. The skill lists local Expo modules, Apple targets such as widgets, native modules not in Expo Go, config plugins, and testing push notifications or universal links. It also says most real apps eventually outgrow Expo Go.
How do I install it?
Use the install box at the top of this page. The README says Claude Code and Codex users can instead install the whole expo plugin, which gets updates through their marketplaces, and that the skills CLI installs all Expo skills for other tools. Start a new session afterwards.
Is it free to use?
The skill is free and MIT licensed. Building locally is free. Cloud builds use your EAS plan's build minutes, and TestFlight or device distribution needs a paid Apple Developer account, according to the skill.
Do I need the other Expo skills?
No. This skill points to eas-app-stores for production TestFlight releases and store submission, and to expo-overview for launch commands. They come in the same repo, and the README installs all of them together.
Is it safe to install?
It runs real build and install commands, so read each one before you approve it. Cloud builds cost build minutes, and the TestFlight option submits a build to App Store Connect. The skill has no scripts of its own, and its feedback command only runs if an agent has something specific to report.
Information
updated Nov 2, 2026
- Repository
- expo/skills
- Folder
plugins/expo/skills/expo-dev-client
Sources
Docs, issue trackers and discussions this page is built from.
Show all 3Hide
- expo/skills README · github.com
- skills.sh listing · skills.sh
- expo-dev-client SKILL.md · github.com