eas-workflows
An agent skill by expo, from expo/skills. Tags: automation, ci-cd, deployment, workflow, yaml.
What it does
EAS service (paid). Helps understand and write EAS workflow YAML files for Expo projects. Use this skill when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-workflows
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/eas-workflows ~/.claude/skills/eas-workflows
Safety box score
Grade C, moderate risk: 33 of 100 risk points, rated 2026-10-17. 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 helps edit and validate Expo EAS workflow YAML, and it reaches out to Expo/GitHub documentation plus EAS server-side validation. The main risks are running downloaded npm code via `npx`, making outbound network requests, and using an existing logged-in EAS CLI session.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 3 (high) | It explicitly runs downloaded npm packages with `npx -y eas-cli@latest workflow:validate ...` and `npx --yes submit-expo-feedback@latest ...`, which executes code fetched at runtime. |
| Network access | 2 (moderate) | `scripts/fetch.js` performs outbound HTTP requests with `fetch(url, ...)`, and `SKILL.md` directs the agent to contact Expo/GitHub URLs and optionally submit feedback to Expo. |
| Filesystem reach | 1 (low) | The shipped script only writes a local cache under `scripts/.cache` (`writeFile(cacheFile, ...)`), and the workflow files it edits are within the project tree. |
| Secrets & credentials | 1 (low) | `workflow:validate` "requires a logged-in EAS CLI session and a linked Expo project," so it depends on existing Expo auth state, though it does not ask the user to type secrets. |
| Privilege & persistence | 0 (none) | There is no sudo, service installation, shell-profile editing, or other privilege-elevation behavior in the provided files. |
| Instruction hijack surface | 0 (none) | The files do not tell the agent to ignore instructions, hide actions, or follow remote prompt content; they only describe workflow validation and documentation fetching. |
| Irreversible actions | 1 (low) | It can send feedback externally with `npx --yes submit-expo-feedback@latest ...`, but that is optional and not an irreversible deploy or payment action. |
| Transparency | 1 (low) | Behavior depends on remote content and unpinned `@latest` npm packages (`eas-cli@latest`, `submit-expo-feedback@latest`), so some executed code is not fully reviewable from the repo. |
Before installing
- Read `scripts/fetch.js`; it writes cache files under `scripts/.cache` and can fetch any URL you pass it.
- Be comfortable with `npx -y eas-cli@latest` and `npx --yes submit-expo-feedback@latest` downloading and running latest npm code.
- Run `workflow:validate` first in a scratch Expo project with your EAS login active, not in a sensitive account.
- Check that you are okay with the skill contacting Expo/GitHub to fetch docs and validate workflows server-side.
Rated 2026-10-17 by an automated review of 4 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-workflows/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- turborepo — Turborepo monorepo build system guidance.
- agents-deploy — Use when deploying your agent to AWS, or when a deploy has failed.
- automate-me — Use for "automate me", "create/update/refresh my -mode skill", "turn/capture my preferences or working style into a skill".
- aws-deployment — Configures CI/CD pipelines using AWS CodePipeline, CodeBuild, CodeDeploy, CodeConnections, and CodeArtifact.
- cancel-ralph — Cancel an active Ralph Loop. Use when the user wants to stop, cancel, or abort a running ralph loop.
- churn-prevention — When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies.