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

71

Quality

88%

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

77%

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 executable commands and well-sequenced, checkpointed workflows, but it is held back by cross-section redundancy and by progressive-disclosure references that point to bundle files that are not actually present.

Suggestions

Ship the referenced bundle files (./rules/*.md, ./cli.md, ./customization.md) or remove the dead links so progressive-disclosure navigation resolves.

De-duplicate content that appears in multiple sections — fold Principles into Critical Rules and consolidate the CLI examples so commands live in one place (e.g., Quick Reference) with Workflow linking to them.

Tighten the Key Patterns section to only show examples not already implied by the Critical Rules bullets to reduce token redundancy.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence with minimal concept explanation, but it restates material across sections — Principles overlaps Critical Rules, Key Patterns repeats the rules as code, and CLI commands appear in both Workflow and Quick Reference — so it could be tightened rather than earning the fully-lean score-3 anchor.

2 / 3

Actionability

Provides fully executable commands with specific flags (e.g. "npx shadcn@latest add button --diff button.tsx", "apply a2r6bw --only theme,font") and copy-paste TSX examples, matching the score-3 anchor rather than the pseudocode score-2 anchor.

3 / 3

Workflow Clarity

A clear 9-step Workflow plus an Updating Components procedure with explicit validation checkpoints (check installed components first, review/verify added files and fix issues before proceeding, diff→decide per file, confirm before --overwrite) matches the score-3 anchor with feedback loops for error recovery.

3 / 3

Progressive Disclosure

The body is well organized with clearly signaled one-level-deep references (rules/forms.md, cli.md, customization.md, etc.), but those referenced files do not exist in the bundle — only assets/*.png are present and unreferenced — so the navigation structure is broken rather than delivering the easy navigation of the score-3 anchor.

2 / 3

Total

10

/

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.

The description is specific, complete, and distinctive: it enumerates concrete actions, gives explicit "applies when" and "also triggers for" guidance, and anchors on shadcn-specific signals. It is a strong, low-conflict skill description.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "adding, searching, fixing, debugging, styling, and composing UI" — directly matching the score-3 anchor rather than the single-action or vague anchors.

3 / 3

Completeness

Explicitly states what ("Manages shadcn components and projects") and when ("Applies when working with…" and "Also triggers for…"), satisfying both halves unlike the score-2 anchor that lacks an explicit when clause.

3 / 3

Trigger Term Quality

Covers natural terms a user would say — "shadcn/ui", "component registries", "presets", "--preset codes", "components.json", and quoted phrases like "shadcn init" and "create an app with --preset"; better than the partial-coverage score-2 anchor.

3 / 3

Distinctiveness Conflict Risk

A clear shadcn-specific niche with distinctive triggers (components.json, --preset codes, "shadcn init") makes conflict with other skills unlikely; not generic like the score-1/2 anchors.

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
Devin-AXIS/iPolloWork
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.