expo/skills: Official Expo Team Skills for Building and Shipping Mobile Apps

LLMs are competent at React and shaky at the parts that make mobile hard: EAS build profiles, iOS and Android constraint differences, the upgrade path between SDK versions. expo/skills (2.5k stars, MIT) is the Expo team's official collection for building, deploying, upgrading, and debugging Expo apps — the vendor teaching agents how its own tooling is supposed to be used, with Expo docs, the Expo CLI, and the EAS CLI kept as the source of truth.

Why This Skill Matters

The skills give agents the focused Expo knowledge the README describes: when to use which Expo API, how to structure common workflows, and which Expo, EAS, React Native, iOS, and Android constraints matter — exactly the places general-purpose agents tend to drift. The team acknowledges its own docs and CLIs are the source of truth, and the skills exist to help agents apply them correctly rather than replace them.

Distribution follows the official channels: plugins for Claude Code and Codex through their curated marketplaces (so updates ride the marketplace), and a skills CLI path covering Cursor, OpenCode, GitHub Copilot, Windsurf, Gemini, Cline, and others. Two install routes cover the ecosystem cleanly.

Installation

The skills CLI installs every Expo skill in one command, selecting all skills but only the agents you pick afterwards:

npx skills@latest add expo/skills --skill '*'

Add --agent <agent> to target one directly. Run it from the project root, then restart or refresh the agent session so it discovers the installed SKILL.md files.

Claude Code and Codex use their official plugin marketplaces, which also handle updates:

claude plugin install expo@claude-plugins-official
codex plugin add expo@openai-curated

Both can also be installed through the in-app plugin UI (/plugin install expo@claude-plugins-official, or /plugins in Codex).

Real Workflow: Upgrade an Existing App

1. Make sure the Expo skills are installed and your session refreshed.
2. Start with the upgrade ask:

Help me upgrade this Expo app to the latest SDK and resolve the breaking changes

3. The skill steers the agent through the upgrade patterns — version-specific change notes and the constraints that changed — rather than a generic "bump the dependency" move.

Real Workflow: Set Up a Build for Release

For the shipping side, ask in project context:

Walk me through configuring an EAS build for iOS and Android release

The agent applies the EAS CLI conventions from the skills instead of guessing profile names and platform flags — the CI-facing configuration flows from documented patterns rather than pretraining memory.

Tips

• Prefer the plugin route on Claude Code and Codex — marketplace updates are automatic, and the README's updating section points there first.
• Refresh the agent session after any skills CLI install; the skills are only discoverable after the reload.
• Since Expo docs and CLIs stay the source of truth, pair the skills with the docs links the agent pulls — they complement rather than compete.
• The docs page at docs.expo.dev/skills is the canonical reference for the collection.

When Not to Use This

The value is in application-specific guidance: Expo APIs, EAS, and the React Native platform quirks. A generic React or TypeScript question triggers nothing useful here. And your app's own legacy patterns may predate the current Expo conventions the skills describe — apply the guidance with an eye to your SDK version.

See the leaderboard for more skills.