Name: eas-hosting
Rating: 68.8 (1 reviews)
Author: expo

eas-hosting

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.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured skill body with concrete code throughout. The main weakness is workflow clarity: the deployment flow omits an explicit validate-preview-before-promoting-to-production checkpoint, which the rubric caps at 3 for consequential deploys.

Suggestions

Add an explicit validation step to the deploy workflow, e.g. after the preview deploy instruct Claude to verify the preview URL responds correctly before running `eas deploy --prod`.

Tighten the 'When to Use API Routes' and 'When NOT to Use API Routes' lists, or collapse the repetitive request-handling examples (query params, headers, body) into a single consolidated block to reduce tokens.

Consider moving the Cloudflare Workers runtime limitations and database-options detail into a separate reference file referenced from the body, keeping SKILL.md as a leaner overview.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence (no explanations of Request/Response/fetch basics) and length is driven by concrete code, but the 'When to Use / When NOT to Use' advisory lists and several near-identical request-handling code blocks could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready code for every common case plus executable commands (npx expo export -p web, eas deploy --prod, eas env:create, curl tests) and complete EAS workflow YAML examples.	5 / 5
Workflow Clarity	The deploy sequence is present (prereqs → export → preview → prod → env → domain → workflows) but lacks an explicit validation checkpoint before promoting a preview to production; the destructive/batch cap applies since production deploys are consequential.	3 / 5
Progressive Disclosure	No bundle files exist, but the single SKILL.md is well-organized with clear section headers and cross-skill references (eas-workflows, expo-skill-feedback) are clearly signaled; some runtime/pattern content could plausibly live in separate reference files.	4 / 5
	Total	16 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: specific, third-person, with an explicit trigger clause and clear boundary guidance against the related eas-app-stores skill. The only minor gap is synonym/extension coverage in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — exporting the web bundle, running eas deploy for production and PR previews, managing env secrets, custom domains, Cloudflare Workers runtime, and authoring +api.ts handlers — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (deploy websites/API routes, export, manage secrets/domains, author API routes) and 'when' with a concrete 'Use when…' trigger clause, plus a negative-scope boundary.	5 / 5
Trigger Term Quality	The 'Use when deploying an Expo web app or API routes, setting up EAS Hosting, or configuring hosting environments and domains' clause covers natural phrases users would say, but omits common synonyms like 'ship'/'publish' and has no file-extension triggers.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear EAS Hosting niche and explicitly disambiguates with 'Not for native builds or store releases - use the eas-app-stores skill for those', minimizing conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: expo/skills
Path: plugins/expo/skills/eas-hosting/SKILL.md
Commit: 3970866

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.