nextjs-developer
Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke for full-stack features, performance optimization, SEO implementation, production deployment.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill nextjs-developer64
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
82%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 solid description that clearly identifies when to use the skill and includes good trigger terms for Next.js development. The main weakness is that the capabilities listed are somewhat high-level categories rather than concrete actions, and some terms like 'full-stack features' and 'performance optimization' could cause overlap with other web development skills.
Suggestions
Replace high-level terms like 'full-stack features' with specific actions such as 'configure route handlers, implement middleware, set up API routes'
Add more distinctive Next.js-specific triggers like 'RSC', 'use server', 'generateStaticParams', 'next.config.js' to reduce conflict with general React skills
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Next.js 14+ with App Router) and mentions some actions like 'performance optimization, SEO implementation, production deployment', but these are high-level categories rather than concrete specific actions like 'configure server components' or 'implement streaming SSR'. | 2 / 3 |
Completeness | Explicitly answers both what (building Next.js 14+ applications with specific features) and when ('Use when building...', 'Invoke for...'). The 'Use when' and 'Invoke for' clauses provide clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Next.js', 'App Router', 'server components', 'server actions', 'full-stack', 'performance optimization', 'SEO', 'production deployment'. These are terms developers naturally use when working with Next.js. | 3 / 3 |
Distinctiveness Conflict Risk | While 'Next.js 14+ with App Router' is specific, terms like 'full-stack features', 'performance optimization', and 'SEO implementation' could overlap with general React skills or other web framework skills. The Next.js-specific terms help but don't fully eliminate conflict risk. | 2 / 3 |
Total | 10 / 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 has strong organizational structure with excellent progressive disclosure through its reference table, but critically lacks actionable code examples. The constraints are useful but abstract - Claude would benefit from seeing actual implementation patterns rather than just being told what to use. The workflow needs validation checkpoints for a production deployment context.
Suggestions
Add executable code examples for key patterns: a basic server component with data fetching, a server action with form handling, and proper Metadata API usage
Include validation checkpoints in the workflow, such as 'Run `next build` and verify no errors' and 'Check Core Web Vitals with Lighthouse'
Replace the abstract 'Role Definition' paragraph with a concrete quick-start example showing a minimal App Router setup
Add a troubleshooting section or common pitfalls with specific error messages and fixes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'Role Definition' paragraph explaining years of experience and the 'Related Skills' section which adds little value. The MUST DO/MUST NOT DO lists are useful but could be tighter. | 2 / 3 |
Actionability | The skill lacks any executable code examples. It describes what to do ('Use Server Components by default', 'Use native fetch with caching options') but provides no concrete implementation patterns, code snippets, or copy-paste ready examples. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a reasonable sequence but lacks validation checkpoints. There's no guidance on how to verify each step succeeded, no feedback loops for error recovery, and the steps are too high-level to be immediately actionable. | 2 / 3 |
Progressive Disclosure | Excellent use of reference table pointing to specific topic files with clear 'Load When' guidance. The structure is clean with one-level-deep references, and the main skill serves as a proper overview without being monolithic. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.