Writing Expo Modules
Create native Expo modules and views — Swift, Kotlin, TypeScript via the Expo Modules API
- What
- Create native Expo modules and views — Swift, Kotlin, TypeScript via the Expo Modules API
- Cost
- Free
- Needs
- Node.js with an Expo/React Native project; Xcode (iOS) and/or Android Studio (Android) toolchains for native builds
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a complete reference for building native modules and views with the Expo Modules API: the module definition DSL (Name, Function, AsyncFunction, Property, Constant, Events), native views with lifecycle and ref-based functions, shared objects, config plugins that modify native project files, lifecycle hooks, autolinking, and the expo-module.config.json fields. Prefers create-expo-module scaffolding over hand-writing module files. Distinct from the other published expo skills (expo-dev-client, expo-deployment) — this one is about writing native code bridges, not app workflows. By @expo, listed here with credit to its creator. Honest caveats: native modules require Xcode (iOS) and Android Studio (Android) toolchains alongside Node; it doesn't migrate existing Swift DSL modules to the 2.0 macros — that's the expo-migrate-module skill from expo-experiments. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: Node.js with an Expo/React Native project; Xcode (iOS) and/or Android Studio (Android) toolchains for native builds Install "Writing Expo Modules" for me. Create native Expo modules and views — Swift, Kotlin, TypeScript via the Expo Modules API Repository: https://github.com/expo/skills/blob/main/plugins/expo/skills/expo-module/SKILL.md 1. Fetch the SKILL.md file for the expo-expo-module skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "expo-expo-module". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.