Eas Workflows
expo/skills
Helps understand and write EAS workflow YAML files for Expo projects.
Helps understand and write EAS workflow YAML files for Expo projects.
Install Expo Cicd Workflows
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflows --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .claude/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.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/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .claude/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflowsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflows --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .agents/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .agents/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflows --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .cursor/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .cursor/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/CherryHQ/cherry-studio-app.git --path .agents/skills/expo-cicd-workflows--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflows --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .gemini/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .gemini/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflowsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .github/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .github/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install CherryHQ/cherry-studio-app expo-cicd-workflows --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/CherryHQ/cherry-studio-app.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/expo-cicd-workflows .opencode/skills/expo-cicd-workflows && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "expo-cicd-workflows" agent skill from https://github.com/CherryHQ/cherry-studio-app/tree/main/.agents/skills/expo-cicd-workflows into .opencode/skills/expo-cicd-workflows/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "expo-cicd-workflows", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
expo-cicd-workflows- GitHub stars
- 4k
- Used in
- 6 other repos
- Token cost
- ~870 tokens
- SKILL.md length
- 348 words
- Files
- 4 (incl. scripts)
- Skills in repo
- 13
- 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 3 more sections
- Runs JavaScript scripts from its folder; calls node and npm
What it does
Expo Cicd Workflows is an agent skill from CherryHQ/cherry-studio-app. 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 870 tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/fetch.js`, `scripts/package.json` and `scripts/validate.js`).
It sits in Mobile, covering CI/CD and Cross-platform mobile apps. It works with Expo. The repository describes itself as: 🍒 This is the mobile version of Cherry Studio. 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 expo-cicd-workflows skill to help understand and write EAS workflow YAML files for Expo projects”
- “/expo-cicd-workflows”
Requirements
- Node.js
- Pre-approved tools (allowed-tools): Read, Write, Bash(node:*)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- JSON Schema — https://api.expo.dev/v2/workflows/schema
- Syntax Documentation — https://raw.githubusercontent.com/expo/expo/refs/heads/main/docs/pages/eas/workflows/syntax.mdx
- 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 3be36cc. 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:
ReadWriteBash(node:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (JavaScript), which the agent can run.
Shell commands in SKILL.md call:
nodenpm
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.comapi.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
Expo Cicd Workflows loads about 870 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 348 words of instructions outside code blocks.
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 CherryHQ/cherry-studio-app at commit 3be36cc, republished under its MIT licence (© CherryHQ). 348 words, ~870 tokens.
Download SKILL.mdSave it as
.claude/skills/expo-cicd-workflows/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- expo-cicd-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:*)
- version
- 1.0.0
- license
- MIT License
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 workflowon— Triggers that start the workflow (at least one required)jobs— Job definitions (required)defaults— Shared defaults for all jobsconcurrency— 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 informationinputs.*— Values fromworkflow_dispatchinputsneeds.*— Outputs and status from dependent jobsjobs.*— Job outputs (alternative syntax)steps.*— Step outputs within custom jobsworkflow.*— 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
needsandafterexist in the workflow - Check that expressions reference valid contexts and outputs
- Ensure
ifconditions 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.
© CherryHQ, 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 .agents/skills/expo-cicd-workflows of CherryHQ/cherry-studio-app.
- SKILL.md
- scripts/fetch.js
- scripts/package.json
- scripts/validate.js
Open the folder on GitHubat commit 3be36cc
Used in 6 other repositories
We found 21 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 6 other GitHub owners. This page covers the copy in CherryHQ/cherry-studio-app, which our catalogue first saw on October 7, 2026.
- adrianhajdin/react-native-lingua.agents/skills/expo-cicd-workflows
- aiskillstore/marketplaceskills/expo/expo-cicd-workflows
- sickn33/agentic-awesome-skillsskills/expo-cicd-workflowsplugins/agentic-awesome-skills/skills/expo-cicd-workflows+3 more
- lingxling/awesome-skills-cnantigravity-awesome-skills/skills/expo-cicd-workflowsantigravity-awesome-skills/plugins/agentic-awesome-skills/skills/expo-cicd-workflows+3 more
- LeoYeAI/openclaw-master-skillsskills/expo-cicd-workflows
- henryalouf/ruflow.agents/skills/expo-cicd-workflows.agents/skills/antigravity-awesome-skills/skills/expo-cicd-workflows+6 more
Compare with similar skills
Expo Cicd 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Expo Cicd Workflows this skillCherryHQ/cherry-studio-app | 4k | 6 repos | ~870 | Automated safety check: Pass | MIT | |
| Eas Workflowsexpo/skills | 2.7k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Frb CI Filterfzyzcjy/flutter_rust_bridge | 5.4k | — | ~2.4k | Automated safety check: Pass | MIT | |
| GitHub Actionscallstackincubator/agent-skills | 1.7k | 1 repos | ~703 | Automated safety check: Pass | MIT | |
| Android Cicddavila7/claude-code-templates | 32k | — | ~2.2k | Automated safety check: Pass | MIT | |
| Flutter CicdHoangNguyen0403/agent-skills-standard | 571 | — | ~578 | Automated safety check: Notes | MIT |
Similar skills
- Official
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…
- Official
GitHub Actions
callstackincubator/agent-skills
GitHub Actions workflow patterns for React Native iOS simulator and Android emulator cloud builds with downloadable artifacts.
Android Cicd
davila7/claude-code-templates
Automated Android CI/CD pipeline to Google Play — supports TWA, React Native, Flutter, and native Android.
Flutter Cicd
HoangNguyen0403/agent-skills-standard
Set up CI/CD pipelines for Flutter apps. An agent skill from HoangNguyen0403/agent-skills-standard.
- Official
React Native Best Practices
vercel-labs/openreview
A prioritized rule set for React Native and Expo apps covering list performance, animation, navigation, UI patterns, state, rendering, monorepos and configuration.
More from CherryHQ/cherry-studio-app
All 13 skills in this repoNative Data Fetching
CherryHQ/cherry-studio-app
A skill your agent uses when implementing or debugging ANY network request, API call, or data fetching.
Building Native UI
CherryHQ/cherry-studio-app
Complete guide for building beautiful apps with Expo Router.
Expo Tailwind Setup
CherryHQ/cherry-studio-app
Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling
Diagnose
CherryHQ/cherry-studio-app
Opt-in evidence-first causal diagnosis for bugs, browser or app/device failures, flaky behavior, and performance regressions.
Improve React
CherryHQ/cherry-studio-app
Survey a whole React codebase as a senior React engineer, using React Doctor's scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper…
Diagnose Fix Loop
CherryHQ/cherry-studio-app
Iterative diagnose-and-fix workflow that repeatedly uses the diagnose skill to find a proven problem, plan the smallest credible improvement, implement it, re-diagnose, and continue until no useful…
Related
Works with
Categories
Questions about Expo Cicd Workflows
What does Expo Cicd Workflows do?
Helps understand and write EAS workflow YAML files for Expo projects. Expo Cicd Workflows is an agent skill from CherryHQ/cherry-studio-app. Helps understand and write EAS workflow YAML files for Expo projects.
When should I use Expo Cicd Workflows?
Expo Cicd 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 Expo Cicd Workflows in Claude Code?
Run `npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a claude-code`. Or copy the skill folder (.agents/skills/expo-cicd-workflows in CherryHQ/cherry-studio-app) into .claude/skills/expo-cicd-workflows in your project. Claude Code loads it when a task matches its description.
How do I install Expo Cicd Workflows in Codex?
Run `npx skills add CherryHQ/cherry-studio-app --skill expo-cicd-workflows -a codex`. Or copy the skill folder (.agents/skills/expo-cicd-workflows in CherryHQ/cherry-studio-app) into .agents/skills/expo-cicd-workflows in your project. Codex loads it when a task matches its description.
Can I use Expo Cicd 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 CherryHQ/cherry-studio-app --skill expo-cicd-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/expo-cicd-workflows, .gemini/skills/expo-cicd-workflows, .github/skills/expo-cicd-workflows and .opencode/skills/expo-cicd-workflows in your project.
What does Expo Cicd Workflows need to run?
Going by SKILL.md and its folder, Expo Cicd Workflows needs JavaScript for the scripts in its folder and the command-line tools its instructions call (node and npm). Our summary lists: Node.js. Its frontmatter pre-approves these tools: Read, Write, Bash(node:*).
Does Expo Cicd Workflows access the network?
SKILL.md names 2 domains. As links in the text: raw.githubusercontent.com and api.expo.dev. This is read from the text; nothing was executed.
Is Expo Cicd 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 Expo Cicd Workflows use?
Expo Cicd 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 Expo Cicd Workflows use?
About 870 tokens (SKILL.md is roughly 3.5k 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 Expo Cicd Workflows?
Skills that share tags, products or a category with Expo Cicd Workflows: Eas Workflows (expo/skills, 2.7k stars), Frb CI Filter (fzyzcjy/flutter_rust_bridge, 5.4k stars), GitHub Actions (callstackincubator/agent-skills, 1.7k stars) and Android Cicd (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Expo Cicd Workflows?
CherryHQ (a GitHub organization) maintains it in CherryHQ/cherry-studio-app, which has 3,976 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 9, 2026.
Source: CherryHQ/cherry-studio-app on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.