Expo Skills
Official Expo AI agent skills for building, deploying, upgrading, observing, and debugging Expo and React Native apps with Expo Router, EAS, native modules, App Clips, Tailwind, native UI, and EAS Update insights.
Open the source and read safety notes before installing.
Safety notes
- Expo Skills can guide agents through native project changes, EAS builds, store submissions, EAS Update rollouts, and EAS Observe queries; those actions can affect real apps and users.
- Do not let an agent trigger EAS builds, submissions, rollouts, or production updates without reviewing project, profile, branch, runtime version, and account context.
- Native modules, config plugins, App Clips, brownfield integration, and prebuild steps can modify iOS and Android project files; inspect diffs before committing.
- Follow the skill's Expo Go-first guidance before creating custom native builds unless custom native code or platform targets require them.
Privacy notes
- Expo and EAS work can involve bundle identifiers, project IDs, app metadata, Apple and Google credentials, service account files, release channels, crash metrics, user counts, update payload sizes, screenshots, and build logs.
- Keep Expo tokens, Apple credentials, Google service account JSON, signing keys, keystore files, secrets, private crash data, and unpublished app metadata out of prompts, public PRs, screenshots, and logs.
- The Expo plugin can bundle MCP configuration; connected agents may access docs, EAS services, simulator screenshots, build status, workflow state, or update health depending on granted permissions.
Prerequisites
- Claude Code, Codex, Cursor, or another Agent Skills-compatible AI coding agent.
- Expo or React Native project when applying project-specific skills.
- Expo CLI, EAS CLI, simulator/device, or Expo account access when building, deploying, observing, or querying EAS state.
- Current Expo docs, Expo CLI help, EAS CLI help, or Expo MCP access for exact commands and service behavior.
Schema details
- Install type
- package
- Reading time
- 8 min
- Difficulty score
- 76
- Troubleshooting
- Yes
- Breaking changes
- No
- Scope
- Source repo
- Skill type
- capability-pack
- Skill level
- expert
- Verification
- validated
- Verified at
- 2026-06-18
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Claude Code
/plugin install expo@claude-plugins-official
# Codex
codex plugin add expo@openai-curated
# Skills CLI
npx skills add expo/skillsAbout this resource
Expo Skills
expo/skills is Expo's official skill repository and plugin package for AI
coding agents working on Expo and React Native apps. It teaches agents how to
build native-feeling UI, configure Expo Router, use EAS Build and EAS Workflows,
upgrade Expo SDKs, work with native modules, inspect EAS Update health, and
handle mobile deployment workflows.
The official docs position Expo documentation, Expo CLI, and EAS CLI as the source of truth. The skills help agents apply that guidance inside real projects without guessing from stale model memory.
Knowledge Freshness
Expo SDKs, React Native versions, EAS CLI behavior, Expo Router conventions, native module APIs, Apple and Google store requirements, and EAS Update health signals change over time. Use the skill pack for workflows and guardrails, then verify exact commands against current Expo docs, CLI help, package versions, and the target project's config.
The companion Expo MCP server can provide live docs and EAS access when a project has been configured for that level of agent authority.
Retrieval Sources
This listing is grounded in:
- Expo's official
expo/skillsGitHub repository. - Expo's
docs.expo.dev/skills.mddocumentation page. - The repository README and
skills.sh.jsongrouping metadata. - Representative skill manifests for
building-native-ui,expo-deployment,expo-module,eas-update-insights, andupgrading-expo. - The Codex plugin metadata for the official Expo plugin.
- The MIT license file.
Core Workflow
Claude Code users can install from the official Claude Code plugin marketplace:
/plugin install expo@claude-plugins-official
Codex users can install from the OpenAI-curated marketplace:
codex plugin add expo@openai-curated
Cursor and other Agent Skills-compatible tools can use the skills CLI:
npx skills add expo/skills
After installing, ask an Expo-specific task such as "upgrade this app to the latest Expo SDK", "build an Expo Router settings screen", "create an EAS workflow for PR previews", or "check whether this EAS Update rollout is healthy". The agent should load the relevant skill automatically.
Capability Scope
Expo currently publishes skills across app design, native/platform work, deployment, observability, and maintenance:
| Skill | Scope |
|---|---|
building-native-ui |
Expo Router screens, navigation, styling, animations, native tabs, UI patterns, safe-area behavior, and Expo Go-first development |
native-data-fetching |
Fetch API, React Query, SWR, caching, offline support, and Expo Router data loaders |
expo-api-routes |
Expo Router API routes with EAS Hosting |
expo-tailwind-setup |
Tailwind CSS v4, react-native-css, and NativeWind v5 setup |
use-dom |
Expo DOM components for gradually using web code in native apps |
expo-dev-client |
Local and TestFlight development client builds |
expo-module |
Expo native modules and views with Swift, Kotlin, TypeScript, config plugins, lifecycle hooks, and autolinking |
expo-ui |
@expo/ui native UI with SwiftUI and Jetpack Compose surfaces |
add-app-clip |
iOS App Clip targets, AASA files, associated domains, and Smart App Banners |
expo-brownfield |
Adding Expo or React Native to existing iOS or Android apps |
expo-deployment |
EAS Build, EAS Submit, app stores, TestFlight, Play Store, web hosting, and API route deployment |
expo-cicd-workflows |
EAS Workflow YAML, CI/CD automation, preview builds, and deployment pipelines |
expo-observe |
EAS Observe setup and launch, route, event, and version metrics |
eas-update-insights |
EAS Update health, crash rates, launch counts, unique users, payload size, and rollout gates |
upgrading-expo |
Expo SDK upgrades, dependency conflicts, deprecated package migrations, and cache cleanup |
Production Rules
Use Expo Skills to improve agent accuracy, but keep production authority explicit:
- Verify whether a task works in Expo Go before creating a custom development build.
- Review
app.json,eas.json, workflows, native project files, config plugins, and generated native module code before committing. - Check target platforms, profiles, channels, branches, runtime versions, and store accounts before running EAS build, submit, update, or workflow commands.
- Inspect EAS Update health and crash signals before expanding rollouts.
- Keep production secrets, signing credentials, service account files, and unpublished app metadata outside prompts and commits.
- Test on real devices or simulators when changing navigation, native modules, App Clips, updates, notifications, deep links, or platform-specific UI.
Use Cases
- Ask Codex to upgrade an Expo SDK and resolve deprecated packages.
- Let Claude Code generate an Expo Router screen with native-feeling UI and safe-area behavior.
- Use Cursor to create an EAS Workflow that builds preview apps on pull requests.
- Ask an agent to inspect EAS Update crash rate and launch data before a rollout continues.
- Pair the Expo plugin's skills with Expo MCP when the agent needs live docs, compatible dependency installation, EAS build monitoring, or simulator screenshots.
Source Review
- Expo's docs page describes Expo Skills as official AI agent skills for building, deploying, and debugging Expo and React Native apps.
- The docs page documents Claude Code plugin installation,
codex plugin add expo@openai-curated, and skills CLI installation for Cursor and other agents. - The docs page lists the current skill inventory and links each skill manifest.
- The README describes the repository as official Expo-authored skills for building, deploying, upgrading, and debugging Expo apps.
skills.sh.jsongroups skills into App Design, Native Platform, Deploy and Observe, and Maintenance.- The Codex plugin metadata identifies the
expoplugin as official Expo skills with read, write, interactive, and MCP capabilities.
Duplicate Review
Checked current content/skills/, content/tools/, content/mcp/, open pull
requests, and repository-wide content for Expo Skills, Expo Agent Skills,
expo/skills, expo codex plugin, EAS skills, and Expo MCP skills.
Existing Expo MCP content covers the MCP server, but no dedicated official Expo
Skills entry, exact source URL duplicate, target file, or open duplicate PR was
found.
Disclosure
Editorial listing. No paid placement or affiliate link is used. Expo Skills are published by Expo under the MIT license. Expo also offers hosted EAS services and commercial developer infrastructure outside this directory.
Source citations
Add this badge to your README
How it compares
Expo Skills side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Expo Skills Official Expo AI agent skills for building, deploying, upgrading, observing, and debugging Expo and React Native apps with Expo Router, EAS, native modules, App Clips, Tailwind, native UI, and EAS Update insights. Open dossier | GSAP AI Skills Official GreenSock GSAP AI Skills for coding agents that need correct GSAP tweens, timelines, ScrollTrigger, React cleanup, plugins, utilities, framework lifecycle guidance, and animation performance patterns. Open dossier | WordPress Agent Skills WordPress contributor-reviewed Agent Skills for AI coding assistants working on Gutenberg blocks, block themes, plugins, REST APIs, Interactivity API, Abilities API, WP-CLI, Playground, performance, PHPStan, and directory rules. Open dossier | .NET Agent Skills Microsoft .NET team skill marketplace for AI coding agents working on .NET, C#, ASP.NET Core, Blazor, MAUI, diagnostics, MSBuild, NuGet, upgrades, tests, AI workflows, RAG pipelines, and C# MCP servers. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | skills | skills | skills | skills |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Expo | GreenSock | WordPress Contributors | .NET Team at Microsoft |
| Added | 2026-06-18 | 2026-06-18 | 2026-06-18 | 2026-06-18 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLIVS Code |
| Source repo | — | — | — | — |
| Safety notes | ✓Expo Skills can guide agents through native project changes, EAS builds, store submissions, EAS Update rollouts, and EAS Observe queries; those actions can affect real apps and users. Do not let an agent trigger EAS builds, submissions, rollouts, or production updates without reviewing project, profile, branch, runtime version, and account context. Native modules, config plugins, App Clips, brownfield integration, and prebuild steps can modify iOS and Android project files; inspect diffs before committing. Follow the skill's Expo Go-first guidance before creating custom native builds unless custom native code or platform targets require them. | ✓GSAP is primarily a frontend animation library, but generated animations can still break layout, accessibility, input handling, scroll behavior, or client performance. ScrollTrigger, pinned sections, smooth scrolling, and layout-dependent timelines should be tested across viewport sizes and after dynamic content loads. React, Vue, Svelte, and other framework integrations need cleanup on unmount so animations, event listeners, and ScrollTriggers do not leak across renders. Remove development markers, debug helpers, and unnecessary long-running animations before production. | ✓WordPress plugin, theme, REST API, WP-CLI, database, cron, and performance changes can affect production sites, admin access, public endpoints, stored content, and user data. Security-sensitive work needs capability checks, nonces, sanitization, escaping, prepared SQL, REST permission callbacks, and explicit authorization review. Block changes can create Invalid block errors if saved markup changes without proper deprecations and migrations. Do not run WP-CLI write operations, database migrations, search-replace, cron tasks, plugin activation, or cache flushes on production without explicit approval and backups. The repo discloses AI-assisted generation from official WordPress and Gutenberg documentation followed by WordPress contributor review; still verify against current project constraints. | ✓.NET build, test, upgrade, package, template, publish, and migration tasks can modify project files, lock files, generated code, packages, app settings, and deployment artifacts. Diagnostics skills may suggest collecting traces, dumps, counters, crash data, MSBuild binlogs, or performance profiles; collect those artifacts only with explicit approval and storage controls. MCP server skills can expose local code, files, APIs, credentials, or production services as callable tools; review tool descriptions, parameter validation, authorization, and transport choice before connecting clients. NuGet and publish workflows can push packages or artifacts to public or private feeds; verify package IDs, versions, API keys, feed targets, and release policy before publishing. Upgrade and modernization guidance should be verified against each application's framework support window, deployment target, package compatibility, and rollback plan. |
| Privacy notes | ✓Expo and EAS work can involve bundle identifiers, project IDs, app metadata, Apple and Google credentials, service account files, release channels, crash metrics, user counts, update payload sizes, screenshots, and build logs. Keep Expo tokens, Apple credentials, Google service account JSON, signing keys, keystore files, secrets, private crash data, and unpublished app metadata out of prompts, public PRs, screenshots, and logs. The Expo plugin can bundle MCP configuration; connected agents may access docs, EAS services, simulator screenshots, build status, workflow state, or update health depending on granted permissions. | ✓The skills are local instruction files and do not require app data by themselves. Do not paste proprietary designs, private Figma exports, customer analytics, unreleased campaign copy, or private frontend source into public prompts or issues when asking an agent to animate UI. If the agent uses browser automation, visual captures, or external model providers while applying these skills, screenshots and source snippets may be processed outside the local project. | ✓WordPress work can expose database content, user accounts, emails, cookies, nonces, application passwords, REST payloads, site URLs, plugin settings, telemetry, performance profiles, and logs. Keep wp-config secrets, salts, database credentials, application passwords, admin cookies, production exports, customer data, and private plugin code out of prompts, screenshots, issues, and public PRs. When using Playground, mounted local code may be copied into an in-memory filesystem; check that the mounted project does not contain secrets before sharing snapshots or repro links. | ✓.NET repositories may contain connection strings, appsettings secrets, user secrets, certificates, environment variables, telemetry keys, logs, traces, dumps, package credentials, and production data. MSBuild binlogs, crash dumps, profiler output, and test artifacts can contain source paths, dependency graphs, request data, exception payloads, configuration values, and environment details. MCP servers created with these skills may forward prompts and tool inputs to local processes, HTTP services, databases, cloud APIs, or third-party model providers depending on the implementation. Keep private NuGet credentials, signing keys, deployment secrets, customer data, dumps, and proprietary source out of public prompts, issues, pull requests, and shared artifacts. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.