CtrlK
BlogDocsLog inGet started
Tessl Logo

nextjs-best-practices

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

47

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/nextjs-best-practices/SKILL.md

The canonical home for this skill is nextjs-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

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 well-organized, token-efficient reference of Next.js App Router best practices, but it stays at the principles level: no executable code examples and no sequenced workflow with validation checkpoints. It works as a quick reference but would be stronger with concrete code snippets.

Suggestions

Add small executable code snippets for the highest-value patterns (e.g. a Server Component fetch with revalidate, a 'use server' action, generateMetadata) to lift actionability.

Replace the filler closing line "This skill is applicable to execute the workflow or actions described in the overview." with a concrete trigger/"Use when" statement.

For mutation/caching sections, show a brief validate-then-revalidate sequence so the workflow_clarity dimension has an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is lean: tables and bullet lists with no padded explanations of what Next.js is, though the closing "This skill is applicable to execute the workflow..." line and a couple of redundant tables could be trimmed.

4 / 5

Actionability

It names concrete artifacts and APIs (page.tsx, layout.tsx, revalidatePath/Tag, generateMetadata, next/image) but provides no executable code examples, leaving guidance at the high-level "principles" tier rather than copy-paste ready.

3 / 5

Workflow Clarity

Content is organized into ten clear topical sections, but this is a reference/principles doc with no sequenced multi-step workflow or validation checkpoints; the section-1 decision tree is the only flow-like element.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is self-contained with well-signaled numbered section headers and tables, giving easy navigation; it is somewhat long for a single-file overview but appropriately structured with no nested references.

4 / 5

Total

14

/

20

Passed

Description

40%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 names a clear domain and a few relevant keywords but is vague on concrete actions and entirely missing a "Use when" trigger clause, capping its completeness. It is concise and distinct but not actionable enough for confident auto-triggering.

Suggestions

Replace "principles" with concrete actions, e.g. "Structure App Router routes, choose Server vs Client Components, and configure data fetching and caching."

Add an explicit trigger clause such as "Use when building or refactoring Next.js App Router apps, or when the user mentions RSC, Server Components, route handlers, or Next.js data fetching."

Include natural synonyms users say (React Server Components, RSC, App Router, route handlers) to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Next.js App Router principles") and lists topics ("Server Components, data fetching, routing patterns") but uses no concrete verbs/actions, so it only minimally describes capabilities.

2 / 5

Completeness

The "what" is vague ("principles") and there is no "Use when..." clause giving explicit trigger guidance, matching the vague-what-and-no-when anchor.

2 / 5

Trigger Term Quality

It includes several relevant natural terms ("Next.js App Router", "Server Components", "data fetching", "routing patterns") but misses common synonyms/variations such as React, RSC, or file-convention triggers.

3 / 5

Distinctiveness Conflict Risk

"Next.js App Router principles" carves a fairly distinct niche with only minor overlap risk against a generic React or frontend skill.

4 / 5

Total

11

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.