Expo Integration Examples
Adapt Expo’s official patterns for third-party integrations.
The skill constrains its tool set and explicitly requires read-only inspection, throwaway directories, non-destructive merging, and placeholder environment variables. However, gh, git clone, npx, bun, and remote repository access can create external effects or execute third-party code; per-step confirmation, source pinning, and rollback procedures are absent, so points are deducted.
The workflow is internally coherent and covers example naming, deprecation checks, version alignment, and several operational pitfalls. It depends on gh, network access, branch names, and changing external repository state, while providing no committed tests, diagnostic failure handling, or offline fallback. The static-review ceiling also prevents a higher score, so points are deducted.
The audience and two modes are clear: adapting integrations in an existing Expo app or scaffolding a new project. It also states that examples are not full application architectures. Trigger boundaries, input/output contracts, and non-fit cases remain limited; Chinese-language support is unspecified, and core operation depends on GitHub and related services whose mainland-China reachability is uncertain, so points are deducted.
The SKILL.md, catalog, agent metadata, and repository README provide clear structure, installation, updating, related-skill guidance, limitations, and MIT licensing. The skill lacks its own changelog, named maintenance responsibility, compatibility matrix, and troubleshooting guidance; the catalog is explicitly described as drifting, so points are deducted.
The intended value is concrete: locate canonical integration patterns, merge dependencies and config plugins safely, or scaffold from an example. The result is actionable, but it depends on the current contents of external examples and contains no file-level representative execution evidence or complete coverage; manual review and adaptation remain necessary, so the static ceiling requires a conservative deduction.
The skill supplies repository and meta.json verification paths, while repository CI checks plugin versions and skill limits. There is no committed test suite covering this skill's key paths or independent third-party reproduction evidence, so the conclusion rests mainly on documentation claims and points are deducted.
- Before running npx, bun, git clone, or remote GitHub commands, confirm source, version, and network permissions, and review install scripts and dependencies.
- catalog.md can drift; verify the live directory plus aliases and deprecated entries rather than relying on the snapshot alone.
- Scaffolding may create or modify project files; run it in an isolated directory after confirming the target path and retain a recoverable copy.
- Examples may involve payments, authentication, cloud storage, or API keys; never copy real secrets, and review permissions, server routes, and data flows.
- Chinese-language documentation and mainland-China network fallbacks are unspecified; core discovery and download steps may fail if GitHub is unreachable.
What does this skill do, and when should you use it?
This is one open-source skill in the expo/skills repository, focused on roughly 70 third-party integration examples in expo/examples. It helps an existing Expo app find a version-aligned implementation pattern and can also scaffold a new project from an example. The workflow examines dependencies, config plugins, permissions, environment variables, and integration code before applying changes non-destructively. It fits Expo developers who need a canonical integration starting point, but not users seeking a complete application architecture.
Maps a user need to an example name; queries the live example directory and meta.json through GitHub CLI for aliases and deprecated entries; lists an example's complete file tree; reads README.md, package.json, app.json, integration code, and .env; optionally obtains a temporary copy with degit or sparse Git checkout; runs create-expo or Bun commands for new projects; and proposes or applies an adaptation plan covering missing dependencies, config plugins, permissions, integration code, and environment variables.
- An existing Expo app needs an official integration pattern for Stripe, Clerk, Supabase, maps, or another third-party service.
- A project uses an older Expo SDK and needs to adapt a current example without copying incompatible pinned versions.
- A developer wants to start a new Expo project from an official with-* example.
- A developer needs to verify whether an example was renamed or deprecated before recommending it.
- An integration spans client code, server routes, and configuration files and requires a complete example listing.
What are this skill's strengths and limitations?
- Built around Expo’s official expo/examples repository of roughly 70 concrete integrations.
- Covers dependencies, config plugins, permissions, environment-variable shape, and minimal integration code.
- Recommends npx expo install for SDK-compatible dependency resolution instead of copying pinned versions.
- Supports both adaptation of existing apps and scaffolding of new projects.
- MIT-licensed, with official marketplace update paths for plugin installations.
- Examples are generally single-screen managed projects, not complete application architectures.
- Because examples track the latest SDK, older projects may need an upgrade or compatibility work.
- The workflow depends on network access, a shell, and command-line tools such as GitHub CLI.
- The source does not document a test suite or the skill’s cross-platform validation coverage.
- No standalone command for installing only expo-examples is documented.
How do you install this skill?
This skill is part of the expo/skills collection. Install all Expo skills with the Skills CLI: npx skills@latest add expo/skills --skill '*'. The Expo plugin can also be installed with claude plugin install expo@claude-plugins-official for Claude Code or codex plugin add expo@openai-curated for Codex. The source does not provide a separate installation command for only expo-examples.
How do you use this skill?
For an existing app, prompt the agent: “Find and adapt the official Stripe example for my Expo app.” The agent should confirm the live example list and meta.json, then inspect the target example and merge only missing dependencies, configuration, and code. For a new project, use npx create-expo --example with-stripe, npx create-expo -e with-stripe, or bun create expo --example with-stripe; confirm the example name against the live list first.