expo skills
OFFICIALLABSCO SUMMARY
The README's own table sorts the other 17 into four groups: App Design and Architecture covers Expo Router screens, native-feeling UI, Tailwind and NativeWind styling, DOM components, and dev-client builds; Native and Platform Work covers native modules, the @expo/ui SwiftUI and Jetpack Compose wrappers, App Clips, and brownfield integration into an existing native app; Deployment, CI, and Observability covers store submission, EAS Build and Workflow YAML, EAS Observe metrics, and EAS Update health and rollout gating; and Maintenance is one skill for SDK upgrades, dependency conflicts, and cache cleanup.
The two the table leaves out are expo-examples, which points at Expo's own with-* example repository — roughly 70 version-matched integrations for Stripe, Clerk, Supabase, OpenAI, and more — for copying a working pattern rather than writing one from scratch, and expo-skill-eval, which runs this same package's skills through an end-to-end benchmark on a real iOS simulator or Android emulator to check that they still produce working, screenshot-verified code.
READ THE FULL ANALYSIS
Roughly a quarter of the package needs an EAS account, and a chunk needs nothing at all. Our dependency check splits the 19 as 7 local_tool, 6 ready, 5 account_key, and 1 unverified — the account_key group lines up with the two skills whose own descriptions flag them as paid EAS services, eas-simulator (cloud iOS/Android simulators) and eas-update-insights (crash and rollout health for a published EAS Update).
Skills teach; the Expo MCP server acts. The README is explicit about the split — these 19 give an agent Expo-specific knowledge, while the separate Expo MCP server, bundled automatically with the Claude Code and Codex plugin installs, is what actually reads live docs, runs npx expo install, triggers EAS builds, pulls TestFlight crash data, and screenshots a running simulator. Installing the skills without the MCP server gets you the guidance without the live hooks into your own project.
ALSO IN THIS PACKAGE
expo
Official Expo skills for building, deploying, upgrading, and debugging Expo apps
expo-experiments
Experimental Expo skills for APIs that are not finalized. Skills here may change or be retired, and graduate to the expo plugin when stable.
expo-app-design
Official Expo skills for building, deploying, upgrading, and debugging Expo apps
upgrading-expo
Official Expo skills for building, deploying, upgrading, and debugging Expo apps
expo-deployment
Official Expo skills for building, deploying, upgrading, and debugging Expo apps
expo
http · https://mcp.expo.dev/mcpWHAT'S INSIDE
9 showing · 9 totalNothing else to set up — install it and go.
eas-simulator
A phone simulator that runs on Expo's servers rather than your own machine, with your app on it — something you or an AI agent can tap through, screenshot and record from anywhere.
eas-update-insights
Right after an update goes out to a live Expo app, this says whether it is healthy and how far it has spread, without anyone opening a dashboard.
expo-brownfield
Adding screens built with React Native to an iPhone or Android app that already exists, one piece at a time — either handed over as a prebuilt package, or built straight into the native project.
expo-dev-client
Builds a development client — a private test copy of an Expo app — and installs it on a phone or a simulator, so the custom native code inside it can actually be run.
expo-examples
Expo's own library of about 70 worked examples — how to hook up Stripe, Supabase, maps and the like — and how to lift one of them into an app you have already built without breaking it.
expo-module
Writes the bridge that lets an Expo app reach something only the phone itself can do — a sensor, a camera, a vendor's own SDK — in Swift for iPhone and Kotlin for Android.
expo-skill-eval
Puts an Expo skill to the test: an AI agent builds the same app twice, once with the skill and once without, and the two results come back side by side, screenshots included.
expo-ui
Controls in an Expo app that are the phone's real ones — a genuine iPhone or Android switch, slider or slide-up sheet — instead of JavaScript copies of them.
web-to-native
There is no button that turns a website into a phone app; this is the order to do it in instead, which screens to move first, and what breaks on the way.
HOW TO GET IT
npx skills add expo/skillsnpx skills add expo/skills --skill <name> --full-depthPick the skill name from the Skills tab — each entry there installs independently.
/plugin marketplace add expo/skills/plugin install expo@expo-plugins/plugin install expo-experiments@expo-plugins/plugin install expo-app-design@expo-pluginsTyped inside the agent's own prompt, not in a terminal. The marketplace lists 5 plugins; three are shown. Every one installs the same way, with its own name before @expo-plugins.