expo-api-routes

Guidelines for creating API routes in Expo Router with EAS Hosting

1.07x

Quality

71%

Does it follow best practices?

Impact

100%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/expo/skills/expo-api-routes/SKILL.md

The canonical home for this skill is expo-api-routes in administrakt0r/AI-Agents-Safe-Coding-Skills

Quality

Content

78%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.

This is a strong, highly actionable reference: nearly every section is complete executable TypeScript or CLI commands covering the full create-test-deploy lifecycle. Its weaknesses are structural — everything is packed into one long file with no progressive disclosure, and a small amount of generic content (basic error handling, CORS) pads the token budget.

Suggestions

Split the SKILL.md into an overview plus one-level-deep references (e.g. references/runtime.md for EAS Hosting limitations and database options, references/patterns.md for auth middleware and proxy patterns) to shrink the always-loaded context.

Trim sections Claude already knows well (generic try/catch error handling, standard CORS header boilerplate) down to Expo-specific notes only.

Add a short explicit workflow line ('1. Create the route file, 2. Test with npx expo serve + curl, 3. Set production env vars, 4. eas deploy') so the sequence and validation checkpoints are stated, not just implied by section order.

Dimension	Reasoning	Score
Conciseness	The body is predominantly executable code with minimal prose and assumes Expo/Cloudflare knowledge rather than re-explaining it, but sections on generic try/catch error handling and CORS boilerplate pad it slightly beyond what Claude already knows.	4 / 5
Actionability	Nearly every section gives copy-paste-ready, complete code: HTTP method handlers, dynamic routes, query/header/body parsing, env-var usage, curl test commands, eas deploy commands, and client-side fetch examples cover the common cases.	5 / 5
Workflow Clarity	Sections follow a sensible create -> test-locally (curl) -> deploy sequence with a concrete local verification step, but the sequence is implicit in section order rather than stated as explicit ordered steps with checkpoints.	4 / 5
Progressive Disclosure	The body has clear section headers but is a ~370-line single file with no reference files; content that belongs in separate references (EAS runtime limitations, database options, common patterns) is inlined, fitting the anchor for structure present but content that should be separate is inline.	3 / 5
	Total	16 / 20 Passed

Description

52%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.

The description is highly distinctive and names its domain precisely, but it is underpowered as a trigger: it lists only one generic action and provides no 'Use when...' guidance, so Claude has little explicit help deciding when to load it. Adding concrete capabilities and trigger phrases would lift it substantially.

Suggestions

Add 2-3 concrete actions, e.g. 'Create, test, and deploy API endpoints for Expo apps, with env-var secrets, CORS, and webhook handling'.

Append an explicit trigger clause, e.g. 'Use when the user mentions Expo API routes, backend endpoints, EAS Hosting, or server-side code in an Expo app'.

Include natural synonyms users say ('API endpoint', 'backend', 'webhook', 'serverless') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain precisely ('API routes in Expo Router with EAS Hosting') but offers only one generic action ('creating'), matching the anchor for domain named with minimal/generic actions rather than the 1-2 concrete actions of score 3.	2 / 5
Completeness	The 'what' is clear (guidelines for creating API routes) but there is no 'Use when...' clause or any explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	'API routes', 'Expo Router', and 'EAS Hosting' are terms an Expo developer would naturally say, but common variations like 'API endpoint', 'backend', 'serverless', or 'webhook' are missing, fitting the anchor for some relevant keywords without common variations.	3 / 5
Distinctiveness Conflict Risk	The pairing of 'Expo Router' and 'EAS Hosting' carves out a clear niche with distinct triggers and minimal overlap with other skills; it would not plausibly fire for the wrong skill.	5 / 5
	Total	13 / 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: openai/plugins
Path: plugins/expo/skills/expo-api-routes/SKILL.md
Commit: 5fd93af

Reviewed: 9 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.