expo-api-routes
Guidelines for creating API routes in Expo Router with EAS Hosting
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 100%
↑ 1.07xAgent success when using this skill
Validation for skill structure
Discovery
22%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too brief and vague to effectively guide skill selection. It lacks concrete actions, explicit trigger conditions, and reads more like a document title than a functional skill description. The technical terms provide some distinctiveness but are insufficient for reliable skill matching.
Suggestions
Add specific concrete actions like 'Create API endpoints, configure route handlers, set up authentication middleware, deploy serverless functions'
Add a 'Use when...' clause with trigger terms like 'Use when building backend routes in Expo, creating API endpoints for React Native apps, or deploying server functions to EAS'
Include common user phrases and variations such as 'server routes', 'backend endpoints', 'serverless', 'Expo API', '+api.ts files'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language ('Guidelines for creating') without listing concrete actions. It doesn't specify what actions Claude can perform - no verbs like 'create', 'configure', 'deploy', or specific capabilities. | 1 / 3 |
Completeness | Only weakly addresses 'what' (guidelines for API routes) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance. The description doesn't tell Claude when to select this skill. | 1 / 3 |
Trigger Term Quality | Contains some relevant technical keywords ('API routes', 'Expo Router', 'EAS Hosting') that users familiar with the Expo ecosystem would use, but missing common variations like 'backend', 'server routes', 'endpoints', or 'serverless functions'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Expo Router' and 'EAS Hosting' provides some specificity to the Expo ecosystem, but 'API routes' is generic enough to potentially conflict with other API or routing skills. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
79%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, actionable skill with excellent code examples and clear guidance on when to use API routes. The content is concise and assumes Claude's competence. Main weaknesses are the lack of explicit validation steps in workflows and the monolithic structure that could benefit from progressive disclosure to separate files.
Suggestions
Add explicit validation checkpoints to the deployment workflow (e.g., 'Verify deployment succeeded: eas deploy:status' or 'Test production endpoint before proceeding')
Split advanced topics like database options, authentication patterns, and CORS handling into separate reference files (e.g., DATABASES.md, AUTH.md) with brief summaries in the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using code examples directly without explaining basic concepts Claude already knows. Each section delivers actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples throughout. Every pattern includes complete TypeScript code with proper imports, request handling, and response formatting. | 3 / 3 |
Workflow Clarity | Steps for deployment and testing are listed but lack explicit validation checkpoints. The deployment section shows commands but doesn't include verification steps to confirm successful deployment or troubleshooting guidance. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a long monolithic document (~300 lines) that could benefit from splitting advanced topics (CORS, authentication patterns, database options) into separate reference files. | 2 / 3 |
Total | 10 / 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 | |
- 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.