expo-cicd-workflows

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

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

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 so generated workflows are accurate and validates them against the live schema. ## Core Features & Use Cases - Workflow Generation: Create EAS workflow YAML files in .eas/workflows/ using up-to-date job types, triggers, and runner configurations fetched from the official JSON schema. - Schema Validation: Validate one or more workflow files against the live Expo schema using the bundled Node.js validator, with clear error messages showing allowed values. - Cached Documentation Access: Fetch the schema, syntax docs, and pre-packaged job docs with ETag-based caching to avoid repeated network requests. - Use Case: You want a CI/CD pipeline that builds your Expo app on every pull request and deploys on merge. Ask for the workflow, and the Skill generates a valid .eas/workflows/build.yml and verifies it against the official schema. ## Quick Start Ask the assistant to create an EAS workflow that builds your Expo app on every push to main 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?

Place workflow files in .eas/workflows/ with a name, at least one trigger under on, and job definitions under jobs. This Skill fetches the official Expo schema to ensure the job types, triggers, and parameters you use are current and valid.

How do I validate an EAS workflow file against the official schema?

Run the bundled validator with node scripts/validate.js followed by your workflow file paths. It fetches the latest schema from api.expo.dev, parses your YAML with js-yaml, and reports structural errors with allowed values using Ajv.

What triggers and job types does EAS workflows support?

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

Can I use expressions like github context in EAS workflows?

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 runner type or job parameter. The validator prints the failing path and the allowed values so you can correct the YAML.