shadcn-ui

The shadcn CLI, component composition, theming, and registry workflow. Use when adding, replacing, upgrading, or debugging a shadcn/ui primitive itself, or when changing a theme or registry. Do not load it for ordinary edits to a file that happens to import a shadcn component.

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

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

An action-dense, well-sectioned instruction skill with concrete CLI commands and explicit verification checkpoints. Its only weakness is progressive disclosure: everything lives inline in one file with no reference layer to offload the denser guidance.

Suggestions

Move the longer reference-style sections (e.g. Transitions And Motion, Styling And Theming, Forms And Inputs) into files under references/ and link to them one level deep, keeping SKILL.md as an overview.

Add a short 'Quick reference' or table of contents at the top of the body so the dense sections are navigable at a glance.

Consider extracting the component-composition rules (Avatar needs AvatarFallback, TabsTrigger in TabsList, etc.) into a references/composition.md checklist to reduce inline length.

Dimension	Reasoning	Score
Conciseness	Lean bullet-driven guidance that assumes Claude's competence; it avoids explaining generic concepts and every line carries project-specific instruction. Not the level below because there is no padded explanation of things Claude already knows.	3 / 3
Actionability	Provides concrete, copy-ready commands ("pnpm dlx shadcn@latest info --json", "add <component> --dry-run", "docs <component>") plus specific primitives (CardHeader, AvatarFallback) and semantic tokens. Not a 2 because guidance is specific and executable rather than pseudocode.	3 / 3
Workflow Clarity	The numbered "First Steps" sequence and the add/update flow include explicit checkpoints ("use --dry-run and --diff to inspect the change", "read the generated files... before using the component"). Not a 2 because validation-style checkpoints are explicit for the risky overwrite operation.	3 / 3
Progressive Disclosure	The body is well organized into clear sections, but it is a single ~107-line file with no one-level-deep references (no references/, scripts/, or assets/ bundle exists), and several sections (Transitions, Forms, Styling) are dense enough to warrant splitting. Not a 3 because there is no appropriately split reference layer; not a 1 because sectioning and navigation are clean and there is no deep reference nesting.	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 tight, third-person description with an explicit trigger and a deliberate exclusion clause that scopes it precisely. It answers what, when, and when-not cleanly with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "adding, replacing, upgrading, or debugging a shadcn/ui primitive itself" and "changing a theme or registry" — rather than vague language.	3 / 3
Completeness	Explicitly states what ("The shadcn CLI, component composition, theming, and registry workflow") and when ("Use when adding, replacing, upgrading, or debugging...") with an explicit trigger clause.	3 / 3
Trigger Term Quality	Uses natural terms a user would say (add/replace/upgrade/debug a primitive, theme, registry) with good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche and adds an explicit exclusion — "Do not load it for ordinary edits to a file that happens to import a shadcn component" — making wrong-skill triggering unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: BuilderIO/agent-native
Path: .agents/skills/shadcn-ui/SKILL.md
Commit: e9a2f0e

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.