What does this skill do, and when should you use it?
This is the eas-workflows skill from expo/skills, focused on EAS Workflow YAML for Expo projects. It covers workflow structure, triggers, jobs, expressions, dependencies, and validation. Before generating or editing files, it requires current EAS schemas and documentation; EAS Workflows is a paid service subject to plan build or compute-minute limits. It fits Expo teams adopting EAS automation, but may be unnecessary for projects limited to local development.
Reads and edits .eas/workflows/*.yml or *.yaml files; uses the Node.js fetch.js script in the skill directory to retrieve the EAS Workflow JSON Schema, syntax documentation, and pre-packaged job documentation; checks required job fields, needs and after references, expression contexts, and if-condition length; uses validate.js to fetch the latest schema and validate one or more workflow files.
- An Expo developer needs a pull-request preview build workflow and asks the agent to create the EAS Workflow YAML.
- A CI/CD engineer needs to determine supported EAS job types, triggers, or runner settings from the current schema.
- A team maintains existing .eas/workflows files and needs to fix dependency references, expressions, or missing required fields.
- An Expo project wants automated build or deployment workflows and accepts EAS pricing and plan limits.
How do you install this skill?
- Do not trigger EAS workflows before confirming paid usage, build-minute impact, and Apple Developer/Google Play account requirements.
- If the remote schema or documentation is unavailable or changes, generation and validation may fail or become incomplete; manually review cache state, versions, and final YAML.
- Bash(node:*) and Write permissions can execute Node commands and modify files; review target paths and commands before use.
- Shell / CLI
- Network access
- Local filesystem
Node.jsnpm
The README documents installation for the full Expo Skills collection, not a standalone eas-workflows installation. Install the collection with: npx skills@latest add expo/skills --skill '*'. For Codex, use codex plugin add expo@openai-curated; for Claude Code, use claude plugin install expo@claude-plugins-official. The source does not provide a separate command for installing only eas-workflows.
tmp="$(mktemp -d)"
git clone --depth 1 https://github.com/expo/skills.git "$tmp"
mkdir -p ~/.claude/skills
cp -R "$tmp/plugins/expo/skills/eas-workflows" ~/.claude/skills/
rm -rf "$tmp"Generated from the source repository and skill path; it copies only this skill's folder. If the author's install steps above differ, follow those first. To scope it to one project, replace ~/.claude/skills with that project's .claude/skills.
How do you use this skill?
Once installed, send your agent any of these to trigger it:
- Create an EAS workflow that builds previews on pull requests.
After installation, ask for a concrete Expo workflow, for example: “Create an EAS workflow that builds previews on pull requests.” Store workflow files under .eas/workflows/*.yml or *.yaml. When generating or editing, the skill fetches current references and checks the configuration; the source does not document a complete standalone usage flow outside an agent.
What are this skill's strengths and limitations?
- Covers EAS Workflow YAML, CI/CD, job dependencies, and expression checks.
- Requires current schemas and official syntax documentation instead of relying on remembered values.
- Includes validation for one or more workflow files.
- MIT-licensed and maintained as part of Expo's official skills collection.
- EAS Workflows is a paid service, and jobs consume plan build or compute minutes.
- Build and submit jobs also require paid Apple Developer and Google Play accounts.
- Requires Node.js, network access, and local filesystem access.
- The source does not document a dedicated test suite, platform test results, or a standalone installation command for this skill.
How does this skill compare with similar options?
Side by side with related skills; every score comes from the same FSRS standard.
| Skill | FS score | Stars | Last updated | License |
|---|---|---|---|---|
| Expo EAS Workflow Assistant this page | 50 · Use with care | ★ 2.9k | 21d ago | MIT |
| EAS Update Health Insights | 55 · Use with care | ★ 2.9k | 21d ago | MIT |
| CI/CD Pipeline Automation | 48 · Use with care | ★ 107k | 13d ago | MIT |
| EAS Observe Performance Guide | 55 · Use with care | ★ 2.9k | 21d ago | MIT |
| Prism Scanner — AI Agent Skill Security Scanner | 55 · Use with care | ★ 27 | 6mo ago | Apache-2.0 |
Expo documentation, Expo CLI, and EAS CLI remain the sources of truth; this skill helps an agent apply that guidance in real projects rather than replacing those tools or documents.
How did FollowSkills review this skill?
The evidence clearly discloses that EAS is paid, fetches remote Expo/GitHub material, and limits tools to Read, Write, and Bash(node:*). However, Bash write access and network retrieval remain broad, with no explicit user confirmation, sensitive-data policy, pre-execution review, rollback, or detailed data-flow disclosure, so points are deducted.
The scripts have coherent roles and include ETag caching, HTTP errors, YAML parse errors, and schema-validation feedback. Dependencies require manual installation; network and JSON failures lack friendly handling, and the documented checks for needs/after references and expression validity are not clearly implemented by the visible validator. Static evidence is therefore limited.
The name, audience, Expo/EAS CI/CD scenario, trigger conditions, and workflow location are clear. Non-fit boundaries, Chinese-language support, and mainland-China network reachability are not documented; core operation depends on api.expo.dev and raw.githubusercontent.com, so environment-fit evidence is incomplete.
The skill is readable and layered, with version, MIT licensing, dependency-install instructions, reference resources, and generation/validation procedures. It lacks representative workflow examples, FAQs, explicit known limitations, a changelog, and clearly assigned maintenance/update responsibility, so points are deducted.
It can guide creation or editing of EAS workflow YAML and provides an official-schema validation command, giving it direct value for the core task. But it depends on dynamic remote resources and provides no representative outputs or test evidence; results still require human review, so static evidence cannot establish complete effectiveness.
The material names an official schema and documentation sources and provides auditable fetch and validation scripts; the README also identifies Expo documentation, CLI, and EAS CLI as sources of truth. No committed key-path test suite or reproducible execution evidence is provided, so verifiability remains limited.
Open a dimension to read why it scored that way
Evidence confidence：Low — Mostly static review, author material or a limited demo; useful for discovery, not high-risk decisions.
See the full review method →