nextjs-best-practices

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

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.agent/skills/nextjs-best-practices/SKILL.md

Quality

Discovery

32%

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 description identifies the technology domain but reads more like a topic list than a functional skill description. It lacks concrete actions (what Claude will do) and completely omits trigger guidance (when to use it). The brevity hurts rather than helps since it sacrifices necessary detail.

Suggestions

Add a 'Use when...' clause specifying triggers like 'building Next.js apps', 'App Router questions', 'server component issues', or 'Next.js 13/14 routing'.

Convert topic nouns into action verbs: instead of 'Server Components, data fetching', write 'Implement Server Components, configure data fetching strategies, set up nested layouts'.

Include common user terms and file references like 'page.tsx', 'layout.tsx', 'loading.tsx', 'RSC', 'use server', 'use client' to improve trigger matching.

Dimension	Reasoning	Score
Specificity	Names the domain (Next.js App Router) and mentions some capabilities (Server Components, data fetching, routing patterns), but these are high-level concepts rather than concrete actions like 'create routes' or 'implement server-side data fetching'.	2 / 3
Completeness	Only addresses 'what' at a high level with no 'Use when...' clause or explicit trigger guidance. Missing any indication of when Claude should select this skill over others.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Next.js', 'App Router', 'Server Components', 'routing' that users might mention, but missing common variations like 'RSC', 'React Server Components', 'page.tsx', 'layout.tsx', or 'Next 13/14'.	2 / 3
Distinctiveness Conflict Risk	The 'Next.js App Router' focus provides some distinction from general React or web development skills, but 'routing patterns' and 'data fetching' are generic enough to potentially overlap with other framework skills.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

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

This skill excels at conciseness and organization, presenting Next.js App Router concepts in a highly scannable format with tables and decision trees. However, it reads more as a reference card than an actionable skill - it tells Claude what patterns exist but doesn't provide executable code examples to demonstrate implementation. Adding concrete code snippets would significantly improve actionability.

Suggestions

Add executable code examples for key patterns: a Server Component with fetch(), a Client Component with useState, and a Server Action with form handling

Include a concrete route handler example showing request validation with Zod and proper error handling

Add a step-by-step workflow for common tasks like 'adding a new authenticated route' with validation checkpoints

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables, decision trees, and minimal prose. No unnecessary explanations of concepts Claude already knows - just actionable patterns and conventions.	3 / 3
Actionability	Provides clear patterns and conventions but lacks executable code examples. Tables describe what to do but don't show concrete implementations - e.g., no actual fetch() calls, no Server Action code, no route handler examples.	2 / 3
Workflow Clarity	The decision tree for Server vs Client is clear, but multi-step processes like data fetching or form handling lack explicit sequences. No validation checkpoints for common workflows like API route creation or Server Action implementation.	2 / 3
Progressive Disclosure	Well-organized with clear sections and logical grouping. For a reference-style skill of this scope, the structure is appropriate - numbered sections, tables for quick lookup, and a clear hierarchy without needing external file references.	3 / 3
	Total	10 / 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

Repository: lchenrique/politron-ide
Commit: 7114206

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