Generate and Validate EAS CI/CD Workflows

Helps developers write, edit, and validate EAS (Expo Application Services) workflow YAML files for Expo projects, living at .eas/workflows/*.yml. Before generating or validating any workflow, it fetches three official reference resources via a bundled Node.js fetch script that caches responses using ETags: the JSON Schema at https://api.expo.dev/v2/workflows/schema (the source of truth for validation, job types and their required/optional parameters, trigger types, and runner/VM enums), the syntax documentation covering workflow YAML syntax and expression contexts, and the pre-packaged-jobs documentation for supported job types and their parameters/outputs - explicitly not relying on memorized values, since these resources change as Expo adds features.

node <skill-dir>/scripts/fetch.js <url>

It knows the top-level workflow structure (name, on triggers, jobs, defaults, concurrency) and the ${{ }} expression syntax with its available contexts (github.*, inputs.*, needs.*, jobs.*, steps.*, workflow.*). When generating or editing a workflow it follows a fixed procedure: fetch the schema for current job types/parameters/allowed values, validate required fields per job type, verify that job references in needs and after actually exist in the workflow, check that expressions reference valid contexts and outputs, and ensure if conditions respect the schema's length constraints. After generating or editing a file it validates it against the live schema with a bundled validator script, installing dependencies if missing, and fixes any reported errors before considering the workflow complete.

node <skill-dir>/scripts/validate.js <workflow.yml> [workflow2.yml ...]

When a user asks about available options - job types, triggers, runner types - it fetches the schema and derives the answer from it rather than answering from potentially outdated knowledge.

Use it when the user asks about CI/CD or workflows in an Expo or EAS context, mentions .eas/workflows/, or wants help with EAS build pipelines or deployment automation. Use it only within its upstream product or API scope, and verify commands, API behavior, pricing, quotas, credentials, and deployment effects against current official documentation before making changes - generated examples are not a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.

Input is a request to write, edit, validate, or explain an EAS workflow YAML file, or a question about available job types, triggers, or runner options. Output is a generated or edited .eas/workflows/*.yml file, a validation result/error list from running it against the current schema, or a schema-derived answer to a workflow-options question.

Fetches directly from Expo's official EAS Workflows JSON Schema API and documentation (api.expo.dev, the expo/expo docs repository), and ships its own Node.js fetch.js and validate.js scripts, installing npm dependencies on demand, to keep validation current with the live schema rather than a bundled snapshot.

Developers building or maintaining CI/CD pipelines for Expo projects using EAS Workflows who need workflow YAML checked against the current, evolving schema rather than memorized syntax.