CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nextjs-developer

Use when building Next.js 14+ applications with App Router, server components, or server actions. Invoke to configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel. Triggers on: Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured with excellent progressive disclosure and largely executable code examples covering the common Next.js App Router cases. Its main weaknesses are a padded keyword-list section that wastes tokens and code examples with a few undefined placeholders.

Suggestions

Remove the 'Knowledge Reference' keyword list (and trim the persona/attribution footer) — these add tokens without actionable value, directly addressing the lowest-scoring conciseness dimension.

Make the code examples fully self-contained: import or define `db` in the server action example, define `fetchProduct` in the generateMetadata example, and import the `Product` type.

Add a short error-recovery loop to the workflow (e.g., 'if `next build` reports type errors, fix and re-run before deploying') to upgrade workflow clarity.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tight constraints, well-chosen code examples), but the 'Knowledge Reference' section is a pure keyword list ('Next.js 14+, App Router, React Server Components... Turbopack, Vercel deployment') that adds no actionable information Claude doesn't already have, and the persona line plus attribution/footer links add further padding. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4.

3 / 5

Actionability

Three complete, executable TSX examples with file paths plus a concrete validation command ('run `next build` locally... run Lighthouse/PageSpeed to confirm Core Web Vitals > 90') provide mostly copy-paste-ready guidance. Minor gaps keep it below 5: the server action example uses an undefined `db`, the metadata example calls an undefined `fetchProduct`, and the `Product` type import is not shown.

4 / 5

Workflow Clarity

The five-step Core Workflow is clearly sequenced and includes an explicit validation checkpoint ('run `next build` locally, confirm zero type errors, check `NEXT_PUBLIC_*` and server-only env vars... Core Web Vitals > 90'). It falls short of 5 because validation appears only at the final deploy step and there is no error-recovery feedback loop (e.g., what to do when the build fails).

4 / 5

Progressive Disclosure

The Reference Guide table lists five topics, each mapped to a real file (all five verified present in references/) with a 'Load When' condition, exactly one level deep. The SKILL.md body is a genuine overview with key examples inline and bulk detail correctly split into bundle files, matching the top anchor.

5 / 5

Total

16

/

20

Passed

Description

88%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 strong description that explicitly states both capabilities and usage triggers with concrete, natural terminology. Its only weaknesses are a few missing common trigger variations and slight overlap risk on generic terms like 'Vercel'.

DimensionReasoningScore

Specificity

The description lists seven-plus concrete actions ('configure route handlers, implement middleware, set up API routes, add streaming SSR, write generateMetadata for SEO, scaffold loading.tsx/error.tsx boundaries, or deploy to Vercel'), giving comprehensive coverage of the skill's capabilities. It clearly exceeds the 'several specific actions; minor gaps' anchor.

5 / 5

Completeness

It explicitly answers 'when' ('Use when building Next.js 14+ applications with App Router, server components, or server actions' plus a dedicated trigger list) and 'what' (the concrete action list), matching the anchor for clearly and explicitly answering both with concrete trigger phrases.

5 / 5

Trigger Term Quality

The trigger list ('Next.js, Next.js 14, App Router, RSC, use server, Server Components, Server Actions, React Server Components, generateMetadata, loading.tsx, Next.js deployment, Vercel, Next.js performance') includes natural phrasing, synonyms, and file names, but omits a few common terms users would say such as 'SSR', 'SEO', 'middleware', or 'Pages Router'. Good coverage with a few natural terms missing fits the score-4 anchor rather than comprehensive score-5.

4 / 5

Distinctiveness Conflict Risk

The Next.js 14+ App Router focus is a clear niche, but triggers like 'Vercel' and 'React Server Components' create minor overlap risk with closely related Vercel-deployment or React skills. Mostly distinct with minor overlap fits score 4; it does not fully meet 'minimal conflict risk' at 5.

4 / 5

Total

18

/

20

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jeffallan/claude-skills

Path

skills/nextjs-developer/SKILL.md

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.