shadcn-svelte

Pre-built shadcn-svelte components for json-render Svelte apps. Use when working with @json-render/shadcn-svelte, adding standard UI components to a Svelte catalog, or building Svelte web UIs with shadcn-svelte + Tailwind CSS components.

Quality

83%

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

78%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.

The body is highly actionable and concise with executable code and a tidy reference layout. Its main weakness is progressive disclosure: the entire 36-component prop catalog lives inline with no separate reference file to split it out.

Suggestions

Move the full Available Components prop reference into a references/ file (e.g. components.md) and keep SKILL.md as an overview with a one-level-deep pointer to it.

Add a brief verification checkpoint in the Usage Pattern (e.g. confirming the registry renders a sample component) so the integration workflow has an explicit success signal.

Trim the inline component prop table to the most-used subset in SKILL.md, linking to the reference for the complete list.

Dimension	Reasoning	Score
Conciseness	The body is efficient and reference-style with minimal padding — no explanations of Svelte/Tailwind concepts — though the full 36-component prop table could arguably be split out to reduce inline bulk.	4 / 5
Actionability	Provides copy-paste-ready TypeScript catalog and registry code plus a Svelte rendering example, and concrete per-component prop signatures covering the common integration cases.	5 / 5
Workflow Clarity	The pick-definitions → build-registry → render sequence is clear and unambiguous for this simple, non-destructive integration skill, with only minor gaps in explicit verification steps.	4 / 5
Progressive Disclosure	Content is well-organized into labeled sections, but the full component prop reference is inlined monolithically with no bundle files or external references to offload it.	3 / 5
	Total	16 / 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.

The description is strong: it explicitly answers both what the skill does and when to use it, with a precise package handle and natural trigger phrases that make it highly distinct. Minor room to add synonyms (e.g. 'UI library') and more distinct action verbs.

Dimension	Reasoning	Score
Specificity	Names the domain ('Pre-built shadcn-svelte components') and several concrete actions ('adding standard UI components to a Svelte catalog', 'building Svelte web UIs'), but the verbs are somewhat generic rather than distinct operations.	4 / 5
Completeness	Clearly states what it does ('Pre-built shadcn-svelte components for json-render Svelte apps') and gives an explicit 'Use when...' clause with multiple concrete trigger phrases, matching the canonical both-answered pattern.	5 / 5
Trigger Term Quality	Good natural keyword coverage including 'shadcn-svelte', 'Svelte catalog', 'Svelte web UIs', 'Tailwind CSS components', and the precise package handle '@json-render/shadcn-svelte', though a few synonyms like 'UI library' are missing.	4 / 5
Distinctiveness Conflict Risk	Tied to a specific package ecosystem with the precise handle '@json-render/shadcn-svelte', giving it a clear niche with minimal overlap risk against unrelated skills.	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/shadcn-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.