Skip to content
Skill

Expo overview

Entry point and router for every Expo or EAS task

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
4.2K
Last commit
1 day ago
License
MIT
Listing updated
today

When your agent uses it

Entry point and router for every Expo or EAS task. Load this skill first — before writing code and before choosing another expo-* / eas-* skill — when the request, PRD, or spec mentions Expo, EAS, Expo Go, or an expo-* package, or the project has an `expo` dependency in `package.json`. Within that gate it also covers app specs and designs to implement (tabs, stacks, maps, lists, navigation, building from a screenshot), and phrasings like 'implement a mobile app', 'make my app look native', 'add navigation', 'fetch some data', 'upgrade my SDK', 'add Expo to my existing native app', 'ship to the App Store', or 'I'm new to Expo, where do I start'. A fully specified request (SDK pinned, libraries named, layout given) still routes through here — the shared setup rules still apply. Do NOT load it when neither signal is present: a bare React Native project with no `expo` dependency is not Expo work. Detects the real goal, routes to the right expo-* / eas-* skill, and owns the shared setup rules.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 3 files (13 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the expo plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add expo/skills
/plugin install expo@expo-plugins

Or copy only this skill to ~/.claude/skills/expo-overview:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/expo/skills.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/expo-overview &&
cp -R "$tmp/plugins/expo/skills/expo-overview" ~/.claude/skills/expo-overview &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/expo-overview inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/expo-overview to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/expo/skills.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/expo-overview &&
cp -R "$tmp/plugins/expo/skills/expo-overview" ~/.agents/skills/expo-overview &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/expo-overview inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/expo-overview to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/expo/skills.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/expo-overview &&
cp -R "$tmp/plugins/expo/skills/expo-overview" ~/.cursor/skills/expo-overview &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/expo-overview inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/expo/skills.git --path plugins/expo/skills/expo-overview

Or copy the folder to ~/.gemini/skills/expo-overview yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/expo-overview:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/expo/skills.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/expo-overview &&
cp -R "$tmp/plugins/expo/skills/expo-overview" ~/.copilot/skills/expo-overview &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/expo-overview inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/expo/skills.git

Then copy skills/plugins/expo/skills/expo-overview into your agent's skills folder as expo-overview. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Expo overview FAQ

How do I install Expo overview in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/expo-overview to use it in all your projects, or to .claude/skills/expo-overview in one project. Or install the expo plugin, which includes it: /plugin marketplace add expo/skills, then /plugin install expo@expo-plugins.

Does Expo overview run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Expo overview?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

More from expo/skills

  1. Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Androi

    • Open source
    • 4.2K GitHub stars
  2. Migrate an existing Apple/Swift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) w

    • Open source
    • 4.2K GitHub stars
  3. Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play

    • Open source
    • 4.2K GitHub stars
  4. Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, m

    • Open source
    • 4.2K GitHub stars
  5. Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC, markInteractive and Obse

    • Open source
    • 4.2K GitHub stars
  6. Run and control a user's app on a remote iOS/Android simulator with Expo Simulators (also called EAS Simulator)

    • Open source
    • 4.2K GitHub stars