| name | expo-cicd-workflows |
| description | 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. |
| type | skill |
| created | 2026-02-27T00:00:00.000Z |
| domain | software-development |
| category | mobile |
| risk | unknown |
| source | community |
| tags | ["skill","software-development","mobile","expo","cicd","workflows"] |
EAS Workflows Skill
Help developers write and edit EAS CI/CD workflow YAML files.
When to Use
- You need to create, edit, or validate
.eas/workflows/*.yml files for an Expo project.
- The task involves EAS build pipelines, deployment automation, workflow triggers, or Expo CI/CD configuration.
- You need schema-backed workflow guidance rather than relying on stale memorized syntax.
Reference Documentation
Fetch these resources before generating or validating workflow files. Use the fetch script (implemented using Node.js) in this skill's scripts/ directory; it caches responses using ETags for efficiency:
node {baseDir}/scripts/fetch.js <url>
-
JSON Schema — https://api.expo.dev/v2/workflows/schema
- It is NECESSARY to fetch this schema
- Source of truth for validation
- All job types and their required/optional parameters
- Trigger types and configurations
- Runner types, VM images, and all enums
-
Syntax Documentation — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx
- Overview of workflow YAML syntax
- Examples and English explanations
- Expression syntax and contexts
-
Pre-packaged Jobs — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx
- Documentation for supported pre-packaged job types
- Job-specific parameters and outputs
Do not rely on memorized values; these resources evolve as new features are added.
Workflow File Location
Workflows live in .eas/workflows/*.yml (or .yaml).
Top-Level Structure
A workflow file has these top-level keys:
name — Display name for the workflowon — Triggers that start the workflow (at least one required)jobs — Job definitions (required)
