eas-workflows

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

Updated Sep 11, 2026
One-click install
npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-workflows-cyrus-pinto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eas-workflows
Source: https://github.com/CYRUS-pinto/pi-bot/tree/main/.agents/skills/eas-workflows
Command: npx skills add https://github.com/CYRUS-pinto/pi-bot --skill eas-workflows-cyrus-pinto

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, and mistakes are only caught late without proper validation against the EAS schema and CLI. ## Core Features & Use Cases - Workflow Authoring: Generate and edit .eas/workflows/*.yml files using the live EAS JSON schema as the source of truth for job types, triggers, and parameters. - CLI Validation: Validate workflow files with eas-cli workflow:validate, which checks build profile references against eas.json and performs server-side validation. - Cached Documentation Fetching: Retrieve the schema and syntax docs through a Node.js fetch script with ETag-based HTTP caching. - Use Case: A developer wants a CI/CD pipeline that builds an iOS app on every pull request and submits it to App Store Connect; this Skill generates the workflow YAML and validates it against the project's EAS configuration. ## Quick Start Ask the assistant to create an EAS workflow that builds your Expo app on every push to main and validate it with the EAS CLI.

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 in the .eas/workflows/ directory with top-level name, on, and jobs keys. Fetch the EAS JSON schema from api.expo.dev to get current job types and required parameters, then validate with npx eas-cli workflow:validate.

How do I validate an EAS workflow file?

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 checks build profiles against eas.json plus server-side validation.

What triggers are available for EAS workflows?

EAS workflows support triggers defined under the top-level on key, including push and pull_request style events and workflow_dispatch with inputs. The exact trigger types and configurations are defined in the EAS JSON schema, which should be fetched for current options.

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 can I use in EAS workflow YAML?

EAS workflows support ${{ }} expressions with contexts including github, inputs, needs, jobs, steps, and workflow. These provide access to repository event data, dispatch inputs, dependent job outputs, and workflow metadata.