codex-expo-run-actions Skill
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. Published by openai in plugins.
Decision snapshot
Is this a fit?
Developers using plugins, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
19 days ago
No specific cautions were detected. Review the source and requested permissions before installing.
What is codex-expo-run-actions Skill?
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. Published by openai in plugins. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using plugins
Declared skill metadata
- Declared license: MIT
- Source file: plugins/expo/skills/codex-expo-run-actions/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use codex-expo-run-actions Skill
- Use it for developers using plugins.
Built with
Editorial notes
Source
- Creator: openai
- Repository: openai/plugins
- Skill file: plugins/expo/skills/codex-expo-run-actions/SKILL.md
What it does
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.
Skill instructions
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 1. Confirm the current workspace is an Expo app. - Look for package.json. - Look for app.json, app.config.js, app.config.ts, or expo in package.json. - Do not wire the Codex action at a monorepo root if the Expo app is in a child package. 2. 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. 3. Create or update script/buildandrun.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 m
Verified compatibility and discovery
Frequently asked questions
What is codex-expo-run-actions?
codex-expo-run-actions is a open-source AI agent skill with Copy skill directory. Wire Expo projects into the Codex app with project-local run scripts and .codex/environments/environment.toml actions.
Who is codex-expo-run-actions best for?
codex-expo-run-actions is best for reusing agent instructions, scripts, and references.
How do I install codex-expo-run-actions?
Install or run codex-expo-run-actions using Copy skill directory. Check codex-expo-run-actions for the latest setup command.
Is codex-expo-run-actions actively maintained?
codex-expo-run-actions may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
