CtrlK
BlogDocsLog inGet started
Tessl Logo

expo-api-routes

Guidelines for creating API routes in Expo Router with EAS Hosting

53

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/expo-api-routes/SKILL.md

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

SKILL.md
Quality
Evals
Security

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.

A well-organized, highly actionable reference with strong executable examples, held back by an inlined monolithic structure and deploy/test workflows that omit validation checkpoints. Splitting detailed sections into reference files and adding verify steps would lift the weaker dimensions.

Suggestions

Add an explicit validation checkpoint after `eas deploy` (e.g. curl the deployed URL or run `eas deploy --logs`) so the deployment workflow has a verify step.

Move the database-options, EAS-runtime-limitations, and common-patterns sections into separate reference files (e.g. references/databases.md) linked one level deep from SKILL.md.

Trim the few restating-the-obvious lines (e.g. 'This builds and deploys your API routes to EAS Hosting (Cloudflare Workers).') to tighten conciseness toward a 5.

DimensionReasoningScore

Conciseness

The body is code-first and mostly lean, assuming Claude's competence, with only minor instances of restating the obvious (e.g. 'This builds and deploys your API routes to EAS Hosting').

4 / 5

Actionability

Provides copy-paste-ready, executable TypeScript and bash examples covering GET/POST/PUT/DELETE, dynamic routes, query params, headers, env vars, CORS, error handling, auth, and deployment.

5 / 5

Workflow Clarity

The deploy and test sequences are present but lack explicit validation checkpoints (no 'verify the deploy succeeded' step), so it sits at the sequence-present-but-checkpoints-missing anchor.

3 / 5

Progressive Disclosure

Content is well-sectioned but the entire 360-line reference is inlined in SKILL.md with no external reference files; chunks like database options, common patterns, and runtime limitations could live in separate one-level-deep references.

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 clearly identifies a specific niche but is terse: it states what the skill covers without any explicit 'when to use it' trigger guidance. Adding a 'Use when...' clause with natural trigger phrases would materially raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when building server endpoints in Expo Router, adding backend routes for EAS Hosting, or proxying third-party APIs from an Expo app.'

Add natural synonyms users might say ('API endpoints', 'server functions', 'backend routes') to broaden trigger coverage.

List a second concrete action beyond 'creating' (e.g. 'create, test, and deploy API routes') to lift specificity.

DimensionReasoningScore

Specificity

Names the domain ('API routes in Expo Router with EAS Hosting') but the only action is the generic 'creating', matching the 'names domain, actions minimal' anchor rather than the multi-action anchor above.

2 / 5

Completeness

The 'what' is clear (guidelines for creating API routes) but there is no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes relevant technical terms ('API routes', 'Expo Router', 'EAS Hosting') a developer might say, but lacks synonyms or variations like 'endpoints', 'server functions', or 'backend'.

3 / 5

Distinctiveness Conflict Risk

The Expo Router + EAS Hosting combination is a clear niche with distinct triggers, with only minor overlap risk against general backend or Next.js API-route skills.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.