expo-api-routes

Guidelines for creating API routes in Expo Router with EAS Hosting

1.07x

Quality

60%

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

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

The skill is a strong, highly actionable reference with comprehensive executable examples, but it is a monolithic single file with no progressive disclosure and its deployment workflow lacks explicit validation checkpoints. Splitting advanced sections into reference files and adding verification steps would lift the weaker dimensions.

Suggestions

Move advanced material (EAS Hosting/Cloudflare Workers runtime limits, database options, deployment details) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Add explicit validation/verification checkpoints to the deployment and database workflows (e.g. 'verify the route responds with curl after deploy', 'confirm env vars are set with eas env:list').

Tighten redundant basic examples (e.g. consolidate the repeated simple GET snippets across HTTP Methods and Request Handling) to improve conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient code-led reference material with brief intros, though a few sections (repeated basic GET examples, separate query/headers/body snippets) could be trimmed, matching 'Efficient; minor instances of over-explanation'.	4 / 5
Actionability	It provides copy-paste-ready, executable TypeScript and bash across all common cases (HTTP verbs, dynamic routes, query/headers/body, env vars, CORS, error handling, local testing, deployment, database, auth, proxy), matching 'Fully executable; specific examples cover the common cases'.	5 / 5
Workflow Clarity	A rough sequence exists in the deployment section (prerequisites -> deploy -> env vars -> custom domain) but there are no explicit validation checkpoints or feedback loops, matching 'Steps listed but validation gaps'.	3 / 5
Progressive Disclosure	The ~360-line body is well-sectioned but entirely inlined with no bundle files or one-level-deep references; advanced topics (Cloudflare Workers runtime, database options, deployment) could be split out, matching 'Some structure but content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

48%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 names a specific, distinct niche but is light on concrete actions and entirely lacks an explicit 'Use when' trigger clause, capping completeness. Adding trigger phrases and 1-2 more concrete verbs would raise specificity and completeness.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building server-side API endpoints in an Expo Router app deployed to EAS Hosting.'

Replace the single verb 'creating' with several concrete actions such as 'creating, securing, and deploying API routes' to improve specificity.

Include natural synonyms users might say (e.g. 'serverless functions', 'backend endpoints', 'server routes') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'Guidelines for creating API routes in Expo Router with EAS Hosting' names a specific domain but offers only the single generic action 'creating', matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It states a clear 'what' (guidelines for creating API routes) but has no 'Use when...' or equivalent trigger clause, so per the rubric a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	'API routes', 'Expo Router', and 'EAS Hosting' are relevant natural terms a developer would say, but common synonyms like 'serverless functions', 'backend endpoints', or 'server routes' are absent.	3 / 5
Distinctiveness Conflict Risk	The Expo Router + EAS Hosting niche is mostly distinct with only minor overlap risk against generic backend or Next.js API-route skills; not a 5 because the missing when-clause weakens it as a pure trigger.	4 / 5
	Total	12 / 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: 1e28582

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.