shadcn

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

Quality

91%

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.

Executable, well-structured guidance with copy-paste code and a clear catalog-to-registry workflow. The main gap is progressive disclosure: the large inline component reference would benefit from being split into a bundled reference file.

Suggestions

Move the 'Available Components' catalog into a bundled reference file (e.g. references/components.md) and keep SKILL.md as an overview with a one-level-deep link, improving progressive_disclosure.

Trim the 'Important Notes' restatements (e.g. the /catalog no-React-dependency point already shown in the Two Entry Points table) to reduce redundancy.

If splitting out the component catalog, add a brief navigation line such as '**Full component reference**: See [components.md](references/components.md)' so the reference is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The prose is lean, assumes Claude's competence (no explanations of what Radix/Tailwind are), and the sectioned component catalog earns its place as reference material; only minor restatement in 'Important Notes'.	3 / 3
Actionability	Provides copy-paste-ready TypeScript for both the catalog/registry usage pattern and custom-component extension, plus concrete props for all 36 components.	3 / 3
Workflow Clarity	The single core task is unambiguous with a clear two-step sequence (defineCatalog then defineRegistry); no destructive/batch operations require validation checkpoints, so the simple-skill guidance applies.	3 / 3
Progressive Disclosure	Sections are well organized, but the full 36-component reference catalog is kept inline in SKILL.md with no bundle files to offload it, matching the level-2 anchor of API/reference content that could live in a separate file.	2 / 3
	Total	11 / 12 Passed

Description

90%

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 tight, third-person description that clearly states both purpose and trigger conditions with strong natural keywords. Its only weakness is that the named actions ('adding to a catalog', 'building web UIs') are somewhat general rather than enumerating concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Pre-built shadcn/ui components for json-render') and a couple of actions ('adding standard UI components to a catalog', 'building web UIs'), but the actions are general rather than the multiple concrete operations (e.g. extract/fill/merge) the level-3 anchor requires.	2 / 3
Completeness	Explicitly answers both what ('Pre-built shadcn/ui components for json-render') and when ('Use when working with @json-render/shadcn, adding standard UI components to a catalog, or building web UIs...').	3 / 3
Trigger Term Quality	Natural terms a user would say are well covered: 'shadcn/ui components', '@json-render/shadcn', 'Radix UI + Tailwind CSS', 'standard UI components', 'catalog'.	3 / 3
Distinctiveness Conflict Risk	The '@json-render/shadcn' niche with Radix UI + Tailwind triggers is highly specific and unlikely to fire for unrelated skills.	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/shadcn/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.