How do I install the Native Data Fetching skill?

Run npx skillmds@latest add francostino/native-data-fetching in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Native Data Fetching safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Native Data Fetching?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Native Data Fetching free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Native Data Fetching?

FrancoStino (@francostino) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Native Data Fetching by francostino

Name: Native Data Fetching
Rating: 4.2 (5 reviews)
Author: FrancoStino

Native Data Fetching

Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).

FrancoStino Updated Sep 8, 2026 63 repo stars

File contents

Expo Networking

You MUST use this skill for ANY networking work including API requests, data fetching, caching, or network debugging.

Detailed Guide

Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.

When to Use

Use this skill when:

Implementing API requests
Setting up data fetching (React Query, SWR)
Using Expo Router data loaders (useLoaderData, web SDK 55+)
Debugging network failures
Implementing caching strategies
Handling offline scenarios
Authentication/token management
Configuring API URLs and environment variables

Example Invocations

User: "How do I make API calls in React Native?" -> Use fetch, wrap with error handling

User: "Should I use React Query or SWR?" -> React Query for complex apps, SWR for simpler needs

User: "My app needs to work offline" -> Use NetInfo for status, React Query persistence for caching

User: "How do I handle authentication tokens?" -> Store in expo-secure-store, implement refresh flow

User: "API calls are slow" -> Check caching strategy, use React Query staleTime User: "How do I configure different API URLs for dev and prod?" -> Use EXPOPUBLIC env vars with .env.development and .env.production files User: "Where should I put my API key?" -> Client-safe keys: EXPOPUBLIC in .env. Secret keys: non-prefixed env vars in API routes only

User: "How do I load data for a page in Expo Router?" -> See references/expo-router-loaders.md for route-level loaders (web, SDK 55+). For native, use React Query or fetch.

Limitations

Use this skill only when the task clearly matches its upstream product or API scope.
Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.
Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

---name: native-data-fetchingdescription: Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, React Query, SWR, error handling, caching, offline support, and Expo Router data loaders (`useLoaderData`).license: MIT---# Expo Networking**You MUST use this skill for ANY networking work including API requests, data fetching, caching, or network debugging.**## Detailed GuideRead [the detailed guide](references/detailed-guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.## When to UseUse this skill when:- Implementing API requests- Setting up data fetching (React Query, SWR)- Using Expo Router data loaders (`useLoaderData`, web SDK 55+)- Debugging network failures- Implementing caching strategies- Handling offline scenarios- Authentication/token management- Configuring API URLs and environment variables## Example InvocationsUser: "How do I make API calls in React Native?"-> Use fetch, wrap with error handlingUser: "Should I use React Query or SWR?"-> React Query for complex apps, SWR for simpler needsUser: "My app needs to work offline"-> Use NetInfo for status, React Query persistence for cachingUser: "How do I handle authentication tokens?"-> Store in expo-secure-store, implement refresh flowUser: "API calls are slow"-> Check caching strategy, use React Query staleTimeUser: "How do I configure different API URLs for dev and prod?"-> Use EXPO*PUBLIC* env vars with .env.development and .env.production filesUser: "Where should I put my API key?"-> Client-safe keys: EXPO*PUBLIC* in .env. Secret keys: non-prefixed env vars in API routes onlyUser: "How do I load data for a page in Expo Router?"-> See references/expo-router-loaders.md for route-level loaders (web, SDK 55+). For native, use React Query or fetch.## Limitations- Use this skill only when the task clearly matches its upstream product or API scope.- Verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes.- Do not treat generated examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Frequently asked questions