expo-brownfield
An agent skill by expo, from expo/skills. Tags: android, architecture, development, integration, ios, mobile.
What it does
Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use eas-app-stores.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-brownfield
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-brownfield ~/.claude/skills/expo-brownfield
Safety box score
Grade C, moderate risk: 39 of 100 risk points, rated 2026-10-19. 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 a build-and-integration guide for adding Expo/React Native to an existing native iOS/Android app. Its main risks are that it runs registry-fetched tooling, edits native build files, and can publish build artifacts to local or remote Maven targets, including using private repository credentials.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It relies on shell commands and package runners such as `npx create-expo-app@latest`, `npx expo install`, `npx expo-brownfield build:android`, `npx expo-brownfield build:ios`, `yarn install`, and `pod install`. |
| Network access | 2 (moderate) | It downloads and publishes over the network, including `npx`-fetched tooling and optional remote Maven publishing via `remotePublic` / `remotePrivate`, plus `npx --yes submit-expo-feedback@latest`. |
| Filesystem reach | 2 (moderate) | It writes into the host project and also outside it, notably the local Maven cache `~/.m2` and generated native/artifact directories like `ios/`, `android/`, and `./artifacts`. |
| Secrets & credentials | 2 (moderate) | The Android publishing config can read credentials from environment variables such as `ARTIFACTORY_URL`, `ARTIFACTORY_USER`, and `ARTIFACTORY_TOKEN`, so the workflow can touch private repo secrets. |
| Privilege & persistence | 0 (none) | There is no sudo, service registration, global install, or OS-level privilege escalation in the skill text. |
| Instruction hijack surface | 0 (none) | The files contain no hidden prompt-injection, no instruction to bypass safeguards, and no fetched instructions to follow; the only `--yes` flag is for an explicit feedback command. |
| Irreversible actions | 2 (moderate) | It can publish build outputs to package repositories and explicitly includes a command to submit feedback externally, but it does not directly pay, delete, or deploy production services. |
| Transparency | 0 (none) | All shipped files are plain-text markdown/YAML; there are no binaries, opaque installers, base64 blobs, or decoded-at-runtime code. |
Before installing
- Decide whether you want the isolated or integrated approach before running any commands.
- Read `references/brownfield-isolated.md` and `references/brownfield-integrated.md` for the exact native files that will be edited.
- Check whether any workflow will write to `~/.m2` or remote Maven repos, and run it first in a throwaway branch or test app.
- Confirm whether you will use private publishing credentials (`ARTIFACTORY_*`) before enabling the remote-private path.
Rated 2026-10-19 by an automated review of 8 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/expo-brownfield/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- eas-app-stores — EAS service (paid). Build and submit iOS and Android apps with EAS to TestFlight, the App Store, or Google Play.
- eas-simulator — EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud.
- expo-dom — Framework (OSS). Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
- expo-web-to-native — Framework (OSS). Migrate an existing web React app to a native iOS/Android app with Expo.
- expo-app-clip — Framework (OSS). Add an iOS App Clip target to an Expo app.
- expo-dev-client — Framework (OSS). Build and distribute Expo development clients locally or via TestFlight for internal testing.