Help us improve
Share bugs, ideas, or general feedback.
From antigravity-bundle-expo-react-native
Creates, edits, and validates EAS workflow YAML files for Expo projects in .eas/workflows/. Guides CI/CD pipelines, build automation, triggers, and deployments using fetched JSON schema.
npx claudepluginhub sickn33/antigravity-awesome-skills --plugin antigravity-bundle-expo-react-nativeHow this skill is triggered — by the user, by Claude, or both
Slash command
/antigravity-bundle-expo-react-native:expo-cicd-workflowsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Help developers write and edit EAS CI/CD workflow YAML files.
Creates, edits, and validates EAS workflow YAML files for Expo projects in .eas/workflows/. Guides CI/CD pipelines, build automation, triggers, and deployments using fetched JSON schema.
Generates, edits, and validates EAS workflow YAML files for Expo CI/CD pipelines. Useful for .eas/workflows/, EAS builds, and deployment automation.
Write and optimize GitHub Actions workflows for CI/CD pipelines, configuring triggers, managing artifacts, and debugging runs.
Share bugs, ideas, or general feedback.
Help developers write and edit EAS CI/CD workflow YAML files.
.eas/workflows/*.yml files for an Expo project.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
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
Do not rely on memorized values; these resources evolve as new features are added.
Workflows live in .eas/workflows/*.yml (or .yaml).
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 runsConsult the schema for the full specification of each section.
Use ${{ }} syntax for dynamic values. The schema defines available contexts:
github.* — GitHub repository and event informationinputs.* — Values from workflow_dispatch inputsneeds.* — Outputs and status from dependent jobsjobs.* — Job outputs (alternative syntax)steps.* — Step outputs within custom jobsworkflow.* — Workflow metadataWhen generating or editing workflows:
needs and after exist in the workflowif conditions respect the schema's length constraintsAfter 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.
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.