expo-examples
An agent skill by expo, from expo/skills. Tags: developer-tools, integration, react-native, research, templates.
What it does
Framework (OSS). Expo's official example projects - the expo/examples repo of ~70 `with-*` integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Use when integrating a third-party library or service into an existing Expo app and you want the canonical, version-matched pattern to adapt, or when scaffolding a new project from one with `npx create-expo --example`.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-examples
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-examples ~/.claude/skills/expo-examples
Safety box score
Grade C, moderate risk: 26 of 100 risk points, rated 2026-10-15. 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 read-only guide to Expo’s public example repository, but it does direct the agent to fetch remote repo data and, in scaffold mode, run network-fetched project generators. The main risks are network exposure, executing downloaded scaffolding tools, and accidentally handling app env/config files while adapting examples.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It explicitly permits running fetched tooling such as `npx create-expo --example <name>`, `bun create expo --example <name>`, `npx degit expo/examples/...`, and `gh api`, which can execute installer/scaffolding code. |
| Network access | 2 (moderate) | The workflow depends on remote fetches from GitHub and the registry, e.g. `gh api repos/expo/examples/...`, `curl -s https://raw.githubusercontent.com/...`, and `npx create-expo --example <name>`. |
| Filesystem reach | 1 (low) | It writes only as part of cloning/scaffolding and even suggests a throwaway path like `/tmp/expo-ref/with-stripe`, so blast radius is usually limited to the workspace unless the user points it elsewhere. |
| Secrets & credentials | 1 (low) | It tells the agent to read an example `.env` shape and recreate env vars, which can bring it near secret-bearing config, but it does not ask to exfiltrate or print real secrets. |
| Privilege & persistence | 0 (none) | There is no `sudo`, global install, service registration, or shell/OS setting change in `SKILL.md` or the shipped files. |
| Instruction hijack surface | 0 (none) | The files do not instruct the agent to ignore safety rules, hide actions, or follow untrusted instructions; the only remote-content guidance is ordinary repo inspection. |
| Irreversible actions | 1 (low) | Its actions are user-driven scaffolding/adaptation, not deployment or messaging; the only remote-facing mention is a launch URL and a feedback command, neither of which is an automatic side effect. |
| Transparency | 0 (none) | All shipped files are plain text Markdown/YAML; there are no binaries, minified blobs, or decoded-at-runtime code in the skill package. |
Before installing
- Confirm you are comfortable with the skill downloading code from GitHub and the npm registry during normal use.
- If you will use scaffold mode, run it in a scratch directory first and inspect the generated files before moving anything into your app.
- Read `SKILL.md` around the “Inspiration / adapt” vs “Scaffold” sections so you do not let it overwrite an existing project.
- Check any `.env` or config changes it proposes before copying them into a real app.
Rated 2026-10-15 by an automated review of 3 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-examples/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- caveman-explore — Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed.
- debugging-wizard — Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points.
- find-docs — Retrieves up-to-date documentation, API references, and code examples for any developer technology.
- vercel-react-native-skills — React Native and Expo best practices for building performant mobile apps.
- eas-observe — EAS service (paid). Use for anything related to EAS Observe - adding `expo-observe` to an Expo project (AppMetricsRoot/ObserveRoot HOC.
- expo-animation — Framework (OSS). Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate.