# Expo Skills: Official AI Agent Skills for Building and Deploying Expo Apps > Expo Skills is a collection of structured knowledge definitions that give AI coding agents accurate, up-to-date guidance on Expo APIs, EAS workflows, and React Native constraints. It installs into Claude Code, Codex, Cursor, and a dozen other agents with a single command, and distinguishes free open-source skills from paid EAS services skills. **expo/skills** — A collection of AI agent skills for working with Expo projects and Expo Application Services - Repository: https://github.com/expo/skills - Stars: 2,641 · Forks: 156 - Language: Shell - License: MIT - Published: 2026-09-10 · Updated: 2026-09-10 · Language: en - Canonical page: https://hysenlabs.com/projects/expo-skills ## Structured Expo Knowledge for AI Coding Agents AI coding agents produce better results when they have precise, project-specific knowledge rather than relying on general training data or live documentation searches. Expo Skills solves this for Expo and EAS work by packaging the Expo team's own guidance into SKILL.md files that agents load as context before answering questions or writing code. The README describes the goal clearly: skills give agents focused knowledge of when to use Expo APIs, how to structure common workflows, and which Expo, EAS, React Native, iOS, and Android constraints matter. Expo documentation, the Expo CLI, and the EAS CLI remain the source of truth; skills help agents apply that documentation correctly rather than substituting for it. The package targets developers who already use Expo and want their AI coding tool to work correctly with Expo-specific patterns rather than generic React Native patterns. The entry-point skill is `expo-overview`, which the README describes as the starting point for any Expo or EAS task: it loads first for vague requests or when the user has not named a specific Expo tool, then routes the agent to a more specific skill. This routing design prevents agents from loading every skill at once and keeps context focused. ## How Skills Work: SKILL.md Files and Agent Discovery Each skill in the collection is a SKILL.md file describing a specific domain: Expo Router navigation, EAS Update rollouts, the expo-module API for native modules, and so on. An agent discovers which skill to load by reading each skill's description and matching it against the current task. The README states that agents choose the right skill from task context and each skill's description, which means the loading is automatic once the skills are installed. The repository is organized as a git repository with a skills.sh.json manifest and submodule or plugin configuration files for each supported agent. The `.claude-plugin/` directory holds Claude Code plugin metadata, `.cursor-plugin/` holds Cursor configuration, and the `.agents/` directory contains agent-level configuration files. There is also a `.claude/` directory and a `CLAUDE.md` file visible in the top-level entries, suggesting the repository itself uses Claude Code during development. ## Installing Expo Skills in Claude Code, Codex, and Other Agents For Claude Code, install via the official plugin marketplace: ```text claude plugin install expo@claude-plugins-official ``` You can also run `/plugin install expo@claude-plugins-official` from inside a Claude Code session. For Codex: ```text codex plugin add expo@openai-curated ``` For Cursor, OpenCode, GitHub Copilot, Windsurf, and other agents that support the skills CLI, install all Expo skills at once: ```text npx skills@latest add expo/skills --skill '*' ``` The `--skill '*'` flag selects every Expo skill without targeting a specific agent; the CLI will ask where to install them. To target one agent directly, add `--agent ` to the command. Run this from the project root, then restart or refresh the agent session so it can discover the installed SKILL.md files. ## Free Framework Skills vs. Paid EAS Services Skills The collection is split into two groups to make the cost boundary explicit. Framework skills cover the open-source Expo SDK and React Native: expo-router, expo-animation, expo-native-ui, expo-data-fetching, expo-upgrade, expo-module, expo-brownfield, expo-dom, expo-design-system, expo-ui, expo-web-to-native, expo-dev-client, expo-examples, expo-app-clip, and expo-skill-feedback. These skills describe free, open-source functionality. Services skills cover paid Expo Application Services features: eas-app-stores, eas-hosting, eas-workflows, eas-observe, eas-update, eas-update-insights, and eas-simulator. The README states that each services skill's description carries a label indicating it uses paid EAS features, and every services skill opens with a costs and plan-limits note. This design means an agent will surface pricing context before suggesting EAS-specific workflows, reducing the chance of recommending a paid step without warning. A third group, marked Experimental, covers Expo APIs that have not yet stabilized; these ship in a separate `expo-experiments` plugin. The current experimental skill is `expo-migrate-module`, which covers migrating Swift Expo modules from the Modules API 1.0 definition DSL to the 2.0 macro API. ## Updating Skills and the Expo MCP Server Plugin installs through the Claude Code or Codex marketplaces are updated through those respective marketplace update mechanisms. For skills CLI installs, update all skills with: ```text npx skills@latest update ``` To update a single skill by name: ```text npx skills@latest update expo-router ``` The README also describes an Expo MCP server as a complement to skills. Where skills teach an agent how Expo work is done, the MCP server gives the agent live access to do that work: reading the latest Expo docs on demand, installing compatible dependencies with `npx expo install`. These are separate tools with different purposes; the README presents them as working together rather than as alternatives. The skills CLI itself is a third-party tool maintained at skills.sh and is not part of the Expo organization, so issues with the CLI itself should be directed to the skills.sh project rather than the Expo team. ## What Expo Skills Does Not Solve Expo Skills does not add Expo knowledge to agents that do not support SKILL.md files or either plugin marketplace. The README lists the supported agents explicitly: Claude Code, Codex (via plugin), Cursor, OpenCode, GitHub Copilot, Windsurf, Gemini, Cline, AMP, Factory Droid, Antigravity, and Kiro CLI (via the skills CLI). Agents not on that list may require manual configuration or may not support skills at all. The skills also cover Expo and EAS workflows, not general React Native development outside Expo. An engineer working on a bare React Native project without Expo tooling will not benefit from this package. The package has no GitHub releases and the latest commit history is not versioned in the same way as a traditional library; the skills CLI's `npx skills@latest` pattern pulls the current HEAD of the skills repository on each install. There is also a distinction worth noting between skills and an MCP server. Skills are static context files loaded by an agent's own runtime. The Expo MCP server is a separate tool that gives agents live access to Expo documentation and commands. Neither replaces the other: skills set the pattern, the MCP server executes it. Teams that want the full picture should consult both, but the skills package is the starting point and does not require the MCP server to function. ## Conclusion Expo developers who use AI coding agents will find these skills directly useful: the package gives agents knowledge of Expo Router, EAS workflows, and React Native constraints without the agent needing to search documentation mid-task. Verify that your agent supports either the Claude Code plugin marketplace, the Codex marketplace, or the skills CLI before installing. Teams not using Expo or EAS have no use for this package. The last push to the repository was on 2026-09-24. ## FAQ ### How to install skills in Claude Code for Expo development? Run `claude plugin install expo@claude-plugins-official` in your terminal, or run `/plugin install expo@claude-plugins-official` from inside a Claude Code session. Updates are handled automatically through the Claude Code plugin marketplace. ### How to use skills in Claude Code for Expo projects? After installing the Expo plugin, ask your Claude Code agent Expo-specific questions such as building an Expo Router screen or creating an EAS workflow. The agent selects the appropriate skill from the installed SKILL.md files based on the task context. ### How to install skills in Codex for Expo development? Run `codex plugin add expo@openai-curated`, or open `/plugins` in Codex and install `expo` from the OpenAI-curated marketplace. Updates are handled through the Codex marketplace. ## Sources - [expo/skills on GitHub](https://github.com/expo/skills) - [Issues](https://github.com/expo/skills/issues) - [License: MIT](https://github.com/expo/skills/blob/main/LICENSE) - [README](https://github.com/expo/skills/blob/main/README.md) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/expo-skills