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

80%

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

82%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 a tight, well-structured reference with executable examples and clear entry-point guidance, avoiding padding and assuming Claude's knowledge. Its main limitation is the full component inventory living inline rather than in a separate reference file, which slightly dilutes both conciseness and progressive disclosure.

Suggestions

Move the full per-component prop list (the 'Available Components' section) into a references/ file and keep only the most-used components inline, linking out for the rest.

Add a short explicit verification note (e.g., confirm each catalog component has a matching registry implementation before rendering) to strengthen workflow checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, using tables and terse component summaries instead of explaining what Radix/Tailwind are; the long component-by-component list could be trimmed slightly but earns its place as reference.	4 / 5
Actionability	Two complete, copy-paste-ready TypeScript examples (catalog + registry, and custom-component extension) cover the common cases, and inline notes like 'Do not spread all definitions -- explicitly select' give executable guidance.	5 / 5
Workflow Clarity	The two-entry-point pattern and catalog-then-registry sequence are clear with implicit checkpoints (matching registry entries to catalog picks), but there are no explicit validation steps; this is not a destructive/batch skill so the 3-cap does not apply.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (entry points, usage, extension, component catalog, validation timing, notes) with no bundle files to link out to; the inlined full component list is borderline bulk that a separate reference could hold, but structure is good overall.	4 / 5
	Total	17 / 20 Passed

Description

78%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 concise, uses third-person voice, and clearly answers both what the skill does and when to use it with concrete trigger phrases. Minor gaps in action specificity and breadth of natural synonyms keep it just short of perfect.

Suggestions

Lead with concrete actions rather than packaging framing (e.g., 'Add standard UI components to a json-render catalog and wire up their React implementations').

Include a few more natural synonyms a user might say (e.g., 'shadcn components', 'UI component library') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and concrete actions ('adding standard UI components to a catalog, or building web UIs'), but the 'what' is phrased as component packaging rather than a list of distinct concrete actions, leaving it at the domain-plus-actions-but-not-comprehensive level.	3 / 5
Completeness	It explicitly states both the 'what' ('Pre-built shadcn/ui components for json-render') and the 'when' via a clear 'Use when working with...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	It surfaces several natural phrases a user would say ('@json-render/shadcn', 'shadcn/ui components', 'building web UIs', 'Radix UI + Tailwind CSS components') but omits some common synonyms and the package-name-as-trigger could be more prominent.	4 / 5
Distinctiveness Conflict Risk	The narrow package-scoped niche ('@json-render/shadcn', catalog vs React entry points) makes it largely distinct, with only minor overlap risk against generic UI/web-UI skills.	4 / 5
	Total	16 / 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/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.