More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    EAS Workflows: CI/CD for Expo Apps

    1

    Author, validate, and debug EAS Workflow YAML the reliable way: derive every file from the live schema, gate builds behind tests, scope triggers, and keep build minutes under control.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    EAS Workflows: CI/CD for Expo Apps

    EAS Workflows: CI/CD for Expo Apps

    Example session with this skill installed

    We ship builds by hand right now. Set up CI/CD for our Expo app: tests on every pull request, iOS and Android builds plus store submission when we merge to main, and a shareable web preview for PRs. Our eas.json already has preview and production profiles. Keep the build-minute bill sane.

    • Read your context and instructions
    • Compiled the eas workflows

    Pipeline designed and authored schema-first: the current workflows schema was fetched this session, and every job type, trigger, and parameter below was read out of it — nothing from memory.

    Two files, because triggers and cost profiles differ:

    1. pr.yml — on pull_request (opened, synchronize): a test job, then a web deploy job with prod: false so every PR gets a shareable preview URL. No native builds on PRs: that's the single biggest minute-saver in the design, worth roughly two full builds per PR iteration.

    2. release.yml — on push to main: test gates everything. build_ios and build_android (profile: production) run in parallel, each conditioned on the push event so the graph's skip case is explicit. submit_ios needs only build_ios; submit_android needs only build_android — neither platform waits on the other. A production web deploy rides the same trigger.

    Details handled: profiles referenced exactly as named in your eas.json; store credentials and environment variables referenced by name from EAS environments, none inline; concurrency set per branch so a rapid second merge cancels the superseded run instead of double-spending.

    Validation: both files run through eas-cli workflow:validate — schema, profile resolution, and server-side checks — and print valid. Estimated cost per merged PR: one test run + two builds + two submits; per PR iteration: one test run + one preview deploy.

    1) pr.yml

    Connects securely to your tools. The creator never sees your data.

    About this skill

    EAS Workflows turn YAML files in your Expo project into pipelines that test, build, deploy, and submit your app — but the syntax moves fast, and YAML written from memory or copied from an old blog post fails in expensive ways. This skill enforces the discipline that makes workflows boring: fetch the current JSON schema before writing a line, design the job graph (what gates what, what runs on PRs vs. merges, what a skipped conditional does to its dependents) before touching YAML, and validate every file with the official CLI validator, which also resolves your build-profile references server-side. It includes a worked release pipeline (PR tests, merge builds for both platforms, per-platform submit, web deploy), a fill-in workflow skeleton, a pre-flight checklist, a failure playbook for the six symptoms that eat afternoons, and explicit cost design — triggers scoped tightly, builds on merge rather than every PR push, and a per-run cost estimate delivered with every workflow. Secrets stay referenced by name, never inline.

    • Workflow YAML must be derived from the live schema at authoring time; if the schema can't be fetched, the skill delivers the pipeline design and marks YAML as pending rather than guessing syntax.
    • It designs pipelines around pre-packaged job types and standard custom jobs; highly custom native build steps may need bespoke job definitions beyond the templates.
    • Store acceptance is outside the workflow's control — the skill gets a valid binary delivered; App Store / Play review outcomes are the stores' decision.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    Requires

    eas-cli
    Node.js

    Permissions

    Terminal / Shell
    Listed24 days ago
    Updated21 days ago

    What's inside

    Frequently Asked Questions

    Because the schema evolves — job types, parameters, and triggers change between EAS releases, and a stale example fails at validation or, worse, at run time after spending minutes. The skill fetches the current schema every session and validates with the official CLI, which also checks your eas.json profile references.

    Trigger scope. The usual cause is native builds firing on every PR push to every branch. The design rules here build on merge, test and preview on PRs, set per-branch concurrency so superseded runs cancel, and attach a per-run cost estimate to every workflow so spend is predictable.

    It references them by name from EAS environments and never puts secret values in YAML. Configuring the credentials themselves in your Apple Developer and Google Play accounts stays a manual, account-owner step — the workflow can only use credentials that already exist.

    New in Mobile Development