next-best-practices

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

Quality

61%

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

Quality

Content

61%Weight 40%Scale 1-5

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

The body is a model of lean progressive-disclosure structure, but it functions only as a navigation index: all referenced detail files are absent, so it offers no executable guidance and the workflow cannot actually be carried out. Token efficiency is excellent; actionability is the main weakness.

Suggestions

Ship the 19 referenced bundle files (file-conventions.md, rsc-boundaries.md, async-patterns.md, etc.) so the 'See [file]' pointers resolve and the skill delivers executable guidance.

Add at least one inline runnable example or concrete rule per high-value section (e.g. an async params snippet, a next/image sizes example) so the skill is actionable even before a file is opened.

For review workflows, add a short validation/checklist step (e.g. 'verify RSC boundary, async API usage, and image optimization before approving') to give the workflow explicit checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is a lean topic-index of short headers and bullet lists with no concept over-explanation, assuming Claude's competence; nearly every token earns its place.	5 / 5
Actionability	No code, commands, or executable steps appear — only topic lists pointing to per-area files, and all 19 referenced files are absent from the bundle, so the concrete guidance needed to execute is missing.	2 / 5
Workflow Clarity	The apply-when context is stated ('Apply these rules when writing or reviewing Next.js code') but there is no multi-step sequence or checkpoints, and the actual rules are delegated to files that do not exist, leaving execution gaps.	3 / 5
Progressive Disclosure	Structure is exemplary — a clean overview with well-signaled, one-level-deep references organized by topic — but every referenced file is missing from the bundle, so the disclosure is signaled but not actually realized.	4 / 5
	Total	14 / 20 Passed

Description

61%Weight 40%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 gives a specific, well-scoped map of Next.js capability areas with good natural keywords, but it omits any explicit 'when to use' trigger guidance, which caps completeness and slightly weakens distinctiveness. It reads as a topic catalog rather than a statement of concrete actions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when writing or reviewing Next.js (App Router) code, or when the user mentions RSC, route handlers, next/image, or Next.js data fetching.'

Reframe the area list as concrete actions (e.g. 'Detect invalid RSC boundaries, apply async params/cookies patterns, optimize images with next/image') to lift specificity from noun-listing to action-stating.

Include natural synonyms and file/extension cues (App Router, .tsx, page.tsx, layout.tsx, Server Actions) to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete Next.js sub-areas (RSC boundaries, async APIs, route handlers, image/font optimization, bundling) giving broad coverage, but they are noun-areas rather than action verbs, so it sits at 'names domain and concrete capabilities' rather than 'lists specific actions'.	3 / 5
Completeness	The 'what' is clear (Next.js best practices across the listed areas) but there is no 'Use when...' or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural Next.js terms a developer would say are present (Next.js, RSC, route handlers, metadata, bundling), but common synonyms/extensions like App Router, .tsx, or pages are missing, matching 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to a Next.js niche with distinct sub-topics, but without explicit trigger phrasing there is minor overlap risk with a generic React or web best-practices skill.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 19 missing	Warning

	Total	15 / 16 Passed

Repository: openstatusHQ/data-table-filters
Path: .agents/skills/next-best-practices/SKILL.md
Commit: fe1bcc5

Reviewed: ~24 hours 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.