expo-cicd-workflows

Generates and validates EAS workflow YAML files for Expo CI/CD pipelines.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/Ahmed-Eldalatony/airbnb-clone-bench --skill expo-cicd-workflows-ahmed-eldalatony
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: expo-cicd-workflows
Source: https://github.com/Ahmed-Eldalatony/airbnb-clone-bench/tree/main/.agents/skills/expo-cicd-workflows
Command: npx skills add https://github.com/Ahmed-Eldalatony/airbnb-clone-bench --skill expo-cicd-workflows-ahmed-eldalatony

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires ajv, ajv-formats, js-yaml, and includes scripts (resource) components.

What problem does it solve? Writing EAS workflow YAML files by hand is error-prone because job types, triggers, and parameters evolve over time, and memorized values quickly become outdated. This Skill fetches the official live schema and documentation so generated workflows are always valid and current. ## Core Features & Use Cases - Schema-Driven Generation: Fetches the official EAS workflow JSON schema, syntax docs, and pre-packaged job documentation before writing any workflow file. - Automated Validation: Validates workflow YAML files against the latest schema using AJV, reporting precise errors with allowed values. - Efficient Fetching: Caches remote resources with ETags and Cache-Control headers to avoid redundant network requests. - Use Case: A developer wants a CI/CD pipeline that builds their Expo app on every pull request and deploys on merge to main. The Skill fetches the current schema, generates a valid .eas/workflows/build.yml with correct triggers and job definitions, and validates it before completion. ## Quick Start Ask the assistant to create an EAS workflow that builds your Expo app on every push to the main branch and validate it against the official schema.

Frequently Asked Questions about expo-cicd-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 keys for name, on (triggers), and jobs. This Skill fetches the official schema first, then generates a valid workflow with correct job types and parameters for your CI/CD needs.

How to validate an EAS workflow file against the official schema?

Run the validate.js script with your workflow file path as an argument. It fetches the latest schema from api.expo.dev, parses your YAML with js-yaml, and reports all validation errors with allowed values using AJV.

What job types and triggers does EAS workflows support?

Supported job types, triggers, runner types, and VM images are defined in the official schema at api.expo.dev/v2/workflows/schema. The Skill fetches this live schema rather than relying on memorized values, since options evolve as Expo adds features.

Why does my EAS workflow validation fail with allowed values errors?

Validation fails when a field uses a value not in the schema's enum, such as an outdated runner type or job parameter. The validator output lists the allowed values for each failing field so you can correct them directly.

Can I use expressions like github context in EAS workflow files?

Yes, EAS workflows support ${{ }} expression syntax with contexts including github, inputs, needs, jobs, steps, and workflow. The available contexts and their constraints are defined in the fetched schema and syntax documentation.