Next.js renderer for json-render that turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata. Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications.

Quality

75%

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 ./skills/next/SKILL.md

Quality

Content

57%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 and offers executable Quick Start code, but it over-explains familiar Next.js concepts, lacks verification checkpoints in its setup workflow, and inlines ~190 lines that would benefit from being split into reference files.

Suggestions

Move the full Server/Client API reference and the large spec example into separate reference files (e.g. REFERENCE.md, EXAMPLES.md) and link to them from SKILL.md to improve progressive disclosure.

Trim the Route Patterns and SSR sections to drop explanations of Next.js URL conventions and server-rendering basics that Claude already knows.

Add a verification step to the Quick Start (e.g. run `next build` or `next dev` and confirm the routes resolve) so the setup workflow has an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and library-specific, but the Route Patterns and SSR sections re-explain Next.js URL conventions and server-rendering basics Claude already knows, and the ~190-line body could be tightened.	3 / 5
Actionability	The Quick Start provides complete, copy-paste TypeScript (spec, createNextApp, route wiring) and built-in actions list explicit params, but the API reference gives prose descriptions rather than full signatures for every export.	4 / 5
Workflow Clarity	Quick Start is a clear numbered sequence (Define spec → Create app → Wire up routes), but there are no validation or verify checkpoints, fitting the score-3 anchor of steps-listed-with-validation-gaps.	3 / 5
Progressive Disclosure	Sections are well-organized, but at ~190 lines the full API reference and detailed spec example are inlined in SKILL.md with no split into reference files; the under-50-line exception does not apply.	3 / 5
	Total	13 / 20 Passed

Description

92%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, third-person description that concisely states both capability and explicit use-when triggers tied to a specific package. The only minor gap is trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete outputs — 'routes, layouts, SSR, and metadata' — constituting comprehensive coverage of what the renderer produces, matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what ('turns JSON specs into full Next.js applications...') and when ('Use when working with @json-render/next, building Next.js apps from JSON specs, or creating AI-generated multi-page applications') with concrete triggers.	5 / 5
Trigger Term Quality	Natural phrases like 'building Next.js apps from JSON specs', '@json-render/next', and 'AI-generated multi-page applications' give good keyword coverage, though a few synonyms/variations are absent.	4 / 5
Distinctiveness Conflict Risk	Tightly scoped to the @json-render/next package and JSON-spec-to-Next.js niche, giving a clear trigger surface with minimal overlap risk.	5 / 5
	Total	19 / 20 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: vercel-labs/json-render
Path: skills/next/SKILL.md
Commit: 0f6798b

Reviewed: 2 days 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.