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

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/svelte/SKILL.md

Quality

Content

73%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 code-rich, actionable reference with excellent executable examples and good sectioning, but it is a flat monolith with no progressive disclosure into bundle files and lacks an explicit end-to-end workflow with validation checkpoints. Strong on actionability, weaker on workflow sequencing and file structure.

Suggestions

Split dense API-reference material (Context Helpers, Dynamic Props/Two-Way Binding, Streaming UI) into references/ files and link to them from SKILL.md to improve progressive disclosure.

Add a short numbered workflow (define catalog -> author components -> build registry -> render spec -> validate output) so users see the end-to-end sequence with checkpoints.

De-duplicate the Button.svelte emit example that appears in both 'Defining Components' and 'Event System' to tighten the token budget.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code-first reference material that assumes Claude's competence, with only minor over-explanation (e.g., restating the Button.svelte emit example twice across sections), fitting 'efficient; minor instances of over-explanation that could be trimmed'.	4 / 5
Actionability	Multiple copy-paste-ready, executable Svelte/TypeScript examples covering registry definition, component authoring, binding, streaming, and chat UIs, with concrete API signatures and JSON spec samples, matching 'fully executable; copy-paste ready code covering common cases'.	5 / 5
Workflow Clarity	Topics are presented as organized sections but there is no end-to-end sequenced workflow with validation checkpoints; the destructive/batch cap is not the issue here, yet the lack of an explicit build-validate-feedback loop leaves it at 'steps listed but validation gaps; sequence present but checkpoints missing'.	3 / 5
Progressive Disclosure	The skill is a monolithic ~280-line SKILL.md with no bundle files and no offloaded references; while well sectioned, API-reference-grade material (context helpers, streaming, binding) that could live in separate files is inlined, matching 'some structure but could be better organized; content that should be separate is inline'.	3 / 5
	Total	15 / 20 Passed

Description

82%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 explicitly covers both capabilities and concrete trigger conditions with natural user phrasing. Minor gaps in synonym/extension coverage and slight overlap risk with generic Svelte work keep it just below perfect on trigger terms and distinctiveness.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('turns JSON specs into Svelte component trees', 'building Svelte UIs from JSON', 'creating component catalogs', 'rendering AI-generated specs') with only minor gaps in coverage, matching the 'several specific actions; minor gaps' anchor.	4 / 5
Completeness	It explicitly answers both 'what' (Svelte 5 renderer turning JSON specs into component trees) and 'when' ('Use when working with @json-render/svelte, building Svelte UIs from JSON, creating component catalogs, or rendering AI-generated specs') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural user-facing terms ('building Svelte UIs from JSON', 'creating component catalogs', 'rendering AI-generated specs') plus the package name, but lacks synonyms and common variations like file extensions or shorthand phrasing, fitting 'good keyword coverage; a few natural terms missing'.	4 / 5
Distinctiveness Conflict Risk	The Svelte 5 + json-render niche is distinct and trigger-specific, but 'building Svelte UIs from JSON' could minorly overlap with general Svelte skill, fitting 'mostly distinct; minor overlap risk with closely related skills'.	4 / 5
	Total	17 / 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/svelte/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.