Expo Examples
sickn33/agentic-awesome-skills
Expo's official example projects — the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more).
Expo's official example projects - the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more).
$ npx skills add expo/skills --skill expo-examples -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install expo/skills expo-examples --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/expo/skills/expo-examples .claude/skills/expo-examples && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .claude/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examplesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add expo/skills --skill expo-examples -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install expo/skills expo-examples --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/expo/skills/expo-examples .agents/skills/expo-examples && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .agents/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add expo/skills --skill expo-examples -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install expo/skills expo-examples --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/expo/skills/expo-examples .cursor/skills/expo-examples && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .cursor/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/expo/skills.git --path plugins/expo/skills/expo-examples--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add expo/skills --skill expo-examples -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install expo/skills expo-examples --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/expo/skills/expo-examples .gemini/skills/expo-examples && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .gemini/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install expo/skills expo-examplesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add expo/skills --skill expo-examples -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/expo/skills/expo-examples .github/skills/expo-examples && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .github/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add expo/skills --skill expo-examples -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install expo/skills expo-examples --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/expo/skills/expo-examples .opencode/skills/expo-examples && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "expo-examples" agent skill from https://github.com/expo/skills/tree/main/plugins/expo/skills/expo-examples into .opencode/skills/expo-examples/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-examples", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
expo-examplesExpo's official example projects - the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more).
Expo Examples is an agent skill from expo/skills, published by the product's own GitHub organization. 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.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/catalog.md`).
It sits in Mobile, covering Cross-platform mobile apps. It works with Expo, Stripe, OpenAI and Supabase. The repository describes itself as: A collection of AI agent skills for working with Expo projects and Expo Application Services. The licence is MIT.
2 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d4f4840. It shows what the files ask for, not the result of running them.
Pre-approves these tools, so the agent can use them without asking each time:
ReadBash(gh api:*)Bash(git clone:*)Bash(npx create-expo:*)Bash(npx degit:*)Bash(bun create:*)From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
ghnpxgitcurlbunFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comlaunch.expo.devraw.githubusercontent.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Expo Examples loads about 1.7k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 669 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check noted patterns worth knowing about, such as sudo or a known installer.
ntegration code the manifest revealed → `.env` (required secrets). Per file:*Recreate env vars** from the example's `.env` shape — it holds placeholders, never working secrets.Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from expo/skills at commit d4f4840, republished under its MIT licence (© expo). 669 words, ~1,666 tokens.
.claude/skills/expo-examples/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.expo/examples is Expo's official library of ~70 integration examples — directories named with-<library> (e.g. with-stripe, with-maps), each built around one library or service. These are not full apps: they're managed projects (no ios//android/ dirs — native setup is via config plugins), and the typical one is a single screen of ~100–200 lines. Mine them for the canonical integration pattern — the dependency set, app.json config plugins, and minimal wiring Expo maintains against the current SDK — and adapt that into the user's app. Don't expect to lift an application architecture from them.
Reach for an example before hand-rolling an integration. (Kinds — full-stack, showcases, starters — are noted in ./references/catalog.md.)
Map the user's need to an example name (e.g. payments → with-stripe, auth → with-clerk). ./references/catalog.md is a categorized snapshot for fast triage — but it drifts, so confirm against the live list:
# Live example names:
gh api repos/expo/examples/contents --jq '.[] | select(.type=="dir" and (.name|startswith(".")|not)) | .name'
# Aliases (renamed) + deprecated (dead/moved) examples — check before recommending:
gh api repos/expo/examples/contents/meta.json --jq '.content' | base64 -dmeta.json is the source of truth for what's renamed or dead (deprecated examples are removed from the repo tree but still listed here, each with a message). If an example is in its deprecated map, don't recommend it — follow the message to the modern path. If it's in aliases, use the destination.
The common case: the user already has an app and wants to see how Expo does something. Read the example as reference and apply the patterns by hand — never scaffold an example on top of their project.
First, list the whole example in one call. Integration code is often nested (e.g. Stripe's server routes live in app/api/), so a one-level listing misses the important files:
gh api 'repos/expo/examples/git/trees/master?recursive=1' \
--jq '.tree[].path | select(startswith("with-stripe/"))'Then read the high-signal files first: README.md (setup) → package.json (deps) → app.json (config plugins / permissions) → the integration code the manifest revealed → .env (required secrets). Per file:
gh api repos/expo/examples/contents/with-stripe/utils/stripe-server.ts --jq '.content' | base64 -d
# No gh? Raw URL (branch is master):
curl -s https://raw.githubusercontent.com/expo/examples/master/with-stripe/utils/stripe-server.tsReading more than a couple of files? Many integrations are spread across server routes, a client provider, and config (Stripe is). Skip the per-file calls — pull the whole example into a throwaway/gitignored dir (not the user's project) and read it freely with Grep/Read, then apply by hand:
npx degit expo/examples/with-stripe /tmp/expo-ref/with-stripe # clean copy, no git history
# fallback without degit (sparse-checkout, no full ~64 MB clone):
git clone --depth 1 --filter=blob:none --sparse https://github.com/expo/examples.git /tmp/expo-ref/examples \
&& (cd /tmp/expo-ref/examples && git sparse-checkout set with-stripe)Read from there with Grep/Read; delete the scratch dir when done.
npx create-expo --example with-stripe # short form: npx create-expo -e with-stripe
bun create expo --example with-stripe # with bunWhen the user already has an app, add only what the example introduces; never overwrite their setup.
package.json pins won't match an older project. Add only the missing deps with npx expo install <pkg> (it resolves SDK-correct versions) instead of copying exact versions.app.json/app.config.* plugins and permissions the example introduces that the user lacks — keep their existing config block intact..env shape — it holds placeholders, never working secrets.Done when the integration code is ported and every dependency, config plugin, permission, and env var it needs is accounted for in the user's app — not when it merely looks wired up.
master, not main (matters for raw URLs and sparse checkout).https://launch.expo.dev/?github=https://github.com/expo/examples/tree/master/<example>.expo-uiexpo-native-uiexpo-routerexpo-moduleexpo-upgrade./references/catalog.md — categorized snapshot of the example library for fast triage.If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:
npx --yes submit-expo-feedback@latest --category skills --subject "expo-examples" "<actionable feedback>"Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.
© expo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 2 other files (references) in plugins/expo/skills/expo-examples of expo/skills.
Open the folder on GitHubat commit d4f4840
Expo Examples next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Expo Examples this skillexpo/skills | 2.7k | — | ~1.7k | Automated safety check: Notes | MIT | |
| Expo Examplessickn33/agentic-awesome-skills | 47k | 1 repos | ~1.7k | Automated safety check: Notes | MIT | |
| Find Skillsrohitg00/skillkit | 1.5k | — | ~1.2k | Automated safety check: Pass | Apache-2.0 | |
| App IconCode-with-Beto/skills | 140 | — | ~2.4k | Automated safety check: Pass | None | |
| Toolifycoreyhaines31/makerskills | 850 | — | ~2.9k | Automated safety check: Notes | MIT | |
| Credentialsalinaqi/maggy | 707 | — | ~2.4k | Automated safety check: Notes | MIT |
sickn33/agentic-awesome-skills
Expo's official example projects — the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more).
rohitg00/skillkit
Discovers, searches, and installs skills from multiple AI agent skill marketplaces (400K+ skills) using the SkillKit CLI.
Code-with-Beto/skills
Generate app icons for your React Native Expo app with iOS 26 support
coreyhaines31/makerskills
When you want to integrate an external tool, API, MCP server, or service into a project — the wizard walks you through auth, config, env vars, client wrapper code, example usage, and an optional…
alinaqi/maggy
Centralized API key management from Access.txt. An agent skill from alinaqi/maggy.
vercel-labs/openreview
A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.
expo/skills
Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel.
expo/skills
Helps understand and write EAS workflow YAML files for Expo projects.
expo/skills
Add an iOS App Clip target to an Expo app. An agent skill from expo/skills.
expo/skills
Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional).
expo/skills
Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in).
expo/skills
Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).
Categories
Expo's official example projects - the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more). Expo Examples is an agent skill from expo/skills, published by the product's own GitHub organization. Expo's official example projects - the expo/examples repo of ~70 with- integrations (Stripe, Clerk, Supabase, OpenAI, maps, Reanimated, SQLite, Skia, NativeWind, and more).
Expo Examples fits situations like: integrating a third-party library; service into an existing Expo app and you want the canonical; version-matched pattern to adapt; scaffolding a new project from one with npx create-expo --example.
Run `npx skills add expo/skills --skill expo-examples -a claude-code`. Or copy the skill folder (plugins/expo/skills/expo-examples in expo/skills) into .claude/skills/expo-examples in your project. Claude Code loads it when a task matches its description.
Run `npx skills add expo/skills --skill expo-examples -a codex`. Or copy the skill folder (plugins/expo/skills/expo-examples in expo/skills) into .agents/skills/expo-examples in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add expo/skills --skill expo-examples -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/expo-examples, .gemini/skills/expo-examples, .github/skills/expo-examples and .opencode/skills/expo-examples in your project.
Going by SKILL.md and its folder, Expo Examples needs the command-line tools its instructions call (gh, npx, git, curl and bun). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Bash(gh api:*), Bash(git clone:*), Bash(npx create-expo:*), Bash(npx degit:*), Bash(bun create:*).
SKILL.md names 3 domains. In commands or code: github.com, launch.expo.dev and raw.githubusercontent.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
Expo Examples is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Expo Examples: Expo Examples (sickn33/agentic-awesome-skills, 47k stars), Find Skills (rohitg00/skillkit, 1.5k stars), App Icon (Code-with-Beto/skills, 140 stars) and Toolify (coreyhaines31/makerskills, 850 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
expo (a GitHub organization, an official publisher) maintains it in expo/skills, which has 2,685 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 7, 2026.
Source: expo/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.