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

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

The canonical home for this skill is shadcn in shadcn-ui/ui

Quality

Content

85%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 content is highly actionable and well-sequenced with strong validation checkpoints, and it is token-efficient without over-explaining. Its main weakness is progressive disclosure: the body points to a rich set of rule/reference files that are not present in the bundle, leaving the navigation structure partly broken.

Suggestions

Ship the referenced bundle files (rules/styling.md, rules/forms.md, rules/composition.md, rules/icons.md, rules/base-vs-radix.md, cli.md, customization.md) or remove the links and inline only what exists.

Reduce the mild redundancy between the 'Critical Rules' bullets and the 'Key Patterns' code examples so each rule appears in one place.

If the rule files are intentionally omitted, replace the file links with self-contained inline guidance so the skill works without missing references.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence — it opens with a one-line definition and otherwise delivers rules, commands, and code rather than concept explanations. Minor repetition between 'Critical Rules' bullets and 'Key Patterns' examples keeps it just below a 5.	4 / 5
Actionability	Fully executable throughout: concrete CLI commands (add/init/apply/docs/search with --dry-run, --diff, --only), copy-paste tsx examples, and a component-selection table covering the common cases.	5 / 5
Workflow Clarity	The 9-step Workflow and 'Updating Components' section give a clear sequence with explicit validation checkpoints — read and verify added files, use --dry-run/--diff before overwriting, and 'Never use --overwrite without the user's explicit approval' — plus feedback loops for destructive/batch operations.	5 / 5
Progressive Disclosure	References are clearly signaled and one level deep ('Detailed References' section, per-rule links), but the referenced files — ./rules/styling.md, forms.md, composition.md, icons.md, base-vs-radix.md, ./cli.md, ./customization.md — do not exist in the bundle (only assets/ is present), so the disclosed structure is not actually backed by files.	3 / 5
	Total	17 / 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 a strong, third-person statement that concretely lists capabilities and provides explicit, multi-form trigger guidance. It cleanly answers both what the skill does and when to invoke it, with minimal conflict risk.

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', giving comprehensive coverage of capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (manages components/projects, provides context/docs/examples) and 'when' ('Applies when working with shadcn/ui... or any project with a components.json file. Also triggers for...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Covers natural terms and synonyms users would say — 'shadcn/ui', 'component registries', 'presets', '--preset codes', 'components.json file', plus explicit phrasings like 'shadcn init' and 'create an app with --preset'.	5 / 5
Distinctiveness Conflict Risk	Niche is clearly scoped to shadcn/ui with distinct triggers (components.json, --preset, shadcn init), minimizing overlap with other skills.	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: 14 missing	Warning

	Total	14 / 16 Passed

Repository: graphif/project-graph
Path: .agents/skills/shadcn/SKILL.md
Commit: f187e86

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.