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

79%

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

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.

A well-organized, largely executable SKILL.md with a solid quick-start sequence and terse concept coverage. Main weaknesses are the missing registry/handlers setup that examples depend on, no verification step in the workflow, and an inlined API reference that belongs in a separate bundle file.

Suggestions

Add a brief step or snippet showing how to create lib/registry.ts (registry and handlers) that the layout.tsx example imports, and define or import getPost in the loaders example so Quick Start is fully copy-paste runnable.

Deduplicate the loaders example between Quick Start and the Data Loaders section, and consolidate the Slot requirement stated in both Key Concepts and the Layouts section.

Move the full API Reference section into a references/api.md file and link to it, keeping SKILL.md as an overview with the Quick Start and Key Concepts.

Dimension	Reasoning	Score
Conciseness	Generally lean with a realistic Quick Start and terse Key Concepts bullets, but the Data Loaders section repeats near-identical loaders code from Quick Start and the Layouts section restates the Key Concepts bullet, so not every token earns its place (anchor 4, not 5).	4 / 5
Actionability	Mostly executable guidance with typed spec, createNextApp wiring, and route-file exports, but examples aren't self-contained: getPost is undefined and the layout imports registry/handlers from @/lib/registry which is never shown. Anchor 4 rather than fully copy-paste-ready anchor 5.	4 / 5
Workflow Clarity	The numbered Quick Start (define spec -> create app -> wire route files) is a clear, correctly ordered sequence, but there is no verification step (e.g., run next dev and check routes render), leaving a minor validation gap at anchor 4.	4 / 5
Progressive Disclosure	No bundle files exist and the single ~190-line body inlines a full API Reference section plus SSR and Key Concepts detail that would fit a separate reference file; structure is present with clear headers, but content that should be separate is inline (anchor 3, below anchor 4).	3 / 5
	Total	15 / 20 Passed

Description

87%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: third person, concise, concrete about capabilities, with an explicit and specific 'Use when...' clause covering natural trigger phrases. Only minor gaps in capability coverage and synonym variety.

Dimension	Reasoning	Score
Specificity	Enumerates concrete capabilities ("turns JSON specs into full Next.js applications with routes, layouts, SSR, and metadata") but omits other surfaced features like data loaders and dynamic routes, matching 'several specific actions; minor gaps' rather than comprehensive anchor 5.	4 / 5
Completeness	Explicitly answers both what ("renderer... that turns JSON specs into full Next.js applications") and when ("Use when working with..." with three concrete trigger phrases), matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	Good natural keyword coverage ("working with @json-render/next", "building Next.js apps from JSON specs", "AI-generated multi-page applications") but misses common synonyms like SSR app or React-from-spec phrasing, so below the comprehensive-synonyms anchor 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche (json-render's Next.js renderer) anchored by a unique package name trigger, so minimal conflict risk with other skills; generic Next.js phrasing is a negligible overlap.	5 / 5
	Total	18 / 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: c2600d7

Reviewed: 1 day 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.