Agent skill · data analytics · aiskillstore
expo-api-audit
Comprehensive audit of Expo/React Native app API integration layer. Use when asked to: (1) Review API interactions, auth handling, or token management, (2) Find hardcoded data or screens bypassing API, (3) Verify user interactions properly sync to backend, (4) Analyze offline behavior and caching, (5) Audit Orval/OpenAPI code generation, (6) Check for API security issues. Supports TanStack Query, Zustand, axios, Expo Router, expo-secure-store, and expo-constants patterns.
Why this skill is useful
Provides specific commands and checks for auditing API integrations in Expo/React Native apps that the AI wouldn't reliably generate on its own.
What it needs
Requires ripgrep installed locally. About 8k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Expo API Integration Audit Overview This skill audits an Expo (React Native) TypeScript app's API integration layer to identify gaps, hardcoded data, auth issues, and offline behavior problems. Designed for apps using Expo Router, expo-secure-store, and expo-constants. Inputs Before starting, gather from the user: Known issues (optional): Specific screens or flows suspected to be broken Output format preference: markdown report, JSON findings, fix PRs, or task list Scope: Full audit or specific focus (auth only, offline only, etc.) Tool Note: ripgrep If rg (ripgrep) is available, use it instead of grep—it's significantly faster and automatically ignores nodemodules/.git. All grep commands in this skill have rg equivalents: Phase 1: Discovery Build a mental model before auditing. Run these commands to locate key files: Key File Mapping Component Typical Location What to Check ----------- ------------------ --------------- Orval config orval.config.ts client type, mutator path, output dir Generated hooks /api/generated/ or /src/api/ completeness vs OpenAPI spec Axios client /api/ or /services/ interceptors, base config Token manager /services/auth/ must use expo-secure-store Zustand stores /stores/ which hold server state (violation?) OpenAPI spec /docs/api/ or root last modified, version Expo config app.config.js or app.json API URLs in extra, env vars Screens /app/ (Expo Router) file-based routing Phase 2: API Layer Audit 2.1 Orval Generation Health Verify: [ ] Generated types match OpenAPI schemas [ ] All spec endpoints have corresponding hooks [ ] Custom mutator injects auth headers [ ] Query defaults sensible (staleTime, gcTime, retry) 2.2 Auth Token Handling Inspect the axios client for these patterns: Expo-specific checks: Red flags: Hardcoded tokens or API keys in source Tokens in AsyncStorage (must use expo-secure-store) API URLs using process.env (use expo-constants instead) No refresh deduplication (parallel refresh calls) Infinite refresh loops (refresh en …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/expo-api-audit