eas-workflows

Write and validate EAS workflow YAML files for Expo CI/CD pipelines.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/gmackie/agent-skills --skill eas-workflows-gmackie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eas-workflows
Source: https://github.com/gmackie/agent-skills/tree/main/skills/eas-workflows
Command: npx skills add https://github.com/gmackie/agent-skills --skill eas-workflows-gmackie

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing EAS workflow YAML files for Expo projects requires up-to-date knowledge of job types, triggers, runners, and expression syntax that changes as the platform evolves, and mistakes are only caught late without proper validation. ## Core Features & Use Cases - Schema-Grounded Authoring: Fetches the live EAS workflow JSON schema and official syntax documentation so generated workflows match current job types, parameters, and enums. - CLI Validation: Validates each workflow file with eas-cli workflow:validate, which checks build profile references against the project's eas.json and performs server-side checks. - Use Case: A developer wants a CI/CD pipeline that builds an iOS app on every pull request and submits to TestFlight on merge. The skill fetches the schema, writes .eas/workflows/deploy.yml with correct triggers and job definitions, then validates it with EAS CLI until it passes. ## Quick Start Use the eas-workflows skill to create an EAS workflow that builds my Expo app on every push to main and validate it.

Frequently Asked Questions about eas-workflows

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write an EAS workflow YAML file for an Expo project?▼

Create a YAML file under .eas/workflows/ with top-level keys name, on, and jobs. Fetch the EAS workflow JSON schema to get current job types, triggers, and parameters, then validate the file with npx eas-cli workflow:validate.

How to validate EAS workflow configuration files?▼

Run npx -y eas-cli@latest workflow:validate .eas/workflows/<file>.yml --non-interactive from the Expo project root. It requires a logged-in EAS CLI session and a linked project, and checks build profiles against eas.json plus server-side rules.

What triggers and job types does EAS Workflows support?▼

Supported triggers, job types, runner types, VM images, and enums are defined in the official JSON schema at api.expo.dev/v2/workflows/schema. Fetch it rather than relying on memorized values, since options evolve as features are added.

Does EAS Workflows cost money to run?▼

Yes, EAS Workflows run on Expo Application Services, a paid product with free-tier limits. Each job consumes plan build/compute minutes, and build or submit jobs also require paid Apple Developer and Google Play accounts.

What expression contexts are available in EAS workflow files?▼

EAS workflows support ${{ }} expressions with contexts including github, inputs, needs, jobs, steps, and workflow. The schema defines the exact available contexts and their fields for dynamic values.