Skills Explorer Add Skills

expo-module

An agent skill by expo, from expo/skills. Tags: api, architecture, development, native, swift, typescript.

What it does

Framework (OSS). Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript). Covers module definition DSL, native views, shared objects, config plugins, lifecycle hooks, autolinking, and type system. Use when building or modifying native modules for Expo. Not for migrating an existing Swift module from the definition DSL to the Expo Modules API 2.0 macros; use expo-migrate-module (from the expo-experiments plugin) for that.

Install

With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:

npx skills add expo/skills --skill expo-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/skills/expo-module ~/.claude/skills/expo-module

Safety box score

Grade B, low risk: 16 of 100 risk points, rated 2026-10-20. 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 documentation-only guide for scaffolding and writing Expo native modules, native views, lifecycle hooks, and config plugins. The main risks come from running Expo CLIs via `npx`, and from the fact that its workflows intentionally edit native project files and can embed app configuration values into iOS/Android manifests.

Category levels, from 0 (none) to 3 (high)
CategoryLevelWhy
Code & shell execution1 (low)The skill recommends running registry-fetched commands such as `npx create-expo-module@latest ...`, `npx expo prebuild --clean`, and `npx --yes submit-expo-feedback@latest ...`, which executes downloaded CLI packages.
Network access1 (low)Those same `npx` workflows fetch packages and can send feedback to Expo; the skill also points to `submit-expo-feedback@latest`, which transmits user-supplied text off-machine.
Filesystem reach1 (low)Its purpose is to scaffold and modify project files like `expo-module.config.json`, native source directories, `Info.plist`, and `AndroidManifest.xml`, but the edits are intended to stay within the app/module project.
Secrets & credentials1 (low)The config-plugin example stores an `apiKey` in app config and reads `MY_API_KEY` from native metadata/Info.plist, which can expose secret-like values in build artifacts rather than secure storage.
Privilege & persistence0 (none)There is no request for sudo, global installs, services, shell startup changes, or OS-level privilege changes.
Instruction hijack surface0 (none)The files do not instruct the agent to ignore safeguards, hide actions, or follow remote instructions; the only notable prompt-like text is a normal feedback-command example.
Irreversible actions0 (none)The skill does not authorize irreversible external actions like publishing, deploying, paying, posting, or deleting; it only describes local module scaffolding and configuration.
Transparency0 (none)All shipped files are readable markdown/YAML; there are no binaries, base64 blobs, or decoded-at-runtime installers.

Before installing

Rated 2026-10-20 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-module/SKILL.md
Branch
main
Collection
expo
Updated
2026-09-22