expo-api-routes

Guidelines for creating API routes in Expo Router with EAS Hosting

1.07x

Quality

57%

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

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with numerous executable examples and concrete commands, but it is a monolithic single-file skill over 50 lines whose advanced sections could be split into referenced files, and its deploy/database workflows lack explicit validation feedback loops.

Suggestions

Split advanced material (EAS Hosting runtime limits, database options, deployment) into one-level-deep referenced files (e.g. DEPLOYMENT.md, DATABASES.md) with clearly signaled links from the main body.

Add explicit validation checkpoints to the deploy and database workflows, e.g. verify the route responds locally before deploying and re-test the endpoint after `eas deploy`.

Tighten the 'When NOT to Use' list and database-option catalog into brief pointers rather than annotated lists to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient — short labels with executable code and no 'what is an API route' preamble — but the 'When NOT to Use' list, database-option catalog, and explanatory notes like 'Use process.env for server-side secrets' pad sections that could be tightened.	2 / 3
Actionability	It provides complete, copy-paste-ready TypeScript for GET/POST/PUT/DELETE, dynamic routes, query params, headers, CORS, error handling, env vars, and a Turso DB example, plus concrete shell commands (npx expo serve, eas deploy) and curl tests.	3 / 3
Workflow Clarity	A deploy sequence (login → deploy → env vars → custom domain) and local-test flow are present, but risky operations such as database writes and auth lack explicit validation checkpoints or validate→fix→retry feedback loops, which caps this dimension at 2.	2 / 3
Progressive Disclosure	It is a single ~360-line document with no references, scripts, or assets; advanced material (runtime limits, database options, deployment) that could be split into one-level-deep files is kept inline, though section headers keep it organized.	2 / 3
	Total	9 / 12 Passed

Description

50%Weight 40%Scale 1-3

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 names a clear, specific niche (Expo Router API routes on EAS Hosting) but is a single abstract action with no explicit use-when trigger guidance and limited trigger-term coverage. It answers 'what' but not 'when' clearly.

Suggestions

Add an explicit 'Use when...' clause naming natural trigger phrases users would say, e.g. 'Use when building server endpoints, handling webhooks, or proxying third-party APIs in an Expo Router app deployed to EAS Hosting.'

Replace the single abstract action 'creating API routes' with several concrete actions (e.g. 'define GET/POST handlers, read request bodies, manage server-side secrets, handle CORS, and deploy to EAS Hosting').

Broaden trigger-term coverage with natural variations such as 'server endpoints', 'serverless functions', and 'backend routes' alongside 'API routes'.

Dimension	Reasoning	Score
Specificity	The phrase 'Guidelines for creating API routes' names the domain (Expo Router API routes) and one action ('creating'), but does not list multiple concrete actions; it is a single abstract action rather than a catalog like 'extract, fill, merge'.	2 / 3
Completeness	It clearly states 'what' (creating API routes in Expo Router with EAS Hosting) but has no 'Use when...' clause or equivalent explicit trigger guidance for when to use it, which caps completeness at 2.	2 / 3
Trigger Term Quality	It includes relevant technical terms a user would say ('API routes', 'Expo Router', 'EAS Hosting') but omits common natural variations such as 'endpoints', 'server functions', or 'backend'.	2 / 3
Distinctiveness Conflict Risk	The 'Expo Router with EAS Hosting' niche is specific, but 'API routes' is a concept shared across many frameworks and the absence of distinct trigger phrasing means it could overlap with other web-API skills.	2 / 3
	Total	8 / 12 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: 11c74d6

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