integration-expo — Claude Code skill: what it does, how to install
The integration-expo skill adds PostHog analytics to Expo apps and guides the setup in stages. Use it for events, user identification, screens, and errors.
MIT 112 installs ★ 80 updated 2026-10-24
npx skills add PostHog/skills --skill integration-expo -a claude-codeWhat integration-expo does
The skill guides a PostHog setup for Expo applications. It covers the SDK integration, identifying users during login and signup, and adding error tracking around important flows and API boundaries. When a project has both client and server code, the setup passes X-POSTHOG-DISTINCT-ID and X-POSTHOG-SESSION-ID to keep the two sides correlated.
The workflow uses four files in sequence: basic-integration-1.0-begin.md, basic-integration-1.1-edit.md, basic-integration-1.2-revise.md, and basic-integration-1.3-conclude.md. Reference material includes an Expo example plus React Native and user-identification notes. PostHog keys belong in environment variables. With expo-router, the provider goes in app/_layout.tsx, while screens are tracked with posthog.screen(pathname, params) inside useEffect. The surveys feature requires react-native-svg.
What it helps with
- add PostHog analytics to an Expo application
- identify users during login and signup
- link client and server events with request headers
- track errors around critical user flows
- record screens in an
expo-routerapp
Example prompts for the agent
- Add PostHog to this Expo app by following
basic-integration-1.0-begin.mdthroughbasic-integration-1.3-conclude.md. - Implement user identification for login and signup using the guidance in
references/identify-users.md. - Configure PostHog for
expo-router: put the provider inapp/_layout.tsxand track screens withposthog.screen(pathname, params).
How to install integration-expo
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-expo -a claude-code2Manually: put the files in place
~/.claude/skills/integration-expo/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/integration-expo/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-expo -a codex2Manually: put the files in place
.agents/skills/integration-expo/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-expo -a cursor2Manually: put the files in place
.cursor/skills/integration-expo/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install PostHog/skills skills/posthog/all/skills/integration-expo2Manually: put the files in place
.github/skills/integration-expo/SKILL.md1Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-expo -a gemini-cli2Platform CLI
gemini skills install https://github.com/PostHog/skills --path skills/posthog/all/skills/integration-expoManually: put the files in place
.devin/skills/integration-expo/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add PostHog/skills --skill integration-expo -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about integration-expo
How do I install integration-expo in Claude Code?
Run npx skills add PostHog/skills --skill integration-expo -a claude-code, then check ~/.claude/skills/integration-expo/SKILL.md.
What does integration-expo do?
It guides PostHog analytics setup in Expo apps, including user identification, screen tracking, and error tracking.
What dependency is needed for the surveys feature?
Install react-native-svg alongside posthog-react-native; the surveys feature uses that peer dependency.
Source text
SKILL.md · MIT
--- name: integration-expo description: PostHog integration for Expo applications metadata: author: PostHog version: 1.9.4 --- # PostHog integration for Expo This skill helps you add PostHog analytics to Expo applications. ## Workflow Follow these steps in order to complete the integration: 1. `basic-integration-1.0-begin.md` - PostHog Setup - Begin ← **Start here** 2. `basic-integration-1.1-edit.md` - PostHog Setup - Edit 3. `basic-integration-1.2-revise.md` - PostHog Setup - Revise 4. `basic-integration-1.3-conclude.md` - PostHog Setup - Conclusion ## Reference files - `references/EXAMPLE.md` - Expo example project code - `references/react-native.md` - React native - docs - `references/identify-users.md` - Identify users - docs - `references/basic-integration-1.0-begin.md` - PostHog setup - begin - `references/basic-integration-1.1-edit.md` - PostHog setup - edit - `references/basic-integration-1.2-revise.md` - PostHog setup - revise - `references/basic-integration-1.3-conclude.md` - PostHog setup - conclusion The example project shows the target implementation pattern. Consult the documentation for API details. ## Key principles - **Environment variables**: Always use environment variables for PostHog keys. Never hardcode them. - **Minimal changes**: Add PostHog code alongside existing integrations. Don't replace or restructure existing code. - **Match the example**: Your implementation should follow the example project's patterns as closely as possible. ## Framework guidelines - posthog-react-native is the React Native SDK package name (same as bare RN) - Use expo-constants with app.config.js extras for POSTHOG_PROJECT_TOKEN and POSTHOG_HOST (NOT react-native-config) - Access config via `Constants.expoConfig?.extra?.posthogProjectToken` in your posthog.ts config file - For expo-router, wrap PostHogProvider in app/_layout.tsx and manually track screens with `posthog.screen(pathname, params)` in a useEffect - posthog-react-native is the React Native SDK package name - Use react-native-config to load POSTHOG_PROJECT_TOKEN and POSTHOG_HOST from .env (variables are embedded at build time, not runtime) - react-native-svg is a required peer dependency of posthog-react-native (used by the surveys feature) and must be installed alongside it - Place PostHogProvider INSIDE NavigationContainer for React Navigation v7 compatibility ## Identifying users Identify users during login and signup events. Refer to the example code and documentation for the correct identify pattern for this framework. If both frontend and backend code exist, pass the client-side session and distinct ID using `X-POSTHOG-DISTINCT-ID` and `X-POSTHOG-SESSION-ID` headers to maintain correlation. ## Error tracking Add PostHog error tracking to relevant files, particularly around critical user flows and API boundaries.
© PostHog · MIT · PostHog/skills