Agent skill

Eas Workflows

by sickn33 in sickn33/agentic-awesome-skills

Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal.

MITAuto-check passed

Install Eas Workflows

skills CLI
$ npx skills add sickn33/agentic-awesome-skills --skill eas-workflows -a claude-code

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

GitHub CLI
$ gh skill install sickn33/agentic-awesome-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/sickn33/agentic-awesome-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/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
47k
Used in
1 other repo
Token cost
~1.3k tokens
SKILL.md length
590 words
Files
3 (incl. scripts)
Skills in repo
1,394
Repo updated
First seen
Licence
MIT

At a glance

Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal.

  • Works in 3 steps: JSON Schema —… → Syntax Documentation —… → Pre-packaged Jobs —…
  • The workflow matches the user goal
  • SKILL.md covers When to Use, Reference Documentation, Workflow File Location and Top-Level Structure, plus 7 more sections
  • Runs JavaScript scripts from its folder; calls npx and node

What it does

Eas Workflows is an agent skill from sickn33/agentic-awesome-skills. Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal.

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

The repository describes itself as: AAS Core is the local, agent-first control plane for complete catalog discovery, agent-owned selection, stack validation, and planning, backed by 2,400+ agentic skills. Includes… The licence is MIT.

When your agent uses it

  • The workflow matches the user goal

Example prompts

  • “/eas-workflows”

Requirements

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

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 1e53ce2. 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@*)
    • version:
    • 1.0.0
    • license:
    • MIT
    • License

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Ships 1 file 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.3k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 590 words of instructions outside code blocks.

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

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 sickn33/agentic-awesome-skills at commit 1e53ce2, republished under its MIT licence (© sickn33). 590 words, ~1,309 tokens.

Download SKILL.mdSave it as .claude/skills/eas-workflows/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
eas-workflows
description
Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal.
allowed-tools
Read, Write, Bash(node:*), Bash(npx *eas-cli@*), version:, 1.0.0, license:, MIT, License
source_repo
expo/skills
source_type
official
source
expo
date_added
2026-09-21
risk
unknown

When to Use

  • Use when this upstream workflow matches the user's stated goal.
  • Use when the task requires the procedures documented in this skill.

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

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

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.

Examples

text
User: Apply this skill to my current task.
Assistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.

Limitations

  • Imported upstream skill; verify credentials, permissions, and safety boundaries before execution.
  • Does not replace environment-specific validation, testing, or maintainer review.

© sickn33, 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 2 other files (scripts) in skills/eas-workflows of sickn33/agentic-awesome-skills.

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

Open the folder on GitHubat commit 1e53ce2

Used in 1 other repository

We found 5 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in sickn33/agentic-awesome-skills, which our catalogue first saw on October 7, 2026.

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 skillsickn33/agentic-awesome-skills47k1 repos~1.3kAutomated safety check: PassMIT
Upstream PRyc-software/qm15k—~2.3kAutomated safety check: NotesMIT
Og URL Matchthedaviddias/Front-End-Checklist74k—~543Automated safety check: PassMIT
Eas Updateexpo/skills2.7k—~2.5kAutomated safety check: PassMIT
Update From Upstream Mainremotion-dev/remotion62k—~1kAutomated safety check: PassCustom licence
Eas Hostingexpo/skills2.7k2 repos~2.9kAutomated safety check: NotesMIT

Similar skills

  • Upstream PR

    yc-software/qm

    Send a change to upstream qm without leaking organization-specific context.

    15k GitHub stars~2.3k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Og URL Match

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing Open Graph tags or investigating why social share counts appear low.

    74k GitHub stars~543 tokensUpdated yesterday
    Auto-check passed
  • Eas Update

    expo/skills

    Official

    Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI.

    2.7k GitHub stars~2.5k tokensUpdated yesterday
    MobileAuto-check passed
  • Update From Upstream Main

    remotion-dev/remotion

    Official

    Update the current Remotion branch with the latest canonical main branch.

    62k GitHub stars~1k tokensUpdated today
    Media & CreativeAuto-check passed
  • Eas Hosting

    expo/skills

    Official

    Deploy Expo websites and Expo Router API routes to EAS Hosting - export the web bundle, run eas deploy for production and PR preview URLs, manage environment secrets and custom domains, and work…

    2.7k GitHub starsUsed in 2 repos~2.9k tokens
    MobileAuto-check: notes
  • Eas Workflows

    expo/skills

    Official

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

    2.7k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from sickn33/agentic-awesome-skills

All 1,394 skills in this repo
  • Liuguang Banlan UI

    sickn33/agentic-awesome-skills

    Implements an interface in one of two named color modes, iridescent white or colorful black, from a parameterized starter that reports measured color intensity.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • User Thoughts Memory

    sickn33/agentic-awesome-skills

    Saves a user's project decisions, rules and preferences into a project-local mdbase so later sessions and other agents can recover the intent.

    47k GitHub starsUsed in 1 repo~2.5k tokens
    Auto-check passed
  • Using LWC Memory and Graphs

    sickn33/agentic-awesome-skills

    Keeps project decisions, research and verified results available across coding-agent sessions through LWC memory, a document Wiki graph and a CodeGraph code index.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed
  • Find Complementary Founders

    sickn33/agentic-awesome-skills

    Guides an agent through assessing its own owner for cofounder fit, publishing an approved profile, and ranking complementary profiles other agents published for their owners.

    47k GitHub starsUsed in 1 repo~4.8k tokens
    Auto-check passed
  • Whatsapp Cloud API

    sickn33/agentic-awesome-skills

    Integracao com WhatsApp Business Cloud API (Meta). An agent skill from sickn33/agentic-awesome-skills.

    47k GitHub starsUsed in 2 repos~4.5k tokens
    Auto-check passed
  • Cline Pilot

    sickn33/agentic-awesome-skills

    Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.

    47k GitHub starsUsed in 1 repo~4.6k tokens
    Auto-check passed

Questions about Eas Workflows

What does Eas Workflows do?

Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal. Eas Workflows is an agent skill from sickn33/agentic-awesome-skills. Curated upstream guidance for Eas Workflows; use when the workflow matches the user goal.

When should I use Eas Workflows?

Eas Workflows fits situations like: the workflow matches the user goal.

How do I install Eas Workflows in Claude Code?

Run `npx skills add sickn33/agentic-awesome-skills --skill eas-workflows -a claude-code`. Or copy the skill folder (skills/eas-workflows in sickn33/agentic-awesome-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 sickn33/agentic-awesome-skills --skill eas-workflows -a codex`. Or copy the skill folder (skills/eas-workflows in sickn33/agentic-awesome-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 sickn33/agentic-awesome-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@*), version:, 1.0.0, license:, MIT, License.

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 (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Eas Workflows use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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: Upstream PR (yc-software/qm, 15k stars), Og URL Match (thedaviddias/Front-End-Checklist, 74k stars), Eas Update (expo/skills, 2.7k stars) and Update From Upstream Main (remotion-dev/remotion, 62k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Eas Workflows?

sickn33 (a GitHub user) maintains it in sickn33/agentic-awesome-skills, which has 47,304 GitHub stars. The repository holds 1,394 skills in this directory. The repository was last updated on October 6, 2026.

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