How do I install the Expo Cicd Workflows skill?

Run npx skillmds@latest add tomevault-io/expo-cicd-workflows-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Expo Cicd Workflows safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Expo Cicd Workflows?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Expo Cicd Workflows free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Expo Cicd Workflows?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Expo Cicd Workflows by tomevault-io

Name: Expo Cicd Workflows
Author: tomevault-io

Expo Cicd Workflows

Helps understand and write EAS workflow YAML files for Expo projects. Use this skill 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 when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

EAS Workflows Skill

Help developers write and edit EAS CI/CD workflow YAML files.

Reference Documentation

Fetch these resources before generating or validating workflow files. Use the fetch script (implemented using Node.js) in this skill's scripts/ directory; it caches responses using ETags for efficiency:

# Fetch resources
node {baseDir}/scripts/fetch.js <url>

JSON Schema — https://api.expo.dev/v2/workflows/schema
- It is NECESSARY to fetch this schema
- Source of truth for validation
- All job types and their required/optional parameters
- Trigger types and configurations
- Runner types, VM images, and all enums
Syntax Documentation — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx
- Overview of workflow YAML syntax
- Examples and English explanations
- Expression syntax and contexts
Pre-packaged Jobs — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx
- Documentation for supported pre-packaged job types
- Job-specific parameters and outputs

Do not rely on memorized values; these resources evolve as new features are added.

Workflow File Location

Workflows live in .eas/workflows/*.yml (or .yaml).

Top-Level Structure

A workflow file has these top-level keys:

name — Display name for the workflow
on — Triggers that start the workflow (at least one required)
jobs — Job definitions (required)
defaults — Shared defaults for all jobs
concurrency — Control parallel workflow runs

Consult the schema for the full specification of each section.

Expressions

Use ${{ }} syntax for dynamic values. The schema defines available contexts:

github.* — GitHub repository and event information
inputs.* — Values from workflow_dispatch inputs
needs.* — Outputs and status from dependent jobs
jobs.* — Job outputs (alternative syntax)
steps.* — Step outputs within custom jobs
workflow.* — Workflow metadata

Generating Workflows

When generating or editing workflows:

Fetch the schema to get current job types, parameters, and allowed values
Validate that required fields are present for each job type
Verify job references in needs and after exist in the workflow
Check that expressions reference valid contexts and outputs
Ensure if conditions respect the schema's length constraints

Validation

After generating or editing a workflow file, validate it against the schema:

# Install dependencies if missing
[ -d "{baseDir}/scripts/node_modules" ] || npm install --prefix {baseDir}/scripts

node {baseDir}/scripts/validate.js <workflow.yml> [workflow2.yml ...]

The validator fetches the latest schema and checks the YAML structure. Fix any reported errors before considering the workflow complete.

Answering Questions

When users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.

Source: lexand-dev/subtrack-monorepo — distributed by TomeVault.

---name: expo-cicd-workflows-2description: Helps understand and write EAS workflow YAML files for Expo projects. Use this skill 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 when this capability is needed.---# EAS Workflows SkillHelp developers write and edit EAS CI/CD workflow YAML files.## Reference DocumentationFetch these resources before generating or validating workflow files. Use the fetch script (implemented using Node.js) in this skill's `scripts/` directory; it caches responses using ETags for efficiency:```bash# Fetch resourcesnode {baseDir}/scripts/fetch.js <url>```1. **JSON Schema** — https://api.expo.dev/v2/workflows/schema - It is NECESSARY to fetch this schema - Source of truth for validation - All job types and their required/optional parameters - Trigger types and configurations - Runner types, VM images, and all enums2. **Syntax Documentation** — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx - Overview of workflow YAML syntax - Examples and English explanations - Expression syntax and contexts3. **Pre-packaged Jobs** — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx - Documentation for supported pre-packaged job types - Job-specific parameters and outputsDo not rely on memorized values; these resources evolve as new features are added.## Workflow File LocationWorkflows live in `.eas/workflows/*.yml` (or `.yaml`).## Top-Level StructureA workflow file has these top-level keys:- `name` — Display name for the workflow- `on` — Triggers that start the workflow (at least one required)- `jobs` — Job definitions (required)- `defaults` — Shared defaults for all jobs- `concurrency` — Control parallel workflow runsConsult the schema for the full specification of each section.## ExpressionsUse `${{ }}` syntax for dynamic values. The schema defines available contexts:- `github.*` — GitHub repository and event information- `inputs.*` — Values from `workflow_dispatch` inputs- `needs.*` — Outputs and status from dependent jobs- `jobs.*` — Job outputs (alternative syntax)- `steps.*` — Step outputs within custom jobs- `workflow.*` — Workflow metadata## Generating WorkflowsWhen generating or editing workflows:1. Fetch the schema to get current job types, parameters, and allowed values2. Validate that required fields are present for each job type3. Verify job references in `needs` and `after` exist in the workflow4. Check that expressions reference valid contexts and outputs5. Ensure `if` conditions respect the schema's length constraints## ValidationAfter generating or editing a workflow file, validate it against the schema:```sh# Install dependencies if missing[ -d "{baseDir}/scripts/node_modules" ] || npm install --prefix {baseDir}/scriptsnode {baseDir}/scripts/validate.js <workflow.yml> [workflow2.yml ...]```The validator fetches the latest schema and checks the YAML structure. Fix any reported errors before considering the workflow complete.## Answering QuestionsWhen users ask about available options (job types, triggers, runner types, etc.), fetch the schema and derive the answer from it rather than relying on potentially outdated information.---> Source: [lexand-dev/subtrack-monorepo](https://github.com/lexand-dev/subtrack-monorepo) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions