expo-data-fetching
An agent skill by expo, from expo/skills. Tags: analysis, api, caching, react, troubleshooting, validation.
What it does
Framework (OSS). Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, loading/empty/error screen states, and Expo Router data loaders (`useLoaderData`).
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-data-fetching
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-data-fetching ~/.claude/skills/expo-data-fetching
Safety box score
Grade C, moderate risk: 28 of 100 risk points, rated 2026-09-22. 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 documentation for Expo networking and data fetching; it does not ship executable code, but it guides an agent to make HTTP requests, handle auth tokens, and use server-side route loaders. The main risks are secret exposure in loaders and environment variables, plus the optional `npx` feedback command that downloads and runs a registry package.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 1 (low) | The skill itself is markdown, but it includes runnable commands such as `npx expo export` and `npx --yes submit-expo-feedback@latest ...`, which would execute code from the local project or registry if followed. |
| Network access | 2 (moderate) | Its core purpose is network I/O: examples call `fetch( |
| Filesystem reach | 1 (low) | It mentions working with `.env` files and app config, but there is no broad filesystem traversal, deletion, or editing outside the project scope. |
| Secrets & credentials | 2 (moderate) | It explicitly handles auth tokens with `expo-secure-store`, reads cookies in loaders, and uses server-only env vars like `process.env.STRIPE_SECRET_KEY`, so it can touch sensitive credentials and session data. |
| Privilege & persistence | 0 (none) | There is no sudo, global install, service registration, shell startup modification, or other privilege escalation in the files. |
| Instruction hijack surface | 0 (none) | The files do not tell the agent to ignore its rules, hide behavior, follow remote instructions, or bypass confirmations. |
| Irreversible actions | 1 (low) | The only outbound action beyond normal fetching is the optional feedback command `npx --yes submit-expo-feedback@latest ...`, which sends a report to Expo, but it is user-invoked rather than automatic. |
| Transparency | 0 (none) | All shipped files are plain text Markdown/YAML; there are no binaries, minified blobs, or decoded-at-runtime code. |
Before installing
- Read `references/expo-router-loaders.md` and confirm you want server-side cookie/env access in route loaders.
- Audit every `EXPO_PUBLIC_` variable you plan to use; do not place secrets there.
- Decide whether you will ever run `npx --yes submit-expo-feedback@latest`; it downloads and runs a package from the registry.
- If you only need native data fetching, ignore the web-only loader path and use client-side fetch/React Query instead.
Rated 2026-09-22 by an automated review of 4 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-data-fetching/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- principle-fix-root-causes — Apply when debugging.
- seo-technical — Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering.
- X MCP guide — ALWAYS read this when a user connects the X plugin or any X MCP, before using any X connection, and again on any X error.
- investigate-first — Diagnose ambiguous failures before editing.
- aws-database — Routes any task involving AWS databases — choosing, comparing, recommending, getting started with.
- aws-sdk-js-v3-usage — AWS SDK for JavaScript v3 development patterns.