Content
67%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is highly actionable with complete, executable code and a clearly sequenced workflow backed by an explicit verification section and a real deep-dive reference file. Its main weakness is token efficiency: much of the body is standard Next.js boilerplate Claude already knows, and significant detail duplicated with the 823-line reference is inlined rather than delegated.
Suggestions
Trim or delegate standard boilerplate (full tsconfig.json dump, stock root layout, next/font setup, basic metadata/sitemap examples) to the reference file, keeping SKILL.md focused on the non-obvious: Next.js 15+ async request APIs, 'use cache' directives, default.tsx pitfalls, and client/server boundary rules.
Add brief error-recovery guidance to the Verification section (e.g., what to check when tsc fails on route context props, or when the build manifest shows unexpected ƒ (Dynamic) entries) to close the feedback-loop gap.
Move the Step 8 parallel/intercepting-routes detail into references/app-router-patterns.md (it already covers this in section 6) and keep only a pointer plus the key pitfall note inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~640-line body inlines substantial boilerplate Claude already knows: a full tsconfig.json dump, a stock root layout with next/font, standard metadata/sitemap examples, and a standard middleware example — matching anchor 2 ("noticeably verbose; several unnecessary... sections"). Not anchor 1: there is no explanatory prose padding and the genuinely version-sensitive content (async params in 15+, 'use cache', default.tsx pitfall) is high-value. | 2 / 5 |
Actionability | Code is fully executable and copy-paste ready throughout: concrete create-next-app flags, await-ed params typings, a working middleware matcher regex, Zod env validation, and route handlers with explicit error handling — matching anchor 5 ("Fully executable; copy-paste ready code or commands; specific examples cover the common cases"). | 5 / 5 |
Workflow Clarity | Ten clearly sequenced steps plus a Verification section with explicit automated gates (next lint, tsc --noEmit, next build manifest inspection, next start runtime checks) match anchor 4. It falls short of anchor 5 because there are no error-recovery feedback loops (e.g., what to do when the build manifest shows unexpected dynamic rendering), but checkpoints are explicit and specific, well above anchor 3. | 4 / 5 |
Progressive Disclosure | The body is well-sectioned and points to a real, one-level-deep reference (references/app-router-patterns.md, 823 lines, verified on disk, with its own table of contents) clearly signaled via the "Deep Dive Reference" section — matching anchor 4. Not anchor 5: substantial content duplicated with the reference (parallel routes, caching, metadata, streaming) is inlined in SKILL.md when it more appropriately belongs in the reference file. | 4 / 5 |
Total | 15 / 20 Passed |