shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. 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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

92%

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

The body is lean, highly actionable, and has a well-sequenced workflow with validation gates. Its main weakness is progressive disclosure: the detailed reference files it points to are absent from the bundle.

Suggestions

Ship the referenced rule/reference files (rules/styling.md, rules/forms.md, rules/composition.md, rules/base-vs-radix.md, rules/icons.md, cli.md, customization.md) so the linked navigation resolves, or inline the essential content and drop the dead links.

Verify each in-body markdown link target exists under references/scripts/assets before publishing; right now only assets/ is present.

Consider folding the standalone Quick Reference command list into the Workflow/CLI sections to reduce command duplication, since the same flags reappear across sections.

Dimension	Reasoning	Score
Conciseness	Information-dense throughout with no padding about what shadcn or libraries are; every section adds project-specific knowledge (CLI flags, composition rules, semantic-color rules) Claude would not already know.	3 / 3
Actionability	Fully executable commands ("npx shadcn@latest add button card dialog", "--dry-run", "--diff") and copy-paste TSX patterns; the Component Selection table maps needs to concrete components.	3 / 3
Workflow Clarity	A clear 9-step Workflow plus an Updating Components loop with explicit validation checkpoints (dry-run → diff → decide per file), and confirmation gates for destructive preset/overwrite operations.	3 / 3
Progressive Disclosure	References are one-level-deep and clearly signaled, but the linked files (rules/styling.md, rules/forms.md, rules/composition.md, rules/base-vs-radix.md, rules/icons.md, cli.md, customization.md) do not exist in the bundle, so navigation does not resolve.	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, third-person description that states concrete capabilities and gives explicit, varied trigger conditions for when to invoke the skill. It is distinctive and unlikely to fire for the wrong skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "adding, searching, fixing, debugging, styling, and composing UI" plus "Provides project context, component docs, and usage examples" — matching the multi-action anchor.	3 / 3
Completeness	Explicitly answers both what ("Manages shadcn components and projects…") and when ("Applies when working with shadcn/ui… Also triggers for…"), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — "shadcn/ui", "shadcn init", "create an app with --preset", "switch to --preset", "components.json" — with good variation rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Narrow shadcn/ui niche with distinctive triggers like "components.json" and "--preset codes" makes conflict with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 14 missing	Warning

	Total	15 / 16 Passed

Repository: databricks/devhub
Commit: 131db95

Reviewed: 5 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.