nextjs-developer
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.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 provides specific concrete actions, comprehensive trigger terms covering natural developer vocabulary, explicit 'Use when' and 'Triggers on' clauses, and a clearly defined niche around Next.js 14+ App Router development that distinguishes it from general React or older Next.js skills.
| 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' (building Next.js 14+ apps with specific actions like configuring route handlers, middleware, API routes, streaming SSR, etc.) and 'when' (explicit 'Use when' clause at the start plus a 'Triggers on' list of keywords). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including variations like 'Next.js', 'Next.js 14', 'App Router', 'RSC', 'React Server Components', 'Server Actions', 'use server', 'Vercel', 'loading.tsx', and 'generateMetadata'. These are terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Next.js 14+ with App Router specifically. The trigger terms are specific to this framework version and its unique features (RSC, Server Actions, generateMetadata), making it unlikely to conflict with generic React or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid Next.js skill with excellent actionability through concrete, executable code examples and clear constraints. Its main weaknesses are the missing bundle files that the reference table points to, reducing the progressive disclosure to aspirational rather than functional, and the workflow lacking intermediate validation checkpoints between major steps. The content is mostly concise but could trim the introductory persona description and the keyword-dump Knowledge Reference section.
Suggestions
Add the five referenced files (references/app-router.md, references/server-components.md, etc.) to the bundle so progressive disclosure actually functions as designed.
Add intermediate validation checkpoints to the Core Workflow (e.g., after step 2: 'Verify routes render with next dev', after step 3: 'Confirm data loads in server components before optimizing').
Remove the introductory persona sentence and the 'Knowledge Reference' keyword list at the bottom — neither adds actionable value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Senior Next.js developer with expertise in...') and the Knowledge Reference section at the bottom is a keyword dump that adds little value. The constraints section has some items Claude would already know (e.g., use next/image over img), but most content earns its place. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready TSX code examples for server components with data fetching, server actions with form handling, and generateMetadata for dynamic SEO. Constraints are specific and concrete with clear do/don't guidance. | 3 / 3 |
Workflow Clarity | The core workflow lists steps at a high level but validation only appears at the final deploy step. There are no intermediate validation checkpoints (e.g., after implementing routing or data layer). For a multi-step workflow involving architecture decisions and data layer setup, the lack of feedback loops between steps caps this at 2. | 2 / 3 |
Progressive Disclosure | The reference table with 'Load When' guidance is well-structured and clearly signaled, but no bundle files are provided, meaning all five referenced files (references/app-router.md, etc.) are missing. The skill attempts good progressive disclosure architecture but cannot deliver on it without the actual reference files. | 2 / 3 |
Total | 9 / 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.
- Repository
- jeffallan/claude-skills
- Commit
e8be415
- 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.