expo-migrate-module
An agent skill by expo, from expo/skills. Tags: code-quality, development, migration, swift, typescript.
What it does
Framework (OSS). Migrate an existing Apple/Swift Expo native module from the Expo Modules API 1.0 definition DSL to the 2.0 macro API (sometimes called v2) while preserving its JavaScript and TypeScript contract. Use when converting or incrementally adopting @ExpoModule, @JS, @Event, @SharedObject, or @Record in an existing module. Do not use for creating a new module, general Expo SDK upgrades, or Android/Kotlin migrations.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill expo-migrate-module
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-experiments/skills/expo-migrate-module ~/.claude/skills/expo-migrate-module
Safety box score
Grade C, moderate risk: 37 of 100 risk points, rated 2026-10-16. 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 is a scoped migration guide for Expo Swift modules, but it still drives native builds/tests, edits module registration and source files, and can contact external services. The main blast-radius risks are running repository build tooling, posting to GitHub/Expo, and pulling an unpinned `npx` package.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It tells the agent to run native builds, unit tests, CocoaPods installs, and example-app launches (`Build or type-check...`, `Run native unit tests and JS/TS tests`, `run the repository's CocoaPods installation workflow`). |
| Network access | 2 (moderate) | It explicitly contacts external services via `gh issue create --repo expo/expo` and `npx --yes submit-expo-feedback@latest`, so the skill is not offline. |
| Filesystem reach | 1 (low) | Migration edits stay inside the working tree but can rewrite Swift sources, `expo-module.config.json`, example-app package files, and remove `definition()` entries. |
| Secrets & credentials | 1 (low) | It can use existing `gh`/npm credentials indirectly for posting or installs, but it never asks the user to reveal secrets or keys. |
| Privilege & persistence | 0 (none) | No sudo, daemons, global installs, or OS/shell configuration changes are required. |
| Instruction hijack surface | 0 (none) | No prompt-injection payload or instruction-hiding trick appears; the only confirmation-sensitive step is posting outward, and the skill says to ask the user first. |
| Irreversible actions | 2 (moderate) | It can create a tracking issue on `expo/expo` and send Expo feedback, which are outward-facing actions even though the skill asks for approval first. |
| Transparency | 2 (moderate) | The feedback command uses `npx --yes submit-expo-feedback@latest`, which fetches and runs remote code that is not readable in the skill files. |
Before installing
- Check `package.json` and the lockfile in both the module root and the example app for Expo `57.0.21` or newer.
- Read `references/compatibility.md` before changing Swift so you know which macros are actually supported by the checked-out core.
- Inspect `expo-module.config.json` before renaming any Swift class; keep the listed class names in sync.
- Decide up front whether you are okay with the skill using `gh` and `npx` to reach external services.
Rated 2026-10-16 by an automated review of 5 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo-experiments/skills/expo-migrate-module/SKILL.md
- Branch
- main
- Collection
- expo-experiments
- Updated
- 2026-09-22
Related skills
- expo-module — Framework (OSS). Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).
- principle-type-system-discipline — Apply when designing types, reviewing a function signature, or writing code in any statically-typed language.
- typescript-best-practices — TypeScript best practices. Use when reading or editing any .ts or .tsx file.
- antfu — Anthony Fu's opinionated tooling and conventions for JavaScript/TypeScript projects.
- migrate-to-shoehorn — Migrate test files from `as` type assertions to @total-typescript/shoehorn.
- write-swift — How to write modern Swift well — modeling with value types, Swift 6 data-race safety and approachable concurrency (@concurrent, main-actor-by-default, actors.