expo-overview
An agent skill by expo, from expo/skills. Tags: analysis, developer-tools, expo, planning, routing, strategy.
What it does
Framework (OSS). 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.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-overview
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/expo-overview ~/.claude/skills/expo-overview
Safety box score
Grade B, low risk: 19 of 100 risk points, rated 2026-10-16. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill is a router and shared-rules entry point for Expo/EAS work, not a feature implementation skill. Its main risks are that it tells the agent to run remote `npx` commands and, for some Expo/EAS tasks, to use account-linked network operations such as EAS login, feedback submission, and build/submit workflows.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | It explicitly directs the agent to run registry packages with `npx create-expo-app@latest`, `npx expo install <pkg>`, and `npx --yes submit-expo-feedback@latest`, which executes downloaded package code but in a bounded workflow. |
| Network access | 1 (low) | The skill relies on network access for npm registry downloads, Expo docs URLs, EAS auth (`eas whoami` / `eas login`), and the optional feedback submission command in `SKILL.md`. |
| Filesystem reach | 1 (low) | It can create and modify project files when starting a new app (`npx create-expo-app@latest`) and installing packages (`npx expo install <pkg>`), but it does not instruct edits outside the working project. |
| Secrets & credentials | 1 (low) | The shared rules include EAS account checks and login (`eas whoami`, `eas login`), which can involve personal account credentials even though it does not directly read local secret stores. |
| Privilege & persistence | 0 (none) | No sudo, service registration, global installs, shell startup edits, or other privilege-escalating actions are described. |
| Instruction hijack surface | 0 (none) | The file contains routing guidance and confirmations like `Confirm intent if ambiguous`, but no prompt-injection tactics such as hiding instructions, skipping safeguards, or following remote instructions. |
| Irreversible actions | 1 (low) | As a router for build/submit/update tasks, it can lead the agent into actions like app scaffolding or feedback submission, but it still requires task-specific leaf skills and does not itself deploy or publish. |
| Transparency | 0 (none) | All reviewed content is plain text Markdown/YAML; there are no binaries, minified blobs, or runtime-decoded payloads. |
Before installing
- Read the leaf skill it routes to before allowing any `npx` command to run.
- Confirm you are okay with remote package execution (`create-expo-app`, `expo install`, and possibly `submit-expo-feedback`).
- If the project is not Expo-related, do not let the router activate just because `package.json` exists.
- Run the setup once in a scratch repo if you want to see exactly what files `create-expo-app@latest` adds.
Rated 2026-10-16 by an automated review of 2 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-overview/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- marketing-plan — When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product.
- seo-cluster — SERP-based semantic topic clustering for content architecture planning.
- seo-plan — Strategic SEO planning for new or existing websites. Industry-specific templates, competitive analysis, content strategy, and implementation roadmap.
- c-review — Performs comprehensive C/C++ security review for memory corruption, integer overflows, race conditions, and platform-specific vulnerabilities.
- co-marketing — When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities.
- create-learning-path — Build a personalized learning roadmap with milestones and practice checkpoints