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

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%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.

A well-structured, actionable instruction skill with concrete commands, explicit do/don't rules, and verification checkpoints for destructive component operations. It sits a notch below the top anchor across dimensions due to minor over-prose and rule-without-example gaps rather than any fundamental weakness.

Suggestions

Tighten the Transitions section: convert the longest prose paragraphs into concise bullet rules so the section matches the lean density of the rest.

Add a one-line inline example to a few rule-only entries (e.g. the accessible-title and InputGroup rules) to lift actionability toward fully copy-paste-ready guidance.

Make the post-add validation explicit as a checkpoint step ("run the app / typecheck and confirm imports resolve before finishing") to close the remaining workflow-clarity validation gap.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's competence (no "what is shadcn" preamble), and every section earns its place; the Transitions section's prose is slightly expansive but justified, keeping it just below the top anchor.	4 / 5
Actionability	Concrete CLI commands (shadcn add/info/docs, --dry-run, --diff) and specific component-pairing rules (Avatar needs AvatarFallback, TabsTrigger inside TabsList) give mostly executable guidance with minor rule-without-example gaps.	4 / 5
Workflow Clarity	First Steps is a clear numbered sequence with inspection/verification checkpoints (shadcn info, resolve aliases, --dry-run/--diff before overwrite, read generated files and fix imports), satisfying most checkpoints with only minor validation gaps.	4 / 5
Progressive Disclosure	The single-file body is cleanly organized into well-signaled sections with one-level cross-references (frontend-design, Related Skills) and no nested references; absence of bundle files keeps it just below a 5 given the inline density.	4 / 5
	Total	16 / 20 Passed

Description

87%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 precise, well-triggered description that concretely names actions and includes explicit when-to-use guidance plus a conflict-avoidance boundary. Minor synonym coverage is the only thing keeping specificity and trigger quality off the top anchor.

Dimension	Reasoning	Score
Specificity	Names the domain (shadcn CLI, component composition, theming, registry) plus several concrete actions ("adding, replacing, upgrading, or debugging a shadcn/ui primitive itself"), with only minor coverage gaps preventing a 5.	4 / 5
Completeness	It clearly states what the skill covers (CLI, composition, theming, registry workflow) and gives an explicit "Use when" trigger with concrete phrases, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural trigger phrasing ("adding, replacing, upgrading, or debugging", "changing a theme or registry") and the product name shadcn/ui give good coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	The trigger is tightly scoped to shadcn/ui primitives and includes an explicit anti-conflict clause ("Do not load it for ordinary edits to a file that happens to import a shadcn component"), minimizing overlap with adjacent skills.	5 / 5
	Total	18 / 20 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: d477ebc

Reviewed: 4 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.