next-best-practices

Name: next-best-practices
Rating: 65 (1 reviews)
Author: vercel-labs

tessl i github:vercel-labs/next-skills --skill next-best-practices

github.com/vercel-labs/next-skills

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Review Score

65%

Validation Score

10/16

Implementation Score

73%

Activation Score

43%

SKILL.md

Review

Evals

Generated

13 days ago

Warnings & errors only

Criteria	Score
description_trigger_hint	Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...')
metadata_version	'metadata' field is not a dictionary
license_field	'license' field is missing
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata
body_examples	No examples detected (no code fences and no 'Example' wording)
body_steps	No step-by-step structure detected (no ordered list); consider adding a simple workflow

Overall Assessment

This skill excels as a well-organized index/navigation hub for Next.js best practices, with excellent progressive disclosure and token efficiency. However, it functions purely as a table of contents with no actionable content in the main file itself - all concrete guidance is delegated to referenced files, which limits its standalone utility.

Suggestions

Add a 'Quick Reference' section at the top with 2-3 most common patterns as executable code snippets (e.g., basic RSC boundary, async params usage)
Include a brief workflow section indicating the order to check these practices when reviewing/writing Next.js code (e.g., 'Start with RSC boundaries, then check async patterns, then...')

Dimension	Score	Reasoning
Conciseness	3/3	Extremely lean and efficient. No unnecessary explanations of what Next.js is or how React works. Every line points to specific, actionable content without padding.
Actionability	2/3	The skill itself is a navigation hub with no executable code or concrete examples - all actionable content is delegated to referenced files. While the references are well-organized, the main file provides no copy-paste ready guidance.
Workflow Clarity	2/3	Sections are logically organized by topic, but there's no sequencing guidance for when to apply which practices, no validation checkpoints, and no workflow for debugging or implementing these patterns in order.
Progressive Disclosure	3/3	Excellent progressive disclosure with clear one-level-deep references. Each section provides a brief context hint (what's covered) before linking to detailed files. Navigation is intuitive and well-signaled.

Overall Assessment

The description effectively lists specific Next.js capabilities and technical areas, demonstrating good domain knowledge. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill over others. The description reads more like a feature list than a selection guide.

Suggestions

Add a 'Use when...' clause specifying triggers like 'when the user asks about Next.js projects, App Router, React Server Components, or Next.js-specific patterns'
Expand trigger terms to include common variations: 'React Server Components' (not just RSC), 'App Router', 'pages directory', 'next.config.js'
Clarify the scope to distinguish from general React skills, e.g., 'Next.js-specific patterns distinct from vanilla React'

Dimension	Score	Reasoning
Specificity	3/3	Lists multiple specific concrete actions and concepts: file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling. These are concrete, actionable areas within Next.js development.
Completeness	1/3	Describes what the skill covers (Next.js best practices across various areas) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.
Trigger Term Quality	2/3	Includes 'Next.js' as a strong trigger term and technical terms like 'RSC', 'route handlers', 'metadata' that developers would use. However, missing common variations like 'React Server Components' spelled out, 'App Router', 'pages router', or file extensions like '.tsx'.
Distinctiveness Conflict Risk	2/3	The 'Next.js' focus provides some distinctiveness, but terms like 'data patterns', 'error handling', and 'bundling' are generic enough to potentially overlap with general React, JavaScript, or web development skills.