eas-workflows

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

Updated Sep 8, 2026
One-click install
npx skills add https://github.com/bmiit145/leadBee --skill eas-workflows-bmiit145
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: eas-workflows
Source: https://github.com/bmiit145/leadBee/tree/main/mobile/.agents/skills/eas-workflows
Command: npx skills add https://github.com/bmiit145/leadBee --skill eas-workflows-bmiit145

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Writing EAS workflow YAML files requires knowing the current schema, job types, triggers, and expression contexts, which change as Expo ships new features. This Skill fetches the live JSON schema and official docs so generated workflows are accurate, then validates them with the EAS CLI. ## Core Features & Use Cases - Schema-Grounded Generation: Fetches the official EAS workflow JSON schema and syntax documentation before writing or editing files in .eas/workflows/. - CLI Validation: Runs eas-cli workflow:validate on each changed workflow file, checking build profile references against eas.json and EAS server-side rules. - 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 generates the workflow YAML with correct triggers, job dependencies, and expressions, then validates it against the linked Expo project. ## 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 under .eas/workflows/ with top-level keys for name, on (triggers), and jobs. Fetch the official schema at api.expo.dev/v2/workflows/schema for current job types and 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 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 Expo adds features.

What expression contexts are available in EAS workflow files?▼

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

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.