Eddy (@ieddysun) on X

What it claims

Expo's official skills package targets two failures Eddy (@ieddysun) attributes to AI agents building Expo apps: inventing outdated APIs and placing routes inconsistently. The package splits Expo knowledge into narrowly scoped skills. The agent loads only the skill that matches the task rather than putting all Expo guidance into context. Eddy argues the skills will not go stale because they are official and Expo's docs are the source of truth. The thread gives no evidence for that claim.

How it works

Each skill covers one area:

• expo-router: file-based routing.
• expo-animation: motion built with Reanimated.
• expo-upgrade: known pitfalls in Expo SDK upgrades.
• eas-update: the health of over-the-air (OTA) releases.

The Expo MCP server is separate from the skills. It gives the agent live access to current docs, dependency installs that match the project, EAS build progress, and simulator screenshots of the running app.

How to use it

Cursor, Copilot, Windsurf and other agents install all skills through the skills CLI:

npx skills@latest add expo/skills --skill '*'

Claude Code and Codex install the package from their official plugin marketplaces instead. The thread says the marketplace route includes automatic updates. It does not say whether CLI installs update automatically, so CLI users should check whether they need to rerun the command to get new skill versions.

Limits

The source is a promotional X thread, not documentation. It lists four skills by name and does not say whether more exist. It gives no setup steps for the MCP server and no versions or supported SDK range. It also gives no licence and no measured result showing fewer invented APIs or routing errors.