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".
79
100%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope around shadcn/ui component management, lists concrete actions, and provides explicit trigger conditions. It uses third person voice consistently and includes both technical identifiers (components.json, --preset) and natural user phrases (shadcn init, create an app). The description is comprehensive yet concise.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: adding, searching, fixing, debugging, styling, and composing UI components. Also mentions providing project context, component docs, and usage examples. | 3 / 3 |
Completeness | Clearly answers both 'what' (manages shadcn components — adding, searching, fixing, debugging, styling, composing UI; provides project context, docs, examples) and 'when' (explicitly states 'Applies when working with shadcn/ui, component registries, presets...' and 'Also triggers for...'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'shadcn/ui', 'component registries', 'presets', '--preset codes', 'components.json', 'shadcn init', 'create an app with --preset', 'switch to --preset'. These cover both technical terms and natural user phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche around shadcn/ui specifically. The mention of components.json, shadcn init, --preset, and component registries creates a very specific domain that is unlikely to conflict with generic UI or component skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exceptionally well-crafted skill that maximizes information density while maintaining clarity. It provides concrete, executable guidance through CLI commands and code examples, maintains clear multi-step workflows with validation checkpoints, and uses progressive disclosure effectively by summarizing critical rules inline while linking to detailed reference files. The dynamic project context injection via CLI command is a particularly strong pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude's competence with programming concepts, never explains what components or libraries are, and every section delivers actionable information. The rules are stated as terse imperatives with correct/incorrect pairs referenced via linked files rather than inline bloat. | 3 / 3 |
Actionability | The skill provides fully executable CLI commands, concrete TSX code examples showing correct vs incorrect patterns, a component selection table, and step-by-step workflows with specific commands. The Key Patterns section has copy-paste ready code, and the Quick Reference provides real CLI invocations covering all major use cases. | 3 / 3 |
Workflow Clarity | The main workflow is clearly numbered with 9 steps covering the full lifecycle from project context to component review. The Updating Components section has an explicit validation flow (dry-run → diff → decide per file) with clear decision criteria. The preset switching workflow offers three distinct paths with specific commands. Destructive operations (--overwrite) have explicit approval gates. | 3 / 3 |
Progressive Disclosure | The SKILL.md serves as a well-structured overview with clear one-level-deep references to detailed rule files (forms.md, composition.md, icons.md, styling.md, base-vs-radix.md, cli.md, customization.md). Critical rules are summarized inline with links to full incorrect/correct code pairs. The Detailed References section at the bottom provides a clear navigation index. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- databricks/devhub
- Commit
49eeda2
- Reviewed
Table of Contents
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.