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

74

Quality

92%

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 concrete commands, executable code examples, and a well-sequenced workflow including validation checkpoints. The main weakness is progressive disclosure: numerous referenced files (rules/*.md, cli.md, customization.md) are cited but absent from the bundle.

Suggestions

Ship 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) or remove the dead links so navigation resolves to real content.

Tighten the Key Fields and Workflow sections by moving verbose per-field explanations into cli.md, keeping SKILL.md as a lean overview.

Consider inlining the most critical one or two rules (e.g., spacing, validation states) fully and demoting the rest to references, so the highest-frequency guidance does not depend on missing files.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence (e.g., terse 'Use Components, Not Custom Markup' rules with one-line justifications), but the Key Fields list and Workflow steps include some explanatory padding that could be trimmed; not severely verbose.

4 / 5

Actionability

Fully executable guidance throughout: concrete CLI commands (`npx shadcn@latest add button card dialog`, `--dry-run`, `--diff`), copy-paste TSX pattern examples, and a precise component-selection table covering common cases.

5 / 5

Workflow Clarity

The 9-step Workflow is clearly sequenced with explicit verification checkpoints ('always read the added files and verify they are correct', check installed components before add, confirm with user before destructive `--overwrite`), and the Updating Components section has a validate-per-file feedback loop.

5 / 5

Progressive Disclosure

Structure and one-level-deep reference signaling are good (clear 'Detailed References' list pointing to rules/*.md, cli.md, customization.md), but those referenced files are not present in the bundle, so the navigation links resolve to missing content rather than real one-level-deep materials.

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.

The description is excellent: third-person voice, concrete actions, explicit 'what' and 'when' guidance, and highly distinctive trigger phrases tied to shadcn-specific artifacts and commands.

DimensionReasoningScore

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 'what' (manages components/projects across multiple actions) and 'when' with concrete trigger phrases ('Applies when...', 'Also triggers for...'), matching the 5-anchor pattern.

5 / 5

Trigger Term Quality

Comprehensive natural-term coverage including 'shadcn/ui', 'component registries', 'presets', '--preset codes', 'components.json file', and exact user phrases like 'shadcn init', 'create an app with --preset', and 'switch to --preset'.

5 / 5

Distinctiveness Conflict Risk

The triggers ('components.json file', '--preset codes', 'shadcn init') are highly specific to shadcn, creating a clear niche with minimal conflict risk against other skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 14 missing

Warning

Total

15

/

16

Passed

Repository
MODSetter/SurfSense
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.