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.