eas-workflows

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

Updated Sep 13, 2026
One-click install
npx skills add https://github.com/aadilmallick/myfitness-pal-clone --skill eas-workflows-aadilmallick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-workflows
Source: https://github.com/aadilmallick/myfitness-pal-clone/tree/main/.agents/skills/eas-workflows
Command: npx skills add https://github.com/aadilmallick/myfitness-pal-clone --skill eas-workflows-aadilmallick

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing EAS workflow YAML files by hand is error-prone because job types, triggers, runners, and expression contexts evolve over time, and invalid configurations only surface after a failed run. This Skill fetches the authoritative JSON schema and syntax documentation, then generates and validates workflow files against the real EAS CLI. ## Core Features & Use Cases - Schema-driven generation: Fetches the live EAS workflow JSON schema, syntax docs, and pre-packaged job documentation before writing any YAML, so output always matches current capabilities. - CLI validation: Runs eas-cli workflow:validate on each workflow file, which checks build profile references against eas.json and performs server-side validation. - Use Case: You want a CI pipeline that builds an iOS app on every pull request to main and submits it to App Store Connect. The Skill writes the .eas/workflows/*.yml file with correct triggers, job dependencies, and expressions, then validates it until EAS confirms the configuration is valid. ## Quick Start Ask the assistant to create an EAS workflow that builds your Expo app for Android on every push to main and validate the generated YAML file.

Frequently Asked Questions about eas-workflows

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

FAQPage Schema
How do I create an EAS workflow YAML file for my Expo project?

Create a YAML file under .eas/workflows/ with top-level keys name, on, and jobs. Define at least one trigger such as push or pull_request, then add jobs like build with a platform parameter. Validate it with npx eas-cli workflow:validate.

How do I validate an EAS workflow configuration?

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 does EAS Workflows support?

EAS Workflows supports push, pull_request, pull_request_labeled, pull_request_comment, ref_delete, workflow_dispatch, schedule with cron expressions, and App Store Connect events. The exact options and parameters are defined in the live JSON schema at api.expo.dev.

Does EAS Workflows cost money to run?

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

Why does my EAS workflow file fail validation?

Common causes include missing required job parameters, references in needs or after pointing to nonexistent jobs, invalid expression contexts, or workflow files exceeding the 16 KiB size limit. Rerun eas-cli workflow:validate and fix each reported error.