The description identifies the technology domain (Next.js App Router) and lists a few relevant topic areas, but it reads more like a list of tags than a functional skill description. It lacks concrete actions (verbs), has no 'Use when...' clause, and doesn't clearly differentiate itself from other web framework skills.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Next.js App Router, server components, route handlers, or data fetching in Next.js 13+.'

Replace topic nouns with concrete action phrases, e.g., 'Guides implementation of Server Components, configures nested layouts, sets up data fetching with server actions, and structures App Router routes.'

Include common user-facing trigger terms and file references like 'page.tsx', 'layout.tsx', 'loading.tsx', 'server actions', 'RSC', and 'route groups' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Next.js App Router) and mentions some areas (Server Components, data fetching, routing patterns), but these are broad topic areas rather than concrete actions. No verbs describing what the skill actually does.	2 / 3
Completeness	Loosely describes the 'what' (Next.js App Router principles) but has no 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also weak—listing topics rather than actions—so this scores a 1.	1 / 3
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', or 'route handlers'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'Next.js App Router' specifically is fairly distinctive, but the broad terms 'data fetching' and 'routing patterns' could overlap with general web development or other framework skills. Without explicit scoping, there's moderate conflict risk.	2 / 3
	Total	7 / 12 Passed

Implementation

50%

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

This skill is well-organized and concise, using tables and decision trees effectively to convey Next.js App Router principles. However, it critically lacks executable code examples—there are no actual code snippets showing fetch calls, server actions, route handlers, or component patterns, making it more of a reference cheat sheet than actionable guidance. Adding concrete, copy-paste-ready code for the key patterns would significantly improve its utility.

Suggestions

Add executable code examples for the most important patterns: a server component with fetch + revalidation, a server action with 'use server' and Zod validation, and a route handler with proper error handling.

Include a concrete example of the Server parent + Client child split pattern, since this is a key architectural decision Claude needs to implement correctly.

Add a brief code example for the caching/revalidation patterns (e.g., `fetch(url, { next: { revalidate: 60 } })` and `revalidatePath('/path')`) since these are Next.js-specific APIs that benefit from exact syntax.

Dimension	Reasoning	Score
Conciseness	The content is lean and well-structured using tables and decision trees. It avoids explaining what Next.js is or how React works, assuming Claude's competence. Every section delivers information efficiently without padding.	3 / 3
Actionability	Despite good organization, the content is almost entirely descriptive tables and bullet points with no executable code examples. There are no concrete code snippets showing how to implement fetch with revalidation, server actions, route handlers, or any of the patterns described. It describes rather than instructs.	1 / 3
Workflow Clarity	The decision tree for Server vs Client components provides a clear workflow, and the anti-patterns table gives useful guidance. However, there are no validation checkpoints or sequenced multi-step processes for common tasks like setting up data fetching, creating server actions, or implementing caching strategies.	2 / 3
Progressive Disclosure	The content is well-organized into numbered sections with clear headers and tables, making it easy to scan. However, for a skill this long (~150+ lines), some sections like API Routes or Caching Strategy could benefit from linking to separate detailed files rather than being inline, and there are no references to external resources.	2 / 3
	Total	8 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Reviewed

1 day ago

Table of Contents

Discovery Implementation Validation