nextjs

Guide for implementing Next.js - a React framework for production with server-side rendering, static generation, and modern web features. Use when building Next.js applications, implementing App Router, working with server components, data fetching, routing, or optimizing performance.

Quality

59%

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 ./claude/skills/nextjs/SKILL.md

Quality

Content

35%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 content is a large, self-contained Next.js reference that scores well on actionability through many code examples but fails conciseness and progressive disclosure by inlining an entire docs-like tutorial into SKILL.md instead of linking out. Workflow clarity is capped by the absence of validation/verification steps for build and deploy operations.

Suggestions

Split the bulk of the reference (routing, data fetching, metadata, image/font optimization, deployment) into separate files under references/ and keep SKILL.md as a concise overview that links to them one level deep.

Trim or remove explanations of concepts Claude already knows (what SSR is, what Server vs Client Components are, basic Next.js architecture) and rely on the llms.txt docs link instead.

Add explicit validation/verification checkpoints to the build and deploy workflow (e.g., 'run next build and confirm no errors before deploying') to lift workflow clarity above the cap.

Dimension	Reasoning	Score
Conciseness	The ~1120-line body is a near-monolithic dump of Next.js reference material explaining concepts Claude already knows (App Router vs Pages Router, what Server Components are, image/font optimization boilerplate), heavily padded and duplicative of the official docs link it already cites.	1 / 5
Actionability	It provides numerous concrete, mostly executable code blocks (create-next-app commands, route handlers, data fetching, middleware, Dockerfile) with only minor gaps such as placeholder helper functions (getPost, getSession) that are not fully defined.	4 / 5
Workflow Clarity	A rough implementation checklist and section sequence exist, but there are no validation checkpoints or feedback loops for destructive or batch operations (e.g., build/deploy), and the cap for missing validation on such operations applies.	3 / 5
Progressive Disclosure	Despite a single one-level link to https://nextjs.org/docs/llms.txt, almost all reference content is inlined into SKILL.md with no split files, no references/ or scripts/ bundle, and no well-signaled navigation to separate detailed materials.	1 / 5
	Total	9 / 20 Passed

Description

83%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, uses third-person voice, and explicitly answers both what the skill does and when to use it with concrete trigger phrases. Minor gaps in keyword synonyms and breadth of action coverage keep a couple dimensions just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions ('implementing App Router', 'working with server components', 'data fetching, routing, or optimizing performance') but coverage is broad rather than comprehensive, leaving minor gaps like API routes and deployment unstated.	4 / 5
Completeness	Clearly answers both 'what' (a React framework for production with SSR, static generation) and 'when' with an explicit 'Use when building Next.js applications, implementing App Router...' clause listing concrete trigger phrases.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say (Next.js, App Router, server components, routing, performance) but is missing some common synonyms and file extensions like .tsx or React framework phrasing.	4 / 5
Distinctiveness Conflict Risk	The Next.js / App Router / server components niche is mostly distinct from other skills, though it could overlap marginally with a generic React skill.	4 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1129 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: einverne/dotfiles
Path: claude/skills/nextjs/SKILL.md
Commit: 7d18cf4

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.