This skill should be used when the user asks to "create a Next.js route", "add a page", "set up layouts", "implement loading states", "add error boundaries", "organize routes", "create dynamic routes", or needs guidance on Next.js App Router file conventions and routing patterns.
80
71%
Does it follow best practices?
Impact
96%
1.39xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.trae/skills/app-router/SKILL.mdQuality
Discovery
54%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 has strong trigger term coverage and clear distinctiveness for Next.js App Router tasks, but fundamentally fails at completeness by only describing when to use the skill without explaining what it actually does. The structure is inverted - it reads like a 'Use when...' clause without the preceding capability description.
Suggestions
Add a capability statement before the trigger phrases, e.g., 'Creates and organizes Next.js App Router pages, layouts, loading states, and error boundaries following file conventions.'
Restructure to follow the pattern: '[What it does]. Use when [triggers].' rather than leading with 'This skill should be used when...'
Include specific outputs or deliverables the skill provides, such as 'generates route files', 'configures nested layouts', or 'implements streaming with Suspense boundaries'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Next.js App Router) and mentions several actions like 'create routes', 'add pages', 'set up layouts', but these are presented as trigger phrases rather than concrete capability descriptions. The description lacks a clear statement of what the skill actually does. | 2 / 3 |
Completeness | The description only addresses 'when' (trigger conditions) but completely omits 'what' - there's no explanation of what capabilities the skill provides or what it actually does. It's essentially just a list of trigger phrases without describing the skill's functionality. | 1 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'create a Next.js route', 'add a page', 'set up layouts', 'implement loading states', 'add error boundaries', 'dynamic routes'. These are realistic phrases developers would use when seeking help. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific to Next.js App Router with distinct triggers like 'App Router file conventions', 'loading states', 'error boundaries'. Unlikely to conflict with general web development or other framework skills due to the specific Next.js terminology. | 3 / 3 |
Total | 9 / 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 well-crafted skill that efficiently documents Next.js App Router patterns with excellent use of tables for quick reference and complete, executable code examples. The content assumes Claude's competence and avoids unnecessary explanations. The only minor weakness is the lack of explicit step-by-step workflows with validation checkpoints, though for a reference-style skill focused on conventions and patterns, this is a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, using tables for quick reference and avoiding explanations of concepts Claude already knows. Every section provides actionable information without padding. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for all major patterns including pages, layouts, dynamic routes, loading states, and error boundaries. TypeScript interfaces and proper imports are included. | 3 / 3 |
Workflow Clarity | While the file conventions and patterns are clearly documented, there's no explicit workflow for creating routes (e.g., 'first create folder, then add page.tsx, then verify route works'). For a reference-style skill this is acceptable, but validation steps are missing. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, well-organized sections progressing from basic to advanced, and clearly signaled one-level-deep references to detailed documentation at the end. | 3 / 3 |
Total | 11 / 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 | |
3069d33
Table of Contents
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.