New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Official agent skill

Eas Workflows

by expo in expo/skills

Helps understand and write EAS workflow YAML files for Expo projects.

OfficialMITAuto-check passedDevOps & Cloud

Install Eas Workflows

skills CLI
$ npx skills add expo/skills --skill eas-workflows -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install expo/skills eas-workflows --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/expo/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/expo/skills/eas-workflows .claude/skills/eas-workflows && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
eas-workflows
GitHub stars
2.7k
Token cost
~1.2k tokens
SKILL.md length
544 words
Files
4 (incl. scripts)
Skills in repo
26
Repo updated
First seen
Licence
MIT

At a glance

Helps understand and write EAS workflow YAML files for Expo projects.

  • Works in 3 steps: JSON Schema —… → Syntax Documentation —… → Pre-packaged Jobs —…
  • The user asks about CI/CD
  • SKILL.md covers Reference Documentation, Workflow File Location, Top-Level Structure and Expressions, plus 4 more sections
  • Runs JavaScript scripts from its folder; calls npx and node

What it does

Eas Workflows is an agent skill from expo/skills, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts (for example `agents/openai.yaml`, `scripts/fetch.js` and `scripts/package.json`).

It sits in DevOps & Cloud, covering CI/CD and Cross-platform mobile apps. It works with Expo. The repository describes itself as: A collection of AI agent skills for working with Expo projects and Expo Application Services. The licence is MIT.

When your agent uses it

  • The user asks about CI/CD
  • Workflows in an Expo
  • Mentions .eas/workflows/
  • Wants help with EAS build pipelines

Example prompts

  • “Use the eas-workflows skill to help understand and write EAS workflow YAML files for Expo projects”
  • “/eas-workflows”

Requirements

  • Node.js
  • Pre-approved tools (allowed-tools): Read, Write, Bash(node:*), Bash(npx *eas-cli@*)

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. JSON Schema — https://api.expo.dev/v2/workflows/schema
  2. Syntax Documentation — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx
  3. Pre-packaged Jobs — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/pre-packaged-jobs.mdx

What it can do on your machine

Read from SKILL.md and the folder at commit d4f4840. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Bash(node:*)
    • Bash(npx *eas-cli@*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 2 files in scripts/ (JavaScript), which the agent can run.

    Shell commands in SKILL.md call:

    • npx
    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • raw.githubusercontent.com
    • expo.dev
    • api.expo.dev

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Eas Workflows loads about 1.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 544 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from expo/skills at commit d4f4840, republished under its MIT licence (© expo). 544 words, ~1,195 tokens.

Download SKILL.mdSave it as .claude/skills/eas-workflows/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.
name
eas-workflows
description
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.
allowed-tools
Read, Write, Bash(node:*), Bash(npx *eas-cli@*)
version
1.0.0
license
MIT License

EAS Workflows Skill

EAS service - costs apply. EAS Workflows run on Expo Application Services, a paid product with free-tier limits. Each workflow job consumes your plan's build/compute minutes, and jobs that build or submit also need paid Apple Developer and Google Play accounts. Review https://expo.dev/pricing before triggering runs.

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

Reference Documentation

Fetch these resources before generating or editing workflow files, or when answering syntax questions. First resolve this skill's directory, then use the fetch script in its scripts/ directory. It is implemented using Node.js and caches responses using ETags for efficiency:

bash
# Fetch resources
node <skill-dir>/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 the workflow YAML structure; EAS CLI remains the authoritative final validator
    • All job types and their required/optional parameters
    • Trigger types and configurations
    • Runner types, VM images, and all enums

  2. 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

  3. 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). Each file must be 16 KiB or smaller.

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
Show full SKILL.md (245 more words)Show less

Generating Workflows

When generating or editing workflows:

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

Validation

After generating or editing a workflow file, validate it with EAS CLI from the Expo project root:

sh
npx -y eas-cli@latest workflow:validate .eas/workflows/<workflow.yml> --non-interactive

Run the command separately for each changed workflow file. It requires a logged-in EAS CLI session and a linked Expo project. Unlike schema-only validation, it also checks build profile references against the project's eas.json and performs EAS server-side validation. Fix every reported error and rerun the command until it prints Workflow configuration YAML is valid. Do not replace this command with a local YAML or JSON Schema validator.

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.

Submitting Feedback

If you encounter errors, misleading or outdated information in this skill, report it so Expo can improve:

bash
npx --yes submit-expo-feedback@latest --category skills --subject "eas-workflows" "<actionable feedback>"

Only submit when you have something specific and actionable to report. Include as much relevant context as possible. If an AI agent repeatedly failed or the user had to take over an Expo task, load the expo-skill-feedback skill and follow its eval-candidate flow instead of reusing the command above.

© expo, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 3 other files (scripts) in plugins/expo/skills/eas-workflows of expo/skills.

  • SKILL.md
  • agents/openai.yaml
  • scripts/fetch.js
  • scripts/package.json

Open the folder on GitHubat commit d4f4840

Compare with similar skills

Eas Workflows next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Eas Workflows compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Eas Workflows this skillexpo/skills2.7k—~1.2kAutomated safety check: PassMIT
Expo Cicd WorkflowsCherryHQ/cherry-studio-app4k6 repos~870Automated safety check: PassMIT
GitHub Actionscallstackincubator/agent-skills1.7k1 repos~703Automated safety check: PassMIT
Gem Devops Guidelinesgithub/awesome-copilot40k1 repos~743Automated safety check: PassMIT
Frb CI Filterfzyzcjy/flutter_rust_bridge5.4k—~2.4kAutomated safety check: PassMIT
Android Cicddavila7/claude-code-templates32k—~2.2kAutomated safety check: PassMIT

Similar skills

  • Expo Cicd Workflows

    CherryHQ/cherry-studio-app

    Helps understand and write EAS workflow YAML files for Expo projects.

    4k GitHub starsUsed in 6 repos~870 tokens
    MobileAuto-check passed

  • GitHub Actions

    callstackincubator/agent-skills

    Official

    GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts.

    1.7k GitHub starsUsed in 1 repo~703 tokens
    DevOps & CloudAuto-check passed

  • Gem Devops Guidelines

    github/awesome-copilot

    Official

    Design or review infrastructure, deployment, CI/CD, Docker, Kubernetes, health checks, rollback, feature flags, production readiness, and mobile release workflows.

    40k GitHub starsUsed in 1 repo~743 tokens
    DevOps & CloudAuto-check passed

  • Frb CI Filter

    fzyzcjy/flutter_rust_bridge

    A skill your agent uses when running focused flutterrustbridge GitHub Actions CI via cifilter, adding/removing the ci-manual-dispatch PR label, choosing exact CI jobs or matrix entries, documenting…

    5.4k GitHub stars~2.4k tokensUpdated yesterday
    MobileAuto-check passed

  • Android Cicd

    davila7/claude-code-templates

    Automated Android CI/CD pipeline to Google Play — supports TWA, React Native, Flutter, and native Android.

    32k GitHub stars~2.2k tokensUpdated today
    MobileAuto-check passed

  • Flutter Cicd

    HoangNguyen0403/agent-skills-standard

    Set up CI/CD pipelines for Flutter apps. An agent skill from HoangNguyen0403/agent-skills-standard.

    570 GitHub stars~578 tokensUpdated today
    MobileAuto-check: notes

More from expo/skills

All 26 skills in this repo

  • Eas Update Insights

    expo/skills

    Official

    Check the health of published EAS Update: crash rates, install/launch counts, unique users, payload size, and the split between embedded and OTA users per channel.

    2.7k GitHub starsUsed in 4 repos~3.1k tokens
    Auto-check passed

  • Expo App Clip

    expo/skills

    Official

    Add an iOS App Clip target to an Expo app. An agent skill from expo/skills.

    2.7k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed

  • Expo Skill Eval

    expo/skills

    Official

    Evaluate Expo skills in this repo end-to-end - trigger accuracy, generated code quality, and runtime screenshots on iOS simulator and Android emulator via Expo Go (web optional).

    2.7k GitHub stars~12k tokensUpdated today
    Auto-check passed

  • Expo Skill Feedback

    expo/skills

    Official

    Submit feedback on an Expo skill—or Expo itself—and control bundled anonymous usage telemetry (off by default / opt-in).

    2.7k GitHub stars~1.3k tokensUpdated today
    Auto-check passed

  • Expo Module

    expo/skills

    Official

    Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).

    2.7k GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Expo Upgrade

    expo/skills

    Official

    Guidelines for upgrading Expo SDK versions and fixing dependency issues

    2.7k GitHub starsUsed in 9 repos~1.9k tokens
    Auto-check passed

Works with

Categories

Questions about Eas Workflows

What does Eas Workflows do?

Helps understand and write EAS workflow YAML files for Expo projects. Eas Workflows is an agent skill from expo/skills, published by the product's own GitHub organization. Helps understand and write EAS workflow YAML files for Expo projects.

When should I use Eas Workflows?

Eas Workflows fits situations like: the user asks about CI/CD; workflows in an Expo; mentions .eas/workflows/; wants help with EAS build pipelines.

How do I install Eas Workflows in Claude Code?

Run `npx skills add expo/skills --skill eas-workflows -a claude-code`. Or copy the skill folder (plugins/expo/skills/eas-workflows in expo/skills) into .claude/skills/eas-workflows in your project. Claude Code loads it when a task matches its description.

How do I install Eas Workflows in Codex?

Run `npx skills add expo/skills --skill eas-workflows -a codex`. Or copy the skill folder (plugins/expo/skills/eas-workflows in expo/skills) into .agents/skills/eas-workflows in your project. Codex loads it when a task matches its description.

Can I use Eas Workflows in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add expo/skills --skill eas-workflows -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/eas-workflows, .gemini/skills/eas-workflows, .github/skills/eas-workflows and .opencode/skills/eas-workflows in your project.

What does Eas Workflows need to run?

Going by SKILL.md and its folder, Eas Workflows needs JavaScript for the scripts in its folder and the command-line tools its instructions call (npx and node). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Bash(node:*), Bash(npx *eas-cli@*).

Does Eas Workflows access the network?

SKILL.md names 3 domains. As links in the text: raw.githubusercontent.com, expo.dev and api.expo.dev. This is read from the text; nothing was executed.

Is Eas Workflows safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Eas Workflows use?

Eas Workflows is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eas Workflows use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Eas Workflows?

Skills that share tags, products or a category with Eas Workflows: Expo Cicd Workflows (CherryHQ/cherry-studio-app, 4k stars), GitHub Actions (callstackincubator/agent-skills, 1.7k stars), Gem Devops Guidelines (github/awesome-copilot, 40k stars) and Frb CI Filter (fzyzcjy/flutter_rust_bridge, 5.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eas Workflows?

expo (a GitHub organization, an official publisher) maintains it in expo/skills, which has 2,661 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on October 6, 2026.

Source: expo/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.