native-data-fetching
Build Expo Networking Flows
Mobile apps need reliable API requests, caching, token handling, and offline behavior. This skill guides Expo developers through fetch, React Query, SecureStore, NetInfo, and environment-based configuration.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "native-data-fetching" from https://skillstore.io/skills/expo-native-data-fetching.md and its manifest at https://skillstore.io/api/skills/expo-native-data-fetching/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "native-data-fetching". Create a fetch pattern for a user profile screen.
Expected outcome:
- A recommended request flow with loading, error, and success states.
- A response-status check before parsing data.
- Notes for replacing placeholder API URLs.
Using "native-data-fetching". Plan API configuration for dev and production.
Expected outcome:
A concise environment plan using public client URLs, separate development and production values, and a warning to keep secrets server-side.
Using "native-data-fetching". Debug unreliable mobile API calls.
Expected outcome:
A troubleshooting checklist covering connectivity, HTTP status handling, retry timing, cache staleness, and request cancellation.
Security Audit
SafeAll static findings appear to be false positives caused by Markdown fences, TypeScript template literals, placeholder fetch calls, and Expo environment-variable examples in SKILL.md. The skill is documentation-only and includes advice to avoid putting secrets in EXPO_PUBLIC variables. No semantic evidence of shell execution, secret collection, data exfiltration, or prompt injection was found.
Risk Factors
⚙️ External commands (58)
🌐 Network access (17)
🔑 Env variables (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/expo-native-data-fetching/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/expo-native-data-fetching?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/expo-native-data-fetching?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/expo-native-data-fetching/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/expo-native-data-fetching.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
expo. (2026). native-data-fetching security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/expo-native-data-fetching/audits/5BibTeX citation
@techreport{expo-expo-native-data-fetching-2026,
author = {expo},
title = {native-data-fetching security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/expo-native-data-fetching/audits/5},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "native-data-fetching security audit report (audit version 5)"
version: "1.0.0"
type: report
authors:
- name: "expo"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/expo-native-data-fetching/audits/5"
identifiers:
- type: other
value: "skillstore:expo-native-data-fetching:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Ship Reliable API Calls
An Expo developer can add fetch wrappers, status checks, and typed errors for a new mobile feature.
Choose a Caching Strategy
A technical lead can compare simple fetch patterns with React Query for shared server state.
Prepare Offline Authentication
A product engineer can combine SecureStore, NetInfo, and retry behavior for authenticated offline-capable screens.
Try These Prompts
Show me how to fetch a user profile in an Expo app with error handling and loading states.
Help me set up React Query in an Expo Router app and add a user detail query with cache settings.
Design an authenticated fetch wrapper for an Expo app that stores tokens in SecureStore and refreshes expired tokens.
Audit this Expo networking layer for caching, retries, offline behavior, request cancellation, and environment configuration. Suggest prioritized changes.
Best Practices
- Keep API base URLs in Expo public environment variables only when they are safe for client bundles.
- Use SecureStore for authentication tokens and avoid AsyncStorage for sensitive values.
- Handle failed HTTP status codes before parsing success data.
Avoid
- Do not place write-capable API keys or database passwords in EXPO_PUBLIC variables.
- Do not assume fetch throws for non-2xx HTTP responses.
- Do not add retries without backoff, cancellation, and clear user feedback.
Frequently Asked Questions
Does this skill run network requests?
Does it require axios?
Can it help with React Query?
How should tokens be stored?
Are EXPO_PUBLIC variables safe for secrets?
Can it help offline apps?
Developer Details
Author
expoLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Repository
https://github.com/expo/skills/tree/main/plugins/expo-app-design/skills/native-data-fetching/Ref
a06681402992ceae98ba04d54cfd4ab004862696
Maintenance freshness
7/18/2026
Usage
5 downloads · 194 views
File structure
📄 SKILL.md