Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.
97
100%
Does it follow best practices?
Impact
95%
1.13xAverage score across 6 eval scenarios
Passed
No known issues
Quality
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 an excellent skill description that hits all the marks. It opens with a clear 'Use when' clause, lists specific concrete actions, and provides comprehensive trigger terms that users would naturally use. The description is well-structured, uses third person voice appropriately, and carves out a distinct niche for Next.js 14+ App Router development.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, deploy to Vercel'. | 3 / 3 |
Completeness | Clearly answers both what (configure route handlers, implement middleware, etc.) and when ('Use when building Next.js 14+ applications...') with explicit trigger terms listed at the end. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say including 'Next.js', 'App Router', 'Server Components', 'Server Actions', 'RSC', 'use server', 'Vercel', 'generateMetadata', and file patterns like 'loading.tsx'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Next.js 14+ with App Router architecture; distinct triggers like 'RSC', 'use server', 'generateMetadata', and 'loading.tsx' clearly differentiate it from generic React or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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 exemplifies best practices: it's concise yet comprehensive, provides executable code examples, has clear workflow steps with validation, and uses progressive disclosure effectively through the reference table. The constraints section is particularly strong with specific MUST DO/MUST NOT DO rules that prevent common Next.js mistakes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of concepts Claude already knows (like what Next.js or React is). Every section provides actionable information without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for server components, server actions, and generateMetadata. The constraints section gives specific, concrete rules rather than vague guidance. | 3 / 3 |
Workflow Clarity | The core workflow has clear numbered steps with an explicit validation checkpoint in the deploy step (run next build, check env vars, run Lighthouse). The MUST DO/MUST NOT DO constraints provide additional guardrails for error prevention. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to one-level-deep topic files. The main skill provides a concise overview while signaling where to find detailed guidance for specific topics like App Router, Server Components, etc. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
5b76101
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.