core

Core package for defining schemas, catalogs, and AI prompt generation for json-render. Use when working with @json-render/core, defining schemas, creating catalogs, or building JSON specs for UI/video generation.

Quality

78%

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

Quality

Content

72%

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

The content is highly actionable with strong executable examples, but it reads as a flat API reference rather than a progressive overview — the large exports table and advanced material are inline instead of split into separate reference files, and the few multi-step flows lack explicit validation checkpoints.

Suggestions

Move the dense Key Exports table and advanced sections (SpecStream, StateStore, Validation) into a separate reference file linked from a concise overview, reducing the monolithic wall of API content.

Sequence the autoFixSpec repair loop as an explicit numbered workflow with a validate→fix→retry checkpoint so the lossy/lossless withholding logic is a clear feedback loop.

Trim duplicated explanations — e.g. the two-way binding rule appears in both the Dynamic Prop Expressions bullets and again as a standalone paragraph — to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient reference material, but the large Key Exports table and some duplicated surface area (e.g. dynamic-prop expressions explained twice across sections) could be tightened, keeping it just below fully lean.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript examples for every major API (defineSchema, defineCatalog, createStateStore, validateSpec, buildUserPrompt) with concrete signatures and expected return values.	3 / 3
Workflow Clarity	Sections are organized by topic, but multi-step operations like the autoFixSpec repair loop are described rather than sequenced with explicit validate→fix→retry checkpoints, and no validation steps are surfaced for risky batch/spec-mutation operations.	2 / 3
Progressive Disclosure	Sections are clearly labeled, but the file is a monolithic single-file wall of API reference (~270 lines) with no bundle files and no off-loading of the dense Key Exports / advanced material into separate references.	2 / 3
	Total	9 / 12 Passed

Description

85%

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 is concrete and complete with an explicit 'Use when' clause, covering multiple specific actions and clear triggers. Its only weakness is trigger-term naturalness — the phrasing leans technical rather than echoing what a user would naturally say.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'defining schemas, catalogs, and AI prompt generation for json-render' and 'building JSON specs for UI/video generation' — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what ('Core package for defining schemas, catalogs, and AI prompt generation') and when ('Use when working with @json-render/core, defining schemas, creating catalogs, or building JSON specs').	3 / 3
Trigger Term Quality	Includes relevant triggers like 'defining schemas', 'creating catalogs', 'building JSON specs', '@json-render/core', but they are technical-jargon heavy and lack common user variations, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	Clearly scoped to the json-render/core niche with package-specific triggers, making conflict with other skills unlikely.	3 / 3
	Total	11 / 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/core/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.