svelte

Svelte 5 renderer for json-render that turns JSON specs into Svelte component trees. Use when working with @json-render/svelte, building Svelte UIs from JSON, creating component catalogs, or rendering AI-generated specs.

Quality

88%

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

77%

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

The body is highly actionable with executable code and a logical section sequence, but it is monolithic and contains minor duplication that could be tightened. Splitting advanced API reference into a separate file would improve progressive disclosure.

Suggestions

Deduplicate the Button.svelte example: show it once in 'Defining Components' and reference the event-binding form only where the 'on' field mapping is introduced.

Move the Context Helpers, Validation, and Streaming UI API reference into a separate REFERENCE.md (or scripts/) and link to it from SKILL.md so the overview stays concise.

Collapse the Providers prose and its table into a single representation to avoid restating each context's purpose twice.

Dimension	Reasoning	Score
Conciseness	Largely lean and code-first with no concept-explaining fluff, but could be tightened: Button.svelte is shown twice (Defining Components and Event System) and the provider contexts are described both inline and in a table.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript/Svelte/JSON examples with imports included (Quick Start, defineCatalog, defineRegistry, getBoundProp, createUIStream), not pseudocode.	3 / 3
Workflow Clarity	As a reference skill it has no destructive multi-step operation requiring validation checkpoints, and sections are clearly sequenced from Quick Start through catalog/component/registry setup to advanced features.	3 / 3
Progressive Disclosure	Well-organized into clear sections, but the ~280-line body is monolithic with all API reference, context helpers, and streaming content inline; no bundle files exist and content that could live in a separate REFERENCE.md is not split out.	2 / 3
	Total	10 / 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.

The description is specific, uses natural trigger terms in third person, and explicitly covers both what the skill does and when to use it. It occupies a clear niche with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'turns JSON specs into Svelte component trees', 'building Svelte UIs from JSON', 'creating component catalogs', 'rendering AI-generated specs' — rather than vague language.	3 / 3
Completeness	Explicitly answers both what ('Svelte 5 renderer for json-render that turns JSON specs into Svelte component trees') and when via an explicit 'Use when working with...' clause.	3 / 3
Trigger Term Quality	Natural phrasings a user would say ('building Svelte UIs from JSON', 'creating component catalogs', 'rendering AI-generated specs', '@json-render/svelte') with good coverage and third-person voice, no jargon-only terms.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to @json-render/svelte and Svelte 5 with distinctive 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/svelte/SKILL.md
Commit: 9d3dfc8

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