expo-api-routes
Guidelines for creating API routes in Expo Router with EAS Hosting
66
48%
Does it follow best practices?
Impact
100%
1.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/expo/skills/expo-api-routes/SKILL.mdQuality
Discovery
32%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 identifies a specific technology stack (Expo Router + EAS Hosting) but is too terse and lacks explicit trigger guidance. It reads more like a document title than a skill description, missing concrete actions and a 'Use when...' clause that would help Claude select it appropriately.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about creating API routes, server endpoints, or backend logic in Expo Router with EAS Hosting.'
List specific concrete actions the skill covers, e.g., 'Defines API route handlers, configures HTTP methods (GET, POST, etc.), sets up middleware, and deploys server routes to EAS Hosting.'
Include natural keyword variations users might say, such as 'server routes', 'API endpoints', '+api.ts files', 'Expo backend', or 'EAS deploy'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (API routes, Expo Router, EAS Hosting) and implies the action (creating), but does not list multiple specific concrete actions like defining endpoints, handling requests, configuring middleware, etc. | 2 / 3 |
Completeness | Describes 'what' at a high level (guidelines for creating API routes) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also weak, so this scores 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'API routes', 'Expo Router', and 'EAS Hosting' that users might naturally mention, but misses common variations like 'server routes', 'backend endpoints', 'API endpoints', 'expo api', or file extensions like '+api.ts'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Expo Router' and 'EAS Hosting' narrows the niche somewhat, but 'API routes' is broad enough to potentially overlap with general API or routing skills. Adding more specific triggers would reduce conflict risk. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive, highly actionable reference for Expo Router API routes with excellent executable code examples covering all common patterns. Its main weaknesses are length (could benefit from splitting advanced topics into separate files) and missing validation/verification steps in the deployment workflow. The 'when to use/not use' sections add moderate value but contribute to verbosity.
Suggestions
Add explicit validation checkpoints to the deployment workflow: verify deployment succeeded with a curl test, check logs for errors, and include rollback guidance.
Split advanced content (database options, common patterns, Cloudflare Workers limitations) into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Trim the 'When NOT to Use' section — Claude can infer most of these anti-patterns from the 'When to Use' section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'When to Use' and 'When NOT to Use' sections explain decision-making context that adds some value but is somewhat verbose for Claude. The code examples are clean and not padded, but the overall document is long with sections like 'Database Options' listing five options with one-line descriptions that could be trimmed. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready TypeScript code for every pattern — basic routes, dynamic routes, query params, headers, JSON body, CORS, error handling, auth middleware, proxying, database integration, and deployment commands. All examples are concrete and complete. | 3 / 3 |
Workflow Clarity | The deployment workflow (prerequisites → deploy → env vars) is listed but lacks validation checkpoints — there's no step to verify the deployment succeeded, test the production endpoint, or handle deployment failures. The testing section provides curl commands but doesn't establish a validate-then-deploy workflow. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic document (~250 lines) with no references to external files. Sections like 'Common Patterns', 'EAS Hosting Runtime', and 'Database Options' could be split into separate reference files. However, the section headers provide reasonable internal navigation. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- expo/skills
- Commit
09ee211
- Reviewed
Table of Contents
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.