Expo Dev Client
Build and distribute Expo development clients locally or via TestFlight for internal testing of native code
- What
- Build and distribute Expo development clients locally or via TestFlight for internal testing of native code
- Cost
- Free
- Needs
- an Expo project; local builds are free — cloud builds use EAS plan build minutes, and TestFlight/device distribution needs a paid Apple Developer account
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an official Expo skill for development clients: it guides building custom Expo Go-style clients with EAS Build to test native code changes on physical devices — the recommended setup for any real or production app, since Expo Go is only a playground for learning and quick experiments. Covers when a dev client is needed, local vs cloud builds, and internal distribution. By @expo, listed here with credit to its creator. Honest caveats: the skill itself is free and local builds are free, but cloud builds consume EAS plan build minutes and device/TestFlight distribution requires a paid Apple Developer account; for production store releases, use the separate eas-app-stores skill. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: an Expo project; local builds are free — cloud builds use EAS plan build minutes, and TestFlight/device distribution needs a paid Apple Developer account Install "Expo Dev Client" for me. Build and distribute Expo development clients locally or via TestFlight for internal testing of native code Repository: https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-dev-client/SKILL.md 1. Fetch the SKILL.md file for the expo-expo-dev-client skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "expo-expo-dev-client". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.