eas-hosting
An agent skill by expo, from expo/skills. Tags: cloudflare, configuration, custom-domain, deployment, web, workers.
What it does
EAS service (paid). 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 within the Cloudflare Workers runtime. Also covers authoring API routes (+api.ts handlers, HTTP methods, request handling, CORS). Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains. Not for native builds or store releases - use the eas-app-stores skill for those.
Install
With the skills CLI, which installs into Claude Code, Codex, Cursor and other agents:
npx skills add expo/skills --skill eas-hosting
Or copy the skill folder into Claude Code's skills directory by hand (~/.claude/skills for every project, or .claude/skills inside one):
git clone --depth 1 https://github.com/expo/skills
cp -r skills/plugins/expo/skills/eas-hosting ~/.claude/skills/eas-hosting
Safety box score
Grade D, elevated risk: 47 of 100 risk points, rated 2026-10-19. The grade rates what the skill and its scripts can reach on the machine of whoever installs it, across eight categories from shell execution to secrets access. How the score works.
This skill deploys Expo web apps and Expo Router API routes to EAS Hosting, including production/preview releases, environment secrets, custom domains, and optional deploy automation. The main risks are public publication of changes, handling secrets, and running remote CLI packages from the npm registry.
| Category | Level | Why |
|---|---|---|
| Code & shell execution | 2 (moderate) | It directs the agent to run CLI commands such as `npm install -g eas-cli`, `npx expo serve`, `npx expo export -p web`, and `npx eas-cli@latest deploy`, so it can execute installed and registry-fetched tools. |
| Network access | 2 (moderate) | It sends code and deploy artifacts to Expo/EAS Hosting and includes remote operations like `eas env:create` plus `npx --yes submit-expo-feedback@latest`, which communicate with Expo services. |
| Filesystem reach | 1 (low) | It asks for project-local file changes like creating `.env` and `.eas/workflows/deploy.yml`, but does not require writing outside the working directory. |
| Secrets & credentials | 2 (moderate) | It explicitly handles secrets via `.env`, `process.env.OPENAI_API_KEY`, `process.env.TURSO_AUTH_TOKEN`, and `eas env:create --name OPENAI_API_KEY --value sk-xxx --environment production`. |
| Privilege & persistence | 1 (low) | The prerequisite `npm install -g eas-cli` makes a global user-level install, but it does not require sudo or system service changes. |
| Instruction hijack surface | 0 (none) | I found no instructions to ignore safeguards, hide behavior, follow fetched prompts, or otherwise manipulate the agent’s decision-making. |
| Irreversible actions | 3 (high) | `npx eas-cli@latest deploy --prod` publishes to production, and the workflow example auto-deploys on `push` to `main`, which is inherently high-impact publication. |
| Transparency | 1 (low) | Several commands use remote, unpinned packages such as `npx eas-cli@latest` and `npx --yes submit-expo-feedback@latest`, so the exact code being run is not visible in the skill files. |
Before installing
- Review `eas.json` and `.eas/workflows/*.yml` for automatic deploy behavior before using `--prod`.
- Pin or vendor the `npx ...@latest` commands if you need reproducible, inspectable installs.
- Test secret setup in a throwaway Expo project or account before creating production `eas env:create` entries.
- Confirm the target Expo project/account has the intended permissions before enabling deploys from `main`.
Rated 2026-10-19 by an automated review of 2 files from the skill's repository.
Source
- Repository
- expo/skills (all skills from this repository)
- Path
- plugins/expo/skills/eas-hosting/SKILL.md
- Branch
- main
- Collection
- expo
- Updated
- 2026-09-22
Related skills
- workers-best-practices — Cloudflare Workers best practices for production applications. Use when writing, reviewing, or configuring Workers.
- eas-update — EAS service (paid). Configure and use EAS Update for over-the-air JavaScript and asset updates with expo-updates and EAS CLI.
- deployment — Deploy applications to DigitalOcean App Platform via GitHub Actions with proper environment management and secrets handling.
- launch-with-aws — Migrates vibe-coded web applications to AWS.
- aws-amplify — Build and deploy full-stack web and mobile apps with AWS Amplify Gen2 (TypeScript code-first).
- durable-objects — Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.