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

90%

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

81%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 strong validation checkpoints, and it respects token budget well apart from minor command duplication. Its main defect is structural: it is built as an overview that offloads detail to seven referenced files that are absent from the bundle, so the progressive-disclosure navigation points to nothing.

Suggestions

Ship the referenced rule files (rules/styling.md, rules/forms.md, rules/composition.md, rules/icons.md, rules/base-vs-radix.md, cli.md, customization.md) alongside SKILL.md, or inline the essential rule content and remove the broken links.

De-duplicate the Quick Reference against the Workflow section — either trim the Workflow's command list and keep Quick Reference as the canonical CLI cheatsheet, or vice versa.

If the rules are intentionally bundled elsewhere, verify the relative paths resolve from SKILL.md's location and confirm the files are part of the distributed skill package.

Dimension	Reasoning	Score
Conciseness	Mostly lean imperative bullets and compact code examples that assume Claude's competence, but the Quick Reference duplicates CLI commands already detailed in the Workflow section, adding modest redundancy.	4 / 5
Actionability	Fully executable throughout — exact CLI commands with specific flags ('npx shadcn@latest add button --dry-run', 'apply a2r6bw --only theme,font'), real code patterns, and a copy-paste-ready Quick Reference covering the common cases.	5 / 5
Workflow Clarity	A 9-step numbered workflow with explicit validation checkpoints ('always read the added files and verify', 'Never use --overwrite without explicit approval') and a validate→diff→decide feedback loop for the destructive Updating Components flow.	5 / 5
Progressive Disclosure	The body signals one-level-deep references to seven files (rules/styling.md, rules/forms.md, rules/composition.md, rules/icons.md, rules/base-vs-radix.md, cli.md, customization.md), but none of these exist in the actual bundle — only assets/ is present, leaving every Detailed References link dangling.	2 / 5
	Total	16 / 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: third-person voice, comprehensive concrete actions, explicit 'Use when'-style triggers, and a clearly distinct niche anchored by the components.json marker. It hits the top anchor on every dimension with no padding.

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 the skill's capabilities.	5 / 5
Completeness	Explicitly answers both what ('Manages shadcn components and projects') and when ('Applies when...', 'Also triggers for...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Comprehensive natural-language triggers users would actually say: 'shadcn init', 'create an app with --preset', 'switch to --preset', plus concrete tokens like 'components.json' and '--preset codes'.	5 / 5
Distinctiveness Conflict Risk	The 'shadcn/ui' niche and 'components.json' file marker are highly distinct triggers with minimal overlap risk against 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: different-ai/openwork
Path: .opencode/skills/shadcn/SKILL.md
Commit: 7b76a2b

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