nextjs-app-router-patterns
Master Next.js 14+ App Router with Server Components, streaming, parallel routes, and advanced data fetching. Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components.
77
67%
Does it follow best practices?
Impact
97%
1.08xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/frontend-mobile-development/skills/nextjs-app-router-patterns/SKILL.mdQuality
Discovery
92%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 is a strong skill description that clearly identifies its domain (Next.js 14+), lists specific capabilities, and includes an explicit 'Use when' clause with relevant trigger terms. The main weakness is a slight risk of overlap with general React or web development skills, though the Next.js-specific terminology helps mitigate this. The use of 'Master' as the opening verb is slightly informal but the description otherwise uses appropriate third-person framing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: App Router, Server Components, streaming, parallel routes, and advanced data fetching. These are distinct, identifiable features of Next.js 14+. | 3 / 3 |
Completeness | Clearly answers both 'what' (Next.js 14+ App Router with Server Components, streaming, parallel routes, advanced data fetching) and 'when' (explicit 'Use when building Next.js applications, implementing SSR/SSG, or optimizing React Server Components'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Next.js', 'App Router', 'Server Components', 'SSR/SSG', 'streaming', 'parallel routes', 'React Server Components'. These cover common variations of how developers discuss this technology. | 3 / 3 |
Distinctiveness Conflict Risk | While Next.js-specific features like App Router and parallel routes are distinctive, there could be overlap with a general React skill or a broader web framework skill. The mention of 'React Server Components' and 'SSR/SSG' could trigger alongside other React-related skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a condensed Next.js App Router tutorial with high-quality, executable code examples, but it fails to respect Claude's existing knowledge of Next.js—most of this content is well-documented framework behavior. The monolithic structure with 8 detailed patterns inline makes it token-expensive without proportional value, and it lacks workflow guidance for when/how to apply these patterns in sequence.
Suggestions
Reduce to a concise reference of project-specific conventions and non-obvious gotchas, removing patterns that mirror standard Next.js documentation (e.g., basic route handlers, metadata generation).
Split detailed patterns into separate referenced files (e.g., PATTERNS.md, CACHING.md) and keep SKILL.md as a brief overview with navigation links.
Add a decision workflow: 'When building a new page, follow this sequence: 1. Determine rendering mode → 2. Set up data fetching → 3. Add Suspense boundaries → 4. Verify with `next build` for static/dynamic classification'.
Focus content on non-obvious pitfalls and project-specific conventions rather than standard Next.js API usage that Claude already knows well.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~400+ lines, with extensive code examples that cover well-documented Next.js patterns Claude already knows. The 'When to Use This Skill' section, rendering modes table, and file conventions are all standard Next.js documentation that Claude has deep familiarity with. Much of this could be reduced to a concise reference of project-specific conventions. | 1 / 3 |
Actionability | The code examples are fully executable, copy-paste ready TypeScript with proper imports, types, and realistic patterns. Each pattern includes complete component implementations with error handling, and the caching strategies section provides concrete fetch options with clear comments. | 3 / 3 |
Workflow Clarity | The patterns are presented as independent examples rather than a sequenced workflow. There are no validation checkpoints, no guidance on verifying that implementations work correctly, and no error recovery steps. For a skill covering migration and architecture decisions, the lack of a clear decision workflow or verification steps is a gap. | 2 / 3 |
Progressive Disclosure | All content is inlined in a single monolithic file with no references to external files for detailed patterns. The 8 full pattern examples with complete code blocks create a wall of content that would be better organized with a concise overview linking to separate pattern files. | 1 / 3 |
Total | 7 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (538 lines); consider splitting into references/ and linking | Warning |
Total | 10 / 11 Passed | |
- Repository
- wshobson/agents
- Commit
91fe43e
- 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.