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

82%

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

Quality

Content

65%

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

A solid, actionable reference with executable examples and a clear setup sequence, but it is a single monolithic document with some redundancy and no progressive disclosure into separate reference files, and the setup workflow lacks validation checkpoints.

Suggestions

Split the full API reference and the large spec example into separate reference files (e.g. REFERENCE.md, SPEC_EXAMPLE.md) and link to them from the body to improve progressive disclosure and conciseness.

Remove the duplicate data-loader example — show it once, either in the Quick Start or in the Data Loaders section, not both.

Add a verification step to the Quick Start workflow, such as running `npm run dev` and confirming the routes render, to give the setup sequence an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	Mostly concrete reference material with little general-concept padding, but the data-loader example appears twice and the inline ~40-line spec example plus full API reference could be tightened or split out.	2 / 3
Actionability	Quick Start provides a complete executable flow — install command, full TypeScript spec, createNextApp usage, and route file wiring — that is copy-paste ready, and the API reference lists specific signatures and params.	3 / 3
Workflow Clarity	The numbered Quick Start (1. Define Spec, 2. Create App, 3. Wire Up Route Files) gives a clear sequence, but there are no validation or verification checkpoints, so it sits below the top anchor.	2 / 3
Progressive Disclosure	Sections are well-organized, but everything is inline in one ~195-line file with no external references; the large spec example and full API reference are candidates for separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

100%

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: third-person voice, concrete capability list, explicit "Use when" triggers, and a clear niche tied to a named package. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — "turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata" — naming specific features rather than vague actions.	3 / 3
Completeness	Explicitly answers both what (renderer that turns JSON specs into Next.js apps) and when via a clear "Use when..." clause listing three trigger scenarios.	3 / 3
Trigger Term Quality	Includes natural phrases a user would say — "building Next.js apps from JSON specs", "creating AI-generated multi-page applications" — alongside the package name, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Tied to the specific @json-render/next package and json-render ecosystem with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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: vercel-labs/json-render
Path: skills/next/SKILL.md
Commit: 9d3dfc8

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