CtrlK
BlogDocsLog inGet started
Tessl Logo

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. 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".

73

Quality

92%

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

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.

Highly actionable, well-sequenced content with strong validation checkpoints, but progressive disclosure is undermined because most of the Detailed References and Critical Rules link to files missing from the bundle. The inline rule summaries soften the impact but cannot replace the absent reference files.

Suggestions

Ship the referenced bundle files (rules/styling.md, forms.md, composition.md, chat.md, icons.md, base-vs-radix.md, cli.md, registry.md, customization.md) or inline the essential Incorrect/Correct pairs so the Critical Rules are self-contained.

Reduce the mild redundancy between Critical Rules and Key Patterns by keeping Key Patterns only for patterns not already shown as bullet rules.

Verify each linked path resolves in the bundle before publishing; broken reference links make the detailed material unreachable.

DimensionReasoningScore

Conciseness

Dense, actionable one-liner rules with minimal conceptual padding, but the Key Patterns section re-illustrates rules already stated in Critical Rules (gap vs space-y, size vs w/h, Badge vs raw colors) — minor redundancy that could be trimmed.

4 / 5

Actionability

Fully executable throughout: copy-paste npx commands, concrete TSX code blocks, a Quick Reference of ready-to-run commands, and a Component Selection table mapping needs to specific components.

5 / 5

Workflow Clarity

A 9-step Workflow and a dedicated Updating Components section with explicit validation checkpoints (dry-run/diff, "always read the added files and verify", "Fix all issues before moving on", require explicit approval before --overwrite) provide feedback loops for batch/destructive operations.

5 / 5

Progressive Disclosure

Sections are clearly organized and references are well-signaled and one level deep, but the body heavily links to bundle files (./rules/styling.md, forms.md, composition.md, chat.md, icons.md, base-vs-radix.md, ./cli.md, ./registry.md, ./customization.md) that are NOT present in the bundle — the promised Incorrect/Correct code pairs are unreachable, undermining navigation.

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.

A strong description: third-person voice, concrete actions, explicit what/when guidance, and distinctive trigger phrases that match real user requests. No padding or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces" — covering the domain comprehensively rather than gesturing at it.

5 / 5

Completeness

Explicitly answers both what ("Manages shadcn components and projects — adding, searching, fixing...") and when ("Applies when working with shadcn/ui... Also triggers for...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users actually say — "shadcn init", "create an app with --preset", "switch to --preset" — plus technical anchors (components.json, --preset codes) and synonyms (shadcn/ui).

5 / 5

Distinctiveness Conflict Risk

Niche is clearly scoped to shadcn/ui via distinctive triggers (components.json, --preset codes, named presets), with minimal overlap risk against generic UI or build skills.

5 / 5

Total

20

/

20

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: 17 missing

Warning

Total

14

/

16

Passed

Repository
1weiho/open-slide
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.