eas-workflows skill: write and validate EAS workflow YAML for Expo CI/CD pipelines

• scripts/fetch.js downloads the schema and docs, with caching

  The agent runs node scripts/fetch.js on three URLs: the workflow JSON schema from api.expo.dev and the syntax and pre-packaged jobs docs from raw.githubusercontent.com. The script caches responses in a .cache folder next to it for 15 minutes by default. SKILL.md says fetching the schema is necessary.

  Try: “Create an EAS workflow that builds a preview on every pull request.”

  Runs code · Fetch reference documents

• Writes .eas/workflows/*.yml, 16 KiB or smaller

  Checks required fields per job type, that needs and after references exist, that expressions use valid contexts, and that if conditions fit the schema limits.

  Write · Generate or edit workflow files

• name, on, jobs, defaults, concurrency, and ${{ }} syntax

  Lists the top-level keys and expression contexts such as github, inputs, needs, jobs, steps and workflow.

  Read · Top-level structure and expressions

• Runs eas-cli workflow:validate on each changed file

  Uses npx -y eas-cli@latest workflow:validate with --non-interactive. It needs a logged-in EAS session and a linked project, and also checks eas.json build profiles and EAS server rules.

  Runs code · Validate with EAS CLI

• Derives job types, triggers and runners from the live schema

  SKILL.md says not to rely on memorized values because they change as EAS adds features.

  Try: “Which runner types can an EAS workflow job use?”

  Network · Answer questions from the schema

• Can send feedback about the skill to Expo

  SKILL.md tells the agent to run npx --yes @expo/agent-cli@latest feedback for specific, actionable problems with the skill, or after repeated failures at an Expo task.

  Runs code · Feedback command

Watch out for

• The plugin route adds a remote MCP server

  The Expo plugin the README recommends for Claude Code and Codex ships a .mcp.json that registers an http MCP server at https://mcp.expo.dev/mcp, on top of the 23 skills in plugins/expo/skills. Its plugin.json lists a name, version (1.14.3), description and author. The skills CLI route installs only this one skill and adds no MCP server. github.com

• Workflows can spend EAS minutes

  The files it writes define jobs that consume your plan's build and compute minutes once they run. Check triggers before you merge, so a workflow does not run on every push.

• The fetch script downloads any URL you give it

  scripts/fetch.js fetches the URL passed to it and writes a cache folder beside the script. SKILL.md points it at three Expo URLs.

• Validation uses your EAS login

  workflow:validate needs a logged-in EAS session and contacts EAS servers. Check which project and account are linked.

• It can send feedback to Expo

  SKILL.md tells the agent to run npx --yes @expo/agent-cli@latest feedback with a short report. Read the text first if you do not want task details shared.