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.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/nextjs-developer/SKILL.md

Quality

Content

57%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with excellent progressive disclosure via a clean reference table, but it provides no executable code, relies on reference files for implementation detail, and lacks validation checkpoints in its build workflow. Role-play padding and a buzzword list mildly hurt token efficiency.

Suggestions

Add at least one copy-paste-ready minimal example (e.g., a server component with fetch caching, or an App Router layout with Metadata API) so the body is actionable without loading a reference.

Insert an explicit validation step in the Core Workflow (e.g., 'Run `next build` and resolve type/build errors before deploying').

Drop the role-play experience claims and the trailing Knowledge Reference buzzword list, or move them into a reference file, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly efficient bullet/table formatting, but the role-play ('senior full-stack developer with 10+ years of experience', 'blazing-fast') and the trailing Knowledge Reference buzzword list add padding Claude does not need, so it could be tightened.	3 / 5
Actionability	Concrete rules appear (MUST DO/MUST NOT DO, 'use client', next/image, Metadata API) and a reference table routes to detail files, but the body itself contains no executable code or commands and defers real implementation guidance to the references.	3 / 5
Workflow Clarity	A clear 5-step Core Workflow is sequenced (architecture -> routing -> data -> optimize -> deploy), but validation/checkpoint steps are missing or only implicit, matching the anchor where checkpoints are absent.	3 / 5
Progressive Disclosure	A clear overview with a well-signaled one-level-deep Reference Guide table (topic -> file -> 'Load When'), all five referenced files exist, and content is appropriately split for easy navigation.	5 / 5
	Total	14 / 20 Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, well-triggered, and distinct, with explicit 'Use when'/'Invoke for' guidance covering the main Next.js App Router contexts. Its main weakness is that the 'what' is phrased as capability domains rather than crisp discrete actions.

Suggestions

Reframe the 'what' as concrete verbs on objects (e.g., 'Build App Router routes and layouts, implement server components and server actions, configure data fetching and caching') instead of 'building ... with' / 'Invoke for' categories.

Add a couple of natural synonyms users might say (e.g., 'RSC', 'Next.js deployment', '.next') to push trigger coverage toward comprehensive.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas (App Router, server components, server actions, full-stack features, performance optimization, SEO, deployment), but the verbs are generic ('building', 'Invoke for') rather than discrete concrete actions, leaving minor coverage gaps versus the comprehensive anchor.	4 / 5
Completeness	Explicit 'Use when...' and 'Invoke for...' clauses answer when clearly, and the what (building Next.js 14+ apps with App Router/RSC/server actions) is present; the what could be more concrete (it leans on domains rather than discrete actions), so it sits below the fully-explicit anchor 5.	4 / 5
Trigger Term Quality	Strong natural keyword coverage a developer would say ('Next.js 14+', 'App Router', 'server components', 'server actions', 'SEO', 'deployment'), but a few common synonyms or variations are missing versus the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Next.js 14+ App Router, server components, server actions) with distinct triggers and minimal conflict risk against unrelated skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: zebbern/claude-code-guide
Path: skills/nextjs-developer/SKILL.md
Commit: 59c5fc4

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.