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.
92
86%
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 clearly defines its scope (Next.js 14+ with App Router), lists specific concrete actions, and provides comprehensive trigger terms. It follows the recommended pattern with explicit 'Use when' and 'Triggers on' clauses, uses third-person voice throughout, and is distinctive enough to avoid conflicts with related skills like generic React or other framework 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' (configure route handlers, implement middleware, set up API routes, streaming SSR, etc.) and 'when' with an explicit 'Use when' clause at the start and a 'Triggers on' list at the end. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including common variations: 'Next.js', 'Next.js 14', 'App Router', 'RSC', 'use server', 'Server Components', 'Server Actions', 'React Server Components', 'generateMetadata', 'loading.tsx', 'Vercel'. These are terms users would 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 enough (App Router, RSC, Server Actions, generateMetadata, loading.tsx) to avoid conflicting with generic React skills or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 strong actionability through executable code examples and excellent progressive disclosure via the reference table. The main weaknesses are some unnecessary verbosity (role description, keyword list) and a workflow that lacks intermediate validation checkpoints for the architecture and data layer steps. The constraints section is particularly well-crafted with clear MUST DO/MUST NOT DO boundaries.
Suggestions
Remove the opening role description line and the 'Knowledge Reference' keyword list at the bottom — they consume tokens without adding actionable guidance.
Add intermediate validation checkpoints to the Core Workflow (e.g., after step 2: verify routes render with `next dev`; after step 3: confirm data fetching works with no runtime errors).
| 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 just a keyword list that adds no actionable value. The 'Output Templates' section is also somewhat generic. However, the constraints and code examples are well-targeted. | 2 / 3 |
Actionability | Provides fully executable, copy-paste-ready TypeScript/TSX code examples covering server components with data fetching, server actions with form handling, and generateMetadata for SEO. The constraints are specific and concrete (e.g., 'use native fetch with explicit cache/next.revalidate options'). | 3 / 3 |
Workflow Clarity | The core workflow lists steps but validation only appears at the final deploy step. For a skill involving multi-step architecture and data layer setup, intermediate validation checkpoints are missing. The deploy validation step is good but there's no feedback loop for earlier steps like routing or data layer implementation. | 2 / 3 |
Progressive Disclosure | Excellent use of a reference table with clear 'Load When' triggers pointing to one-level-deep reference files. The main SKILL.md serves as a well-organized overview with quick-start code examples inline and detailed guidance deferred to specific reference documents. | 3 / 3 |
Total | 10 / 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
3d95bb1
- 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.