CtrlK
BlogDocsLog inGet started
Tessl Logo

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

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable, well-sequenced skill body with strong command and code examples and clear workflow checkpoints. Its only real defect is broken progressive disclosure: the rule and reference files it links to are absent from the bundle.

Suggestions

Ship the referenced bundle files (rules/styling.md, rules/forms.md, rules/composition.md, rules/base-vs-radix.md, rules/icons.md, cli.md, customization.md) so the Critical Rules' promised Incorrect/Correct pairs and detailed references actually exist, or inline the essential Incorrect/Correct pairs directly and drop the dangling links.

Remove or fix the 'Detailed References' section entries that point to non-existent files, since following them leads to dead ends.

If the rule files are intentionally not bundled, replace the file links with a note that the guidance is self-contained in SKILL.md to avoid implying external detail that isn't present.

DimensionReasoningScore

Conciseness

Lean, information-dense body that assumes Claude's competence — it does not explain React, Tailwind, or Radix, and every section adds shadcn-specific knowledge (FieldGroup/Field, data-icon, semantic tokens) rather than padding with known concepts.

3 / 3

Actionability

Packed with copy-paste-ready CLI commands (npx shadcn@latest add/docs/search/init with concrete flags) and executable TSX with correct/wrong pairs (gap-* vs space-y-*, size-10 vs w-10 h-10, Badge variant vs raw span), matching the fully-executable anchor.

3 / 3

Workflow Clarity

A 9-step Workflow plus a dedicated Updating Components sequence with explicit checkpoints — check installed components before add, --dry-run/--diff previews, 'always read the added files and verify they are correct... Fix all issues before moving on', and 'Never use --overwrite without the user's explicit approval'.

3 / 3

Progressive Disclosure

Structure and signaling are strong (inline links, '→ [styling.md]', and a final Detailed References list, all one level deep), but none of the 7 referenced files (rules/*.md, cli.md, customization.md) exist in the bundle, so the claimed Incorrect/Correct detail content is missing and navigation hits dead ends — 'content appropriately split' is not actually delivered.

2 / 3

Total

11

/

12

Passed

Description

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.

A highly specific, well-triggered description that clearly states both capabilities and activation conditions with natural user phrasings. No weaknesses across any dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'adding, searching, fixing, debugging, styling, and composing UI' plus 'Provides project context, component docs, and usage examples' — matching the score-3 anchor of enumerating specific actions rather than vague language.

3 / 3

Completeness

Explicitly answers both what ('Manages shadcn components and projects...') and when ('Applies when working with shadcn/ui... Also triggers for...'), with an explicit 'Use when'-style trigger clause.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say, including 'shadcn/ui', 'components.json', 'presets', '--preset codes', and the exact invocations 'shadcn init', 'create an app with --preset', and 'switch to --preset'.

3 / 3

Distinctiveness Conflict Risk

The shadcn domain and its distinctive triggers ('shadcn/ui', 'components.json', 'shadcn init', '--preset') form a clear niche unlikely to overlap with unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

relative_links

Relative link issues: 14 missing

Warning

Total

14

/

16

Passed

Repository
udecode/plate
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.