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

77%

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

Quality

Discovery

89%

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 is a solid skill description that clearly identifies its domain (Next.js) and provides explicit 'Use when' guidance with relevant trigger terms. The main weakness is that it lists feature areas rather than concrete actions - it tells you what Next.js concepts it covers but not specific tasks it can help accomplish (e.g., 'create API routes', 'configure middleware', 'set up ISR').

Suggestions

Replace feature categories with concrete action verbs: instead of 'working with server components', say 'create and optimize server components, implement streaming, configure caching strategies'

Add specific file/configuration triggers: '.next', 'next.config.js', 'page.tsx', 'layout.tsx' to improve matching on file-based queries

Dimension	Reasoning	Score
Specificity	Names the domain (Next.js) and lists several features (server-side rendering, static generation, App Router, server components, data fetching, routing, performance optimization), but these are more feature categories than concrete actions. Missing specific verbs like 'create routes', 'configure SSR', 'implement caching'.	2 / 3
Completeness	Clearly answers both what ('Guide for implementing Next.js - a React framework for production with server-side rendering, static generation, and modern web features') and when ('Use when building Next.js applications, implementing App Router, working with server components, data fetching, routing, or optimizing performance').	3 / 3
Trigger Term Quality	Good coverage of natural terms users would say: 'Next.js', 'App Router', 'server components', 'data fetching', 'routing', 'performance', 'server-side rendering', 'static generation'. These are terms developers naturally use when working with Next.js.	3 / 3
Distinctiveness Conflict Risk	Clear niche focused specifically on Next.js with distinct triggers like 'App Router', 'server components', and 'Next.js' itself. Unlikely to conflict with generic React skills or other framework skills due to Next.js-specific terminology.	3 / 3
	Total	11 / 12 Passed

Implementation

64%

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

This is a comprehensive Next.js reference with excellent actionable code examples covering the full framework. Its main weaknesses are verbosity (could trim explanatory content Claude already knows) and monolithic structure (would benefit from splitting into focused sub-documents). The workflow guidance lacks explicit validation steps for multi-step processes like deployment.

Suggestions

Remove introductory explanations Claude already knows (e.g., 'Next.js is a React framework...', basic concept definitions) to improve token efficiency

Split into focused sub-documents (ROUTING.md, DATA_FETCHING.md, DEPLOYMENT.md) with SKILL.md as a quick-start overview pointing to detailed guides

Add explicit validation checkpoints to multi-step workflows, especially deployment (e.g., 'Run `npm run build` and verify no errors before proceeding to deployment')

Add a troubleshooting feedback loop: 'If hydration error occurs → check X → fix Y → rebuild → verify'

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes explanations Claude already knows (e.g., 'Next.js is a React framework for building full-stack web applications'). Some sections like 'Core Concepts' explain basic architectural principles that could be trimmed. However, most code examples are lean and useful.	2 / 3
Actionability	Excellent executable code examples throughout - installation commands, complete component code, configuration files, and deployment steps are all copy-paste ready. Every major concept includes working code snippets with proper TypeScript types.	3 / 3
Workflow Clarity	While the skill covers many topics, multi-step processes lack explicit validation checkpoints. The deployment section lists steps but doesn't include verification (e.g., 'verify build succeeded before deploying'). The implementation checklist at the end is helpful but lacks feedback loops for error recovery.	2 / 3
Progressive Disclosure	The skill is a monolithic document (~700 lines) that could benefit from splitting into separate files (routing.md, data-fetching.md, deployment.md). The reference to external docs (https://nextjs.org/docs/llms.txt) is good, but internal content organization is flat rather than hierarchical.	2 / 3
	Total	9 / 12 Passed

Validation

81%

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

Repository: einverne/dotfiles
Commit: b1b2fe0

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