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.
80
71%
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
100%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+ App Router), lists specific capabilities, and includes an explicit 'Use when' clause with natural trigger terms. The only minor note is the use of 'Master' at the beginning which is slightly informal/imperative rather than third-person declarative, but the rest of the description uses appropriate voice. Overall it would perform well in skill selection among many candidates.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: App Router, Server Components, streaming, parallel routes, and advanced data fetching. These are distinct, identifiable technical features rather than vague abstractions. | 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 Next.js development. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Next.js 14+ App Router paradigm, which is a clear niche. The mention of specific features like parallel routes, streaming, and Server Components distinguishes it from generic React or web development skills. | 3 / 3 |
Total | 12 / 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 that duplicates well-known documentation. While the code examples are high-quality and executable, the content is far too verbose for a skill file—it explains concepts Claude already knows thoroughly and fails to organize the extensive content across multiple files. The skill would benefit greatly from being reduced to a concise decision guide with project-specific conventions, splitting detailed patterns into referenced files.
Suggestions
Reduce the SKILL.md to a concise overview (~50-80 lines) covering only non-obvious patterns or project-specific conventions, and move detailed code examples into separate referenced files (e.g., PATTERNS.md, CACHING.md, SEO.md).
Remove explanations of basic Next.js concepts (rendering modes table, file conventions) that Claude already knows—focus on gotchas, edge cases, and opinionated decisions specific to the project.
Add a workflow section with validation checkpoints for common multi-step tasks like migration from Pages Router or setting up parallel routes, including how to verify each step works correctly.
Add clear navigation links to split-out reference files so the skill follows progressive disclosure (e.g., '**Parallel Routes**: See [PARALLEL_ROUTES.md](PARALLEL_ROUTES.md) for full examples').
| 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 or non-obvious patterns. | 1 / 3 |
Actionability | The code examples are fully executable, copy-paste ready TypeScript with proper imports, type annotations, and realistic patterns. Each pattern includes complete component implementations with error handling and real-world usage contexts. | 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 | The entire skill is a monolithic wall of code examples with no references to external files. At this length, caching strategies, route handlers, metadata/SEO, and individual patterns should be split into separate reference files with the SKILL.md serving as a concise overview with links. | 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
27a7ed9
- 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.