shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

88%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 well-sequenced with explicit validation checkpoints, and it organizes detail into well-signaled one-level-deep references. Its main weaknesses are mild repetition across sections and that the linked rule/reference files (rules/*.md, cli.md, registry.md, customization.md) are not present in the bundle, breaking the progressive-disclosure navigation it advertises.

Suggestions

Include the referenced rule and reference files (rules/*.md, cli.md, registry.md, customization.md) in the bundle, or remove the dead links — the body currently advertises navigation to files that do not exist.

Deduplicate preset-flag guidance between the Workflow (#9) and Quick Reference sections so each command appears in one canonical place.

Trim the component-selection table or move it into a reference file to reduce the inline token footprint, keeping only the most common mappings in SKILL.md.

Dimension	Reasoning	Score
Conciseness	The body is dense and largely assumes Claude's competence — rules are terse one-liners and code snippets are tight — but it still runs ~270 lines and repeats some guidance (e.g., preset sub-flags appear in both Workflow and Quick Reference), leaving minor trimming opportunities.	4 / 5
Actionability	Every rule is paired with concrete, executable commands (npx shadcn@latest … with specific flags) and copy-paste-ready code pairs showing correct vs. incorrect usage, fully covering the common cases.	5 / 5
Workflow Clarity	The numbered Workflow gives a clear sequence with explicit validation checkpoints — check installed components before add, run docs before using, use --dry-run/--diff to preview, read added files and verify correctness — including feedback loops for risky batch/registry operations.	5 / 5
Progressive Disclosure	Structure is strong: SKILL.md is an overview with one-level-deep, clearly signaled references (rules/*.md, cli.md, registry.md, customization.md) and a detailed-references index. However, the referenced bundle files do not exist on disk, so navigation links cannot be resolved — a real organizational gap rather than just an inlining issue.	4 / 5
	Total	18 / 20 Passed

Description

100%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 exemplary: it states concrete capabilities, gives explicit "Applies when" and "Also triggers for" guidance with natural user phrases, and is tightly scoped to shadcn-specific tokens that minimize conflict risk. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "adding, searching, fixing, debugging, styling, and composing UI" — alongside concrete project-context capabilities (component docs, usage examples), giving comprehensive coverage of the skill's actions.	5 / 5
Completeness	Explicitly answers both halves: the "what" (manages components/projects, provides context, docs, examples) and the "when" ("Applies when working with shadcn/ui…" plus the explicit "Also triggers for…" trigger phrases).	5 / 5
Trigger Term Quality	Covers natural terms users would say — "shadcn/ui", "components.json", "component registries", "presets", "--preset codes", "shadcn init", "create an app with --preset", "switch to --preset" — including the concrete file/flag tokens that trigger the skill.	5 / 5
Distinctiveness Conflict Risk	The niche is sharply defined by product-specific tokens (shadcn/ui, components.json, --preset), making collision with other skills minimal and the triggers highly distinctive.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
relative_links	Relative link issues: 17 missing	Warning

	Total	14 / 16 Passed

Repository: shadcn-ui/ui
Path: skills/shadcn/SKILL.md
Commit: 8a7701e

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