nextjs-best-practices

Next.js App Router principles. Server Components, data fetching, routing patterns.

Quality

43%

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-best-practices/SKILL.md

Quality

Content

50%Scale 1-5

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

This skill provides a well-organized reference for Next.js App Router principles using efficient tables and decision trees. Its main weakness is the lack of concrete, executable code examples—it tells Claude what patterns to use but rarely shows implementation. The content reads more like a cheat sheet than an actionable skill guide.

Suggestions

Add executable code examples for key patterns: a server component with fetch + caching options, a server action with validation, and a route handler implementation.

Replace generic best-practice bullets that Claude already knows (e.g., 'Handle errors gracefully') with specific Next.js patterns or code showing how to handle errors in this context.

Consider splitting detailed topics (caching strategy, server actions) into referenced files to keep the main skill as a concise overview with links to deeper content.

Dimension	Reasoning	Score
Conciseness	The content is well-structured with tables and minimal prose. Some sections like 'Best Practices' bullet lists state things Claude already knows (e.g., 'Return proper status codes', 'Handle errors gracefully'), but overall it's efficient and avoids lengthy explanations.	4 / 5
Actionability	The skill provides high-level guidance and categorizations but lacks executable code examples. There are no concrete code snippets showing fetch calls with caching options, server action implementations, or route handler examples. It describes what to do but rarely shows how.	2 / 5
Workflow Clarity	The decision tree for Server vs Client components provides a clear workflow, and the tables organize information well. However, there are no multi-step processes with validation checkpoints. For a principles/reference skill this is acceptable, but the lack of any sequenced workflow with verification steps limits the score.	3 / 5
Progressive Disclosure	The content is well-sectioned with clear headers and tables, making it navigable. However, it's a fairly long single file with no references to supporting documents for deeper topics (like detailed caching strategies or server action patterns), and some sections could benefit from being split out or linked to examples.	3 / 5
	Total	12 / 20 Passed

Description

36%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 identifies the technology domain (Next.js App Router) but reads more like a topic list than a skill description. It lacks concrete actions (no verbs), has no 'Use when...' clause, and uses sentence fragments rather than describing what the skill enables Claude to do.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Guides implementation of Next.js App Router patterns including Server Components, data fetching with async components, nested layouts, and dynamic routing.'

Add an explicit 'Use when...' clause with trigger terms, e.g., 'Use when the user asks about Next.js 13+/14, App Router, Server Components, RSC, route handlers, server actions, or file-based routing with app/ directory.'

Include common synonyms and related terms users might use, such as 'RSC', 'server actions', 'app/ directory', 'layout.tsx', 'page.tsx', 'loading states', 'error boundaries'.

Dimension	Reasoning	Score
Specificity	Names the domain (Next.js App Router) and mentions a few concepts (Server Components, data fetching, routing patterns), but these are high-level topic areas rather than concrete actions. No verbs describe what the skill actually does.	2 / 5
Completeness	Provides a vague 'what' (Next.js App Router principles) but has no 'when' clause at all. There is no explicit trigger guidance for when Claude should select this skill, which per the rubric should cap completeness at 3, and the weak 'what' brings it to 2.	2 / 5
Trigger Term Quality	Includes relevant keywords like 'Next.js', 'App Router', 'Server Components', 'data fetching', and 'routing patterns' that users might mention, but misses common variations like 'RSC', 'server actions', 'layout', 'page.tsx', 'loading.tsx', 'route handlers', or file-based routing.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to Next.js App Router which narrows the domain, but could overlap with general React skills, Next.js Pages Router skills, or generic web framework skills. The lack of concrete actions makes it harder to distinguish from related skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/nextjs-best-practices/SKILL.md
Commit: 57c135b

Reviewed: 3 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.