expo-overview

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

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill expo-overview-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-overview
Source: https://github.com/gmackie/agent-skills/tree/main/skills/expo-overview
Command: npx skills add https://github.com/gmackie/agent-skills --skill expo-overview-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Expo and EAS work spans many specialized skills, and picking the wrong one from project files alone leads to incorrect guidance. This Skill acts as the mandatory entry point that confirms a task is Expo work, classifies the user's goal, and routes to the right expo-* or eas-* leaf skill. ## Core Features & Use Cases - Goal Classification and Routing: Translates casual phrasings like "ship it" or "make it look native" into concrete goals and maps them to the correct leaf skill such as eas-app-stores, expo-router, or expo-ui. - Shared Setup Rules: Centralizes cross-cutting rules every Expo skill needs, including SDK version detection, version-pinned documentation URLs, npx expo install for packages, managed vs. bare project detection, and EAS authentication checks. - Use Case: A user says "add navigation to my app and ship to the App Store." This Skill confirms the expo dependency, detects the SDK version, then routes navigation work to expo-router and release work to eas-app-stores. ## Quick Start Use the expo-overview skill to classify my Expo app request and route me to the right expo or eas skill before writing any code.

Frequently Asked Questions about expo-overview

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

FAQPage Schema
How do I know which Expo skill to use for my task?▼

Load expo-overview first whenever the request mentions Expo or the project has an expo dependency. It classifies your goal using its skill map and routes you to the correct leaf skill such as expo-router for navigation or eas-app-stores for store submission.

How to route vague Expo requests like "make it look native"?▼

Translate the phrasing to a concrete goal first. Grouped controls and settings forms map to expo-ui, screens and styling map to expo-native-ui, and navigation maps to expo-router. The skill map in expo-overview handles this translation.

Does expo-overview apply to bare React Native projects?▼

No. A bare React Native project with no expo dependency in package.json is not Expo work, and this skill explicitly does not apply. It only activates when the request mentions Expo or an expo dependency exists.

Can I skip expo-overview if my task is fully specified?▼

No. A fully specified task with pinned SDK and named libraries still routes through expo-overview because the shared setup rules apply. Only skip it when the user explicitly names a specific expo-* or eas-* skill.

Why install Expo packages with npx expo install instead of npm?▼

npx expo install selects package versions compatible with the project's Expo SDK, while raw npm, yarn, or pnpm add can install incompatible versions. This is one of the shared setup rules applied across all Expo skills.