shadcn-ui

Build UI components with shadcn/ui. Pairs with the Stitch design loop to ship structured, accessible components quickly.

Quality

57%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/shadcn-ui/SKILL.md

Quality

Content

57%

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

This is a thin catalogue entry rather than a working skill: it is well-organized and points cleanly upstream, but provides no executable guidance for actually building components and punts the core install step to an external README.

Suggestions

Provide the concrete install command for the upstream bundle (e.g., the exact git clone / copy paths) instead of instructing the reader to 'inspect the upstream README for exact paths'.

Replace the meta-framing about Open Design discovery with a minimal, actionable quick-start step.

Add a brief validation step confirming the skill is installed and invokable before relying on it.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, but spends tokens on meta-framing ('This catalogue entry advertises the skill in Open Design so the agent discovers it during planning') rather than skill substance, so it does not meet the 'every token earns its place' anchor.	2 / 3
Actionability	It offers a concrete command (`open https://github.com/google-labs-code/skills`) and names skill invocation, but the core instruction to 'install the upstream bundle into your active agent's skills directory' provides no install command or paths, leaving key details missing.	2 / 3
Workflow Clarity	A loose sequence is present (install bundle -> inspect README -> invoke by name/trigger), but the single action is not unambiguous — 'install the upstream bundle' is unspecified — and there are no validation checkpoints, so it cannot reach 3.	2 / 3
Progressive Disclosure	At under 50 lines with no local bundle files, the body is well-organized into clear sections (What it does, Source, How to use) and points one level out to a clearly signaled upstream link, satisfying the simple-skill progressive disclosure guidance.	3 / 3
	Total	9 / 12 Passed

Description

57%

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 and distinguishable, naming shadcn/ui and the Stitch pairing, but it lacks explicit 'Use when...' trigger guidance and lists only one core action, capping completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when building or styling UI components, especially with shadcn/ui, Radix primitives, or Tailwind-based component libraries.'

Expand from the single 'Build' action to multiple concrete actions (e.g., 'Scaffold, customize, and theme shadcn/ui components') to lift specificity.

Broaden trigger coverage with natural phrasings users actually say, such as 'component library', 'radix components', or 'tailwind UI components'.

Dimension	Reasoning	Score
Specificity	Names the domain (shadcn/ui UI components) and attributes ('structured, accessible components') but offers only one core action ('Build') rather than multiple concrete actions, so it does not reach the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	It clearly states what the skill does, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant natural terms a user would say ('shadcn/ui', 'accessible components'), but coverage is thin — missing common variations like 'shadcn components', 'radix', 'tailwind components', or 'component library' that users would naturally invoke.	2 / 3
Distinctiveness Conflict Risk	Naming the specific shadcn/ui library and the Stitch design loop carves out a clear niche with distinct triggers that are unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/shadcn-ui/SKILL.md
Commit: a2ba3ee

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