CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

74

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

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 body is highly actionable with strong workflow validation and dense non-obvious guidance, but it ships with seven broken bundle references, which undercuts its progressive-disclosure architecture. Minor internal duplication (rules restated in Key Patterns, links restated in Detailed References) also costs tokens.

Suggestions

Include 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) in the skill directory, or remove/consolidate the dead references — the Detailed References and Critical Rules sections currently point readers to files that do not exist.

De-duplicate content that appears in both Critical Rules and Key Patterns (gap-* vs space-y-*, size-* vs w-* h-*, semantic colors/Badge) — keep one inline and defer the other to the linked rule file.

Drop the bottom 'Detailed References' section that re-lists every link already given inline, or keep only it (with inline links removed) to save tokens.

DimensionReasoningScore

Conciseness

Largely efficient and free of known-concept filler, but has duplication: the gap-*/space-y-* and size-*/w-* h-* rules appear in both Critical Rules and Key Patterns, the semantic-color/Badge guidance appears twice, and the Detailed References section re-lists every link already given inline. Matches the anchor 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

Fully executable guidance throughout: exact CLI commands ("npx shadcn@latest add button --diff button.tsx"), copy-paste code patterns with correct/wrong pairs, a needs→component selection table, and field-by-field instructions for interpreting project context.

5 / 5

Workflow Clarity

The nine-step workflow has explicit validation checkpoints and feedback loops: check installed components before add, --dry-run/--diff before updates, "always read the added files and verify they are correct", and "Never use --overwrite without the user's explicit approval". Destructive/batch operations are well guarded, so no cap applies.

5 / 5

Progressive Disclosure

In-body structure is well organized with clearly signaled references, but every referenced path (rules/styling.md, rules/forms.md, rules/composition.md, rules/icons.md, rules/base-vs-radix.md, cli.md, customization.md) is missing from the actual bundle — only two unreferenced PNGs exist in assets/. All seven references are dead, so the one-level-deep split is non-functional as shipped.

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.

Excellent description: concrete, comprehensive action list, explicit trigger guidance covering both natural phrases and file-based markers, and third-person voice throughout. It mirrors the rubric's best-in-class examples closely.

DimensionReasoningScore

Specificity

Lists six concrete actions ("adding, searching, fixing, debugging, styling, and composing UI") plus "Provides project context, component docs, and usage examples" — comprehensive, specific coverage of the skill's capabilities with no filler.

5 / 5

Completeness

Explicitly answers both: what ("Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI") and when ("Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for...").

5 / 5

Trigger Term Quality

Covers natural terms users would actually say: "shadcn/ui", "component registries", "presets", "--preset codes", "components.json", plus verb phrases like "shadcn init", "create an app with --preset", "switch to --preset" — including the config filename and CLI flag forms.

5 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — "components.json" and "--preset codes" are shadcn-specific markers unlikely to fire for other skills; voice is consistently third person ("Manages", "Provides", "Applies").

5 / 5

Total

20

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 14 missing

Warning

Total

15

/

16

Passed

Repository

databricks/devhub

Path

.agents/skills/shadcn/SKILL.md

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.