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

96%

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

92%

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

Highly actionable and concise body with complete executable examples and a clear usage sequence. The main weakness is progressive disclosure: the large inline component catalog could be offloaded to a reference file with the SKILL.md acting as an overview.

Suggestions

Move the 'Available Components' reference (36 components with props) into a separate COMPONENTS.md and link to it from a brief overview section, keeping SKILL.md focused on the entry points, usage pattern, and key notes.

Add clearly signaled one-level-deep references (e.g. 'See [COMPONENTS.md](COMPONENTS.md) for the full prop reference') so navigation is explicit rather than a single monolithic document.

Consider splitting the 'Validation Timing' and 'Important Notes' detail into the reference file as well, leaving only the essential getting-started workflow inline.

Dimension	Reasoning	Score
Conciseness	The body is lean per-line — terse one-line component descriptions and two complete code examples — and avoids explaining concepts Claude already knows (no 'what is Svelte/Tailwind' padding).	3 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript catalog/registry setup and a Svelte render component, plus specific import paths and an explicit 'do not spread all definitions' instruction.	3 / 3
Workflow Clarity	The catalog → registry → render sequence is shown unambiguously with matching keys, and the Two Entry Points table clarifies usage; no destructive/batch operations require validation checkpoints, so the simple-skill clause applies.	3 / 3
Progressive Disclosure	Sections are well-organized, but the full 36-component reference is inline content that could be split into a separate file, and no external references exist to provide one-level-deep navigation.	2 / 3
	Total	11 / 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.

A strong, well-scoped description that concisely states both what the skill provides and when to use it with natural trigger terms. No vague fluff or over-claims; third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions such as 'adding standard UI components to a Svelte catalog' and 'building Svelte web UIs with shadcn-svelte + Tailwind CSS components', matching the multiple-specific-actions anchor.	3 / 3
Completeness	Explicitly states what it provides ('Pre-built shadcn-svelte components for json-render Svelte apps') and includes an explicit 'Use when ...' trigger clause answering when to invoke it.	3 / 3
Trigger Term Quality	Uses natural terms a user would say — 'shadcn-svelte', 'Svelte web UIs', 'UI components', 'Tailwind CSS components' — with good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to '@json-render/shadcn-svelte' and Svelte catalog/UI scenarios, giving it a clear niche unlikely to trigger 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/shadcn-svelte/SKILL.md
Commit: 9d3dfc8

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