expo-cicd-workflows

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

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Divith123/Flamingo --skill expo-cicd-workflows-divith123
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: expo-cicd-workflows
Source: https://github.com/Divith123/Flamingo/tree/main/.agents/skills/expo-cicd-workflows
Command: npx skills add https://github.com/Divith123/Flamingo --skill expo-cicd-workflows-divith123

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 requires knowing the current schema, job types, triggers, and expression contexts, which change as Expo adds features. This Skill fetches the official schema and documentation, then generates and validates workflow files against the live specification. ## Core Features & Use Cases - Schema-Driven Generation: Fetches the official EAS workflow JSON schema and syntax documentation before writing workflow files, avoiding outdated assumptions. - Automated Validation: Validates .eas/workflows/*.yml files against the live schema using Ajv, reporting precise errors with allowed values. - Efficient Fetching: Caches schema and documentation responses using ETags and Cache-Control headers to minimize redundant network requests. - Use Case: A developer wants a CI/CD pipeline that builds an iOS app on every push to main. The Skill fetches the current schema, writes the workflow YAML with correct job types and triggers, and validates it before committing. ## Quick Start Ask the assistant to create an EAS workflow file that builds your Expo app on every push 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 file for my Expo project?▼

Create a YAML file in the .eas/workflows/ directory with top-level keys for name, on (triggers), and jobs. Fetch the official schema from api.expo.dev to confirm current job types, required parameters, and trigger configurations before writing the file.

How to validate EAS workflow YAML files against the official schema?▼

Run the validate.js script with your workflow file paths as arguments. It fetches the latest schema from api.expo.dev, parses the YAML with js-yaml, and checks it with Ajv, printing specific errors with allowed values for each failure.

What triggers are available for EAS workflows?▼

Available triggers are defined in the official EAS workflow schema, which evolves as Expo adds features. Fetch the schema from https://api.expo.dev/v2/workflows/schema to see current trigger types and their configurations rather than relying on memorized values.

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 schema defines which contexts and outputs are valid for each field.

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 job type or runner image. The validator output lists the allowed values; fetch the latest schema since valid options change as Expo releases new features.