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:
Quick answer
Expo Dev Client is a free Muse skill, an Expo skill for development clients: it guides building Expo Go-style clients with EAS Build to test native code changes on devices, the recommended setup for any real app, since Expo Go is only a playground for learning. It covers when a dev client is needed, local versus cloud builds, and distribution.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit d4f4840Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/expo/skills/d4f484024fec15196bfd3c272e953e3f983972cf/plugins/expo/skills/expo-dev-client/SKILL.md Pinned version: install the code at commit d4f484024fec15196bfd3c272e953e3f983972cf exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the expo-expo-dev-client skill from the repository into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- d4f4840 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 18, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.