openai/codex-expo-run-actions
plugins/expo/skills/codex-expo-run-actions/SKILL.md
Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions. Use when the user wants the Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex.
$ install --global
skillsauthnpx skillsauth add openai/plugins codex-expo-run-actionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 25, 2026, 8:39 AM126.7s3 files scanned
SKILL.md
- name:
- codex-expo-run-actions
- description:
- Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions. Use when the user wants the Codex app Run button, build/run actions, action buttons, or a stable Expo start/run workflow from Codex.
- version:
- 1.0.0
- license:
- MIT
Codex Run Actions for Expo
Use this skill to connect an Expo project to the Codex app action bar.
The goal is one project-local script plus .codex/environments/environment.toml,
so the user can press Run in the Codex app and see the Expo CLI / Metro logs in
an action terminal.
Workflow
-
Confirm the current workspace is an Expo app.
- Look for
package.json. - Look for
app.json,app.config.js,app.config.ts, orexpoinpackage.json. - Do not wire the Codex action at a monorepo root if the Expo app is in a child package.
- Look for
-
Discover the package runner.
- Prefer the package manager declared in
packageManager. - Otherwise infer from lockfiles.
- The generated run script should still have a safe fallback to
npx expo.
- Prefer the package manager declared in
-
Create or update
script/build_and_run.sh.- Use the reference file for the script shape.
- Default no-argument mode starts the Expo dev server:
expo start. - Keep the dev server in the foreground so the Codex action terminal owns logs and Ctrl-C behavior.
- Support optional modes for direct buttons:
--iosstarts Expo and opens iOS simulator.--androidstarts Expo and opens Android.--webstarts Expo for web.--dev-clientstarts in dev-client mode.--tunnelstarts a tunnel.--export-webexports web.
-
Write
.codex/environments/environment.toml.- Always add or update one primary action named
Run. - Wire
Runto./script/build_and_run.sh. - Add direct
Run iOS,Run Android,Run Web, orRun Dev Clientactions only when the user asks for those buttons or the project clearly needs them. - If the environment file already exists, update the existing matching action instead of duplicating it.
- Always add or update one primary action named
-
Use the action script as the default local run path.
- After wiring, run
./script/build_and_run.sh --helpor a short non-server mode if you need to sanity-check syntax. - Do not start a long-lived Metro server during a setup-only task unless the user asked you to run the app.
- After wiring, run
References
references/expo-run-button-bootstrap.md: canonical Exposcript/build_and_run.shand Codex environment action examples.
Guardrails
- Try Expo Go /
expo startfirst; do not default the Codex Run button toexpo run:ios,expo run:android, prebuild, or EAS Build. - Do not wire cloud actions such as
eas build,eas submit, or store deployment into Codex buttons unless the user explicitly asks and accepts the auth / time / cost tradeoff. - Do not create a nested git repo.
- Do not put secrets in
.codex/environments/environment.tomlor in the run script. - Do not background Metro from the run script; the action terminal should show the active server logs.
- Do not hard-code npm if the project uses pnpm, yarn, or bun.
Output Expectations
When setup changes are made, summarize:
- the Expo app root you wired
- the run script path
- the Codex environment file path
- the actions added or updated
- how to launch the same path from shell
Related Skills
openai/provision-droplet
development
VerifiedTrustedCommunity
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
3,575SKILL.mdUpdated Jun 26, 2026
openai/teams
data-ai
VerifiedTrustedCommunity
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
3,575SKILL.mdUpdated May 9, 2026
openai/figma-use-motion
tools
VerifiedTrustedCommunity
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
3,511SKILL.mdUpdated Jun 25, 2026
openai/figma-swiftui
development
VerifiedTrustedCommunity
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.
3,511SKILL.mdUpdated Jun 25, 2026