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".
99
100%
Does it follow best practices?
Impact
Pending
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 natural user phrases and technical terms that would help Claude accurately select this skill. The description is comprehensive without being verbose.
| 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 trigger profile 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, code examples with correct/incorrect contrasts, and a clear multi-step workflow with validation checkpoints. The progressive disclosure is excellent, with the main file serving as a comprehensive overview that links to detailed rule files for edge cases.
| 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 earns its place with actionable rules, patterns, or commands. The component selection table and key patterns section are dense with useful information without padding. | 3 / 3 |
Actionability | The skill provides fully executable CLI commands, concrete TSX code examples with correct/incorrect pairs, specific component composition patterns, and a clear workflow with exact commands to run. The Quick Reference section is copy-paste ready, and the Key Patterns section shows executable code contrasting right vs wrong approaches. | 3 / 3 |
Workflow Clarity | The workflow section provides a clear 9-step sequence with explicit validation checkpoints (step 7: review added components, step 5: use --dry-run and --diff before updating). The Updating Components section has an explicit feedback loop (check diff → decide per file → preserve local changes). The preset switching workflow asks the user first and provides three clear paths with specific commands. | 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). Each reference is clearly signaled with descriptive labels, and the main file contains just enough context (critical rules summaries, key patterns) to be useful without being monolithic. | 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
6338825
- 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.