Tessl • The package manager for agent skills

SkillPublic

next-best-practices

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

1.09x

Quality

68%

Does it follow best practices?

Impact

90%

1.09x

Average score across 3 eval scenarios

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

53%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 exemplary as a lean, well-signaled index, but it is an index to nothing: all 20 referenced bundle files are absent from the skill directory, leaving the skill with no reachable concrete guidance. Either the bundle files must be shipped with the skill, or the most critical rules must be inlined so the skill functions standalone.

Suggestions

Ship the 20 referenced bundle files (file-conventions.md, rsc-boundaries.md, async-patterns.md, etc.) or fix the link paths — as delivered, every reference is a dead link and the skill delivers no content.

Inline the handful of highest-frequency rules (e.g., async params/cookies in Next.js 15+, 'use client' boundaries, next/image over <img>) directly in SKILL.md so the skill is useful even without bundle loads.

Add a short "how to use this skill" note stating the lookup workflow (identify the concern, open the matching reference) so the navigation intent is explicit.

Dimension	Reasoning	Score
Conciseness	The body is a lean index with zero padding and no re-explanation of concepts Claude already knows; every line is either a topic pointer or a terse useful fact like "Middleware rename in v16 (middleware → proxy)" and "Inline scripts need `id`", matching the anchor "every token earns its place".	5 / 5
Actionability	The body contains no code, commands, or executable instruction — every section is "See [x.md](./x.md) for:" plus high-level topic hints ("Async `params` and `searchParams`", "Avoiding data waterfalls"), and the referenced files that should hold the concrete guidance do not exist in the bundle, so no actionable instruction is reachable anywhere.	2 / 5
Workflow Clarity	This is a single-purpose lookup skill ("Apply these rules when writing or reviewing Next.js code") with clear topic grouping, but the rules themselves are unreachable because all referenced files are missing, so the reader can navigate the index yet never complete the intended lookup; structure is present but the essential follow-through is missing.	3 / 5
Progressive Disclosure	The in-body structure is anchor-5 quality — nineteen clearly signaled, one-level-deep references each with a topic summary — but scoring against the actual bundle structure, none of the 20 referenced files (file-conventions.md, rsc-boundaries.md, etc.) exist in references/, scripts/, or alongside SKILL.md, so every link is dead and the disclosure chain is broken end-to-end, landing it below the midpoint.	2 / 5
	Total	12 / 20 Passed

Description

70%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.

A strongly distinctive, well-scoped description with good natural keyword coverage, but it is a topic catalog rather than an action statement and entirely lacks a "Use when..." trigger clause, which caps completeness. Adding an explicit trigger clause (e.g., "Use when writing or reviewing Next.js App Router code") would raise it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when writing or reviewing Next.js code, especially App Router, server components, or data fetching."

Lead with an action verb framing (e.g., "Apply Next.js best practices for...") so the description states what the skill does, not just what it covers.

Include natural synonyms such as "App Router", "server components", and "React" alongside "RSC" to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description enumerates nine concrete sub-areas ("file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling"), which is broad and specific coverage, but they are topic nouns rather than action verbs, so it falls short of the anchor-5 example of multiple concrete actions.	4 / 5
Completeness	The "what" is clear (best-practice guidance across nine named areas) but there is no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3, and it is not lower because the topic list makes the scope unambiguous.	3 / 5
Trigger Term Quality	"Next.js", "best practices", "route handlers", "metadata", "bundling", and "image/font optimization" are terms users would naturally say when needing this skill, but common variations like "App Router", "server components", or "React" are missing and "RSC" leans technical-jargon, matching anchor 4 rather than comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	"Next.js best practices" occupies a clear niche with the specific subtopic list (RSC boundaries, async APIs, route handlers) giving distinct triggers; it is unlikely to fire for any non-Next.js skill, matching the anchor-5 example of a clear niche with minimal conflict risk.	5 / 5
	Total	16 / 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: Voltaire405/coolisimplify
Path: .agents/skills/next-best-practices/SKILL.md
Revision: 036c7de

Reviewed: 8 days ago

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.

next-best-practices

Table of Contents

Is this your skill?