expo-overview

Routes Expo and EAS tasks to the correct leaf skill and applies shared setup rules.

2.5k|140|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/expo/skills --skill expo-overview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-overview
Source: https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-overview
Command: npx skills add https://github.com/expo/skills --skill expo-overview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When working on an Expo or EAS project, it is hard to know which specialized skill applies to a given request, and shared setup rules (SDK detection, package installation, EAS authentication) get repeated or missed. This Skill acts as the entry point that classifies the user's goal and routes to the right expo-* or eas-* skill.

Core Features & Use Cases

  • Goal classification and routing: Maps casual phrasings like "ship it" or "make it look native" to the correct leaf skill such as eas-app-stores, expo-ui, or expo-router.
  • Shared setup rules: Enforces SDK version detection from package.json, version-pinned documentation URLs, npx expo install for packages, and EAS login/project linking checks.
  • Use Case: A user asks to "add navigation and ship to the App Store." The Skill detects the Expo dependency, routes navigation work to expo-router, then routes the release work to eas-app-stores after verifying EAS auth and project linking.

Quick Start

Ask the agent to load the expo-overview skill first whenever the request mentions Expo, EAS, or the project has an expo dependency in package.json.

Frequently Asked Questions about expo-overview

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right Expo skill for my task?

Load expo-overview first and describe your goal in plain terms. It classifies the request using its skill map and routes you to the matching leaf skill, such as expo-router for navigation or eas-app-stores for store submission.

When should I load expo-overview versus a specific Expo skill directly?

Load expo-overview whenever the request mentions Expo or the project has an expo dependency, even if the task is fully specified. Skip it only when the user explicitly names a specific expo-* or eas-* skill.

Does expo-overview apply to bare React Native projects?

No. A bare React Native project without an expo dependency in package.json is not Expo work, and the skill explicitly does not apply. It requires either an Expo mention in the request or an expo dependency.

How do I install packages in an Expo project correctly?

Use npx expo install <pkg> instead of npm, yarn, or pnpm add. This keeps package versions compatible with the project's Expo SDK, which the skill detects from package.json before giving version-specific advice.

Why does Expo documentation advice differ between SDK versions?

APIs and defaults change between SDK releases, so the skill reads version-pinned docs like /versions/v56.0.0/ instead of /latest/. The latest pages may document APIs the project's SDK does not have yet.

What is required before using EAS build or submit commands?

Verify login with eas whoami or eas login, and confirm the project is linked by checking for extra.eas.projectId in the app config. Run eas init to create the project link if it is missing.