CtrlK
BlogDocsLog inGet started
Tessl Logo

nextjs-mastery

Next.js 14+ App Router patterns including RSC, ISR, middleware, parallel routes, and data fetching

64

Quality

76%

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 ./skills/nextjs-mastery/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%

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

The content is highly actionable with executable, copy-paste-ready code and a useful anti-patterns/checklist structure, but it carries minor redundant explanation and is monolithic rather than progressively disclosing detail into separate reference files.

Suggestions

Trim well-known restatements (e.g. the Server Components and Middleware summary sentences) to assume Claude's competence and lift conciseness.

Add an explicit verify/retry checkpoint for the destructive Server Action DB write (e.g. confirm the row exists and surface a structured error before and after `db.user.update`).

For a skill spanning six substantial topics, consider moving deeper material (e.g. full ISR/caching semantics or parallel-route patterns) into reference files referenced one level deep from SKILL.md.

DimensionReasoningScore

Conciseness

The body is largely lean with executable code, but includes a few restatements Claude already knows ("Server Components are the default... send zero JavaScript to the client", "Middleware runs at the edge before every matched request"), fitting anchor 2 leaning toward 3.

2.5 / 3

Actionability

Provides copy-paste-ready, executable TSX/TS throughout (Server Component with `await params`, ISR `revalidate`, middleware with matcher, Server Action with Zod validation), matching the anchor 3 fully-executable example.

3 / 3

Workflow Clarity

Includes a Checklist and Zod input validation before the DB write, but it is a multi-topic patterns catalog rather than a sequenced multi-step workflow, and the DB mutation lacks an explicit verify/retry feedback loop, so it sits between anchors 2 and 3.

2.5 / 3

Progressive Disclosure

Content is well-organized into clear sections and is self-contained with no nested references, but it is a single monolithic file with all six topics inline and no split into reference files, fitting between anchors 2 and 3.

2.5 / 3

Total

10.5

/

12

Passed

Description

70%

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 specific, distinguishable Next.js niche with several concrete sub-topics, but it lacks an explicit "Use when..." trigger clause, which caps completeness and weakens trigger guidance.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or debugging Next.js 14+ App Router apps, or when the user mentions RSC, ISR, middleware, parallel routes, or data fetching."

Prefer natural user-facing terms over jargon (e.g. "Server Components" alongside "RSC", "on-demand revalidation" alongside "ISR") to broaden trigger coverage.

Lead with concrete verbs the skill performs (e.g. "Implements and reviews Next.js 14+ App Router patterns...") to lift specificity from topic labels to performed actions.

DimensionReasoningScore

Specificity

Names a clear domain ("Next.js 14+ App Router patterns") and lists multiple specific sub-areas ("RSC, ISR, middleware, parallel routes, and data fetching"), but these are topic labels rather than concrete performed actions, placing it between anchors 2 and 3.

2.5 / 3

Completeness

It states what the skill covers but has no "Use when..." or equivalent trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural Next.js terms a user would say ("Next.js", "App Router", "middleware", "parallel routes", "data fetching") but mixes in jargon ("RSC", "ISR") and omits common variations like "Server Components" or "Server Actions", fitting anchor 2 leaning toward 3.

2.5 / 3

Distinctiveness Conflict Risk

"Next.js 14+ App Router patterns" is a clear, narrow niche with distinct triggers (App Router, RSC, ISR) unlikely to fire for unrelated skills, matching anchor 3.

3 / 3

Total

10

/

12

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
rohitg00/awesome-claude-code-toolkit
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.