route-handlers

This skill should be used when the user asks to "create an API route", "add an endpoint", "build a REST API", "handle POST requests", "create route handlers", "stream responses", or needs guidance on Next.js API development in the App Router.

1.22x

Quality

80%

Does it follow best practices?

Impact

93%

1.22x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./.trae/skills/route-handlers/SKILL.md

Quality

Discovery

72%

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 excels at providing trigger terms and establishing a clear niche for Next.js App Router API development. However, it's structured backwards - it focuses entirely on when to use the skill without first explaining what the skill actually does. Adding a capability statement would significantly improve its effectiveness.

Suggestions

Add a leading capability statement describing what the skill does, e.g., 'Creates and configures Next.js App Router API routes, including route handlers, request/response handling, and streaming responses.'

Restructure to follow the 'what then when' pattern: start with concrete actions the skill performs, then follow with the 'Use when...' trigger guidance.

Dimension	Reasoning	Score
Specificity	The description names the domain (Next.js API development, App Router) and mentions some actions like 'create an API route', 'add an endpoint', 'handle POST requests', 'stream responses', but these are presented as trigger phrases rather than concrete capabilities the skill performs.	2 / 3
Completeness	The description focuses heavily on 'when' (trigger phrases) but lacks a clear 'what does this do' statement. It tells Claude when to use it but doesn't explain what capabilities or actions the skill provides beyond the implied context of the triggers.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'create an API route', 'add an endpoint', 'build a REST API', 'handle POST requests', 'create route handlers', 'stream responses'. These are realistic phrases developers would use when needing this skill.	3 / 3
Distinctiveness Conflict Risk	The description is clearly scoped to Next.js App Router API development with specific triggers like 'route handlers' and 'App Router'. This creates a distinct niche that wouldn't conflict with general backend API skills or other Next.js skills focused on different areas.	3 / 3
	Total	10 / 12 Passed

Implementation

87%

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

This is a high-quality API reference skill that provides comprehensive, executable examples for Next.js Route Handlers. The content is well-organized and token-efficient, covering all major use cases from basic CRUD to streaming. The main weakness is the lack of an explicit step-by-step workflow for creating new routes, treating the content more as a reference than a guided tutorial.

Suggestions

Add a 'Quick Start Workflow' section at the top with numbered steps: 1) Create route file, 2) Export HTTP method, 3) Test with curl/fetch, 4) Verify response

Include a brief validation/testing step showing how to verify the route works (e.g., a curl command or simple fetch example)

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, jumping directly into file conventions and code examples without explaining what APIs are or how HTTP works. Every section provides actionable code without unnecessary preamble.	3 / 3
Actionability	All examples are fully executable TypeScript/JavaScript code with proper imports, type definitions, and realistic patterns. Code is copy-paste ready with complete function signatures and proper error handling.	3 / 3
Workflow Clarity	While individual patterns are clear, there's no explicit workflow for creating a new API route from scratch, and no validation steps for testing endpoints. The content is more of a reference than a guided process.	2 / 3
Progressive Disclosure	Excellent structure with clear sections progressing from basic to advanced (structure → request → response → streaming → caching → errors). References to detailed docs are well-signaled at the end with one-level-deep links.	3 / 3
	Total	11 / 12 Passed

Validation

90%

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 — 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: Lingjie-chen/MT5
Commit: 3069d33

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