nextjs-expert

Next.js expert for App Router, SSR/SSG, API routes, middleware, and deployment

Quality

57%

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 ./crates/openfang-skills/bundled/nextjs-expert/SKILL.md

Quality

Content

57%

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-organized and technically accurate with a clean section structure, but it lacks any executable code examples and presents inherently multi-step tasks as topical bullets rather than sequenced workflows with validation checkpoints.

Suggestions

Add short executable code snippets for the highest-value techniques (a Server Component data fetch, a Route Handler, middleware with a matcher, ISR revalidate usage) to lift actionability toward 3.

Replace the marketing-style intro ('seasoned Next.js architect with deep expertise...') with a one-line purpose statement to remove filler.

For multi-step tasks like deployment or ISR setup, provide a brief numbered sequence with a validation/verification checkpoint (e.g. 'verify the route statically generated via build output').

Dimension	Reasoning	Score
Conciseness	The Principles, Techniques, and Pitfalls bullets are reasonably dense and assume Claude's Next.js knowledge, but the intro paragraph is padded with marketing language ('seasoned Next.js architect with deep expertise,' 'This skill provides guidance on...') that could be cut.	2 / 3
Actionability	The body names specific, correct file conventions and APIs (app/[segment]/page.tsx, route.ts, middleware.ts, generateStaticParams, revalidatePath/revalidateTag, next/image), but it contains no executable code examples at all, leaving guidance concrete yet incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	Content is organized into clear topical categories (Principles, Techniques, Patterns, Pitfalls) but offers no sequenced multi-step procedures or validation checkpoints for inherently multi-step tasks like deployment, ISR setup, or middleware configuration.	2 / 3
Progressive Disclosure	The body is a concise (~35 lines), self-contained overview with no bundle files and no nested references, and it is cleanly sectioned, meeting the rubric's carve-out for short skills with no need for external references.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 has a clear, distinctive Next.js niche and reasonable trigger terms, but it lists capability areas rather than concrete actions and lacks any explicit 'Use when...' trigger guidance, capping both specificity and completeness at 2.

Suggestions

Reword capability areas as concrete actions, e.g. 'Build App Router routes, configure SSR/SSG/ISR, implement API routes and middleware, and deploy Next.js apps.'

Add an explicit 'Use when...' clause, e.g. 'Use when building or debugging Next.js 14+ apps using the App Router, Server Components, or API routes.'

Include common natural variations users would say, such as 'React,' 'Server Components,' 'SSG,' and 'ISR,' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the Next.js domain and several capability areas (App Router, SSR/SSG, API routes, middleware, deployment), but these are feature areas/topics rather than concrete enumerated actions like 'build,' 'deploy,' or 'configure,' placing it at 'names domain and some actions, but not comprehensive.'	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance for when Claude should use it, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Terms like 'Next.js,' 'App Router,' 'SSR/SSG,' 'API routes,' and 'middleware' are natural keywords users would say, but common variations such as 'React,' 'Server Components,' 'SSG,' and 'ISR' are missing, so coverage is partial rather than complete.	2 / 3
Distinctiveness Conflict Risk	'Next.js expert' scoped to App Router, SSR/SSG, API routes, and middleware defines a clear, narrow niche with distinctive triggers unlikely to match unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: RightNow-AI/openfang
Path: crates/openfang-skills/bundled/nextjs-expert/SKILL.md
Commit: acf2587

Reviewed: about 8 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.