CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

shadcn-ui

Using the app's local UI adapter and Toolkit or shadcn primitives. Use when choosing or composing standard controls, implementing dialogs, menus, or forms, or changing component variants and theme tokens.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is an exemplary lean, rule-dense instruction skill: concrete component mappings, exact tokens and import paths, and clear prohibitions, organized into clean sections. Its only weaknesses are a couple of abstract conditional directives and the absence of any post-change validation guidance.

Suggestions

Add a brief final verification cue (e.g., "confirm the control still passes the app's existing checks for focus and dismissal") to close the loop after changes.

Replace abstract directives like "Follow an adjacent local shim" with a one-line concrete example of what such a shim looks like.

Consider a minimal import example (e.g., `import { Button } from "@/components/ui/button"`) to make the adapter rule immediately executable.

DimensionReasoningScore

Conciseness

The ~60-line body is dense, directive guidance with zero padding: it never explains what shadcn or a dialog primitive is, and every sentence carries an actionable rule, matching the 'lean and efficient; every token earns its place' anchor.

5 / 5

Actionability

Highly concrete for an instruction-only skill — an explicit control-choice mapping ("Switch for a binary setting, Checkbox for independent multi-select, RadioGroup for one choice"), exact tokens (bg-background, text-muted-foreground), exact import paths (@/components/ui/*), and hard prohibitions ("Never use browser alert, confirm, or prompt"). A few conditional/abstract directives ("Follow an adjacent local shim", "class-merging helper when it has one") keep it just below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The opening establishes a clear pre-flight checkpoint ("Read the app's design-system configuration, Toolkit provider, and local UI components before adding or changing a control") and the sections are thematically coherent. However, beyond that first read-before-acting step there is no sequencing or result validation, fitting the 'clear sequence with most checkpoints; minor gaps' anchor rather than the fully validated one.

4 / 5

Progressive Disclosure

No bundle files are needed or present; the body is compact, well-organized under clear section headers, and includes a clearly signaled pointer to the related frontend-design skill with no nested references — per the simple-skill guidance this matches the top anchor.

5 / 5

Total

18

/

20

Passed

Description

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

The description is specific and includes a well-formed explicit trigger clause with concrete terms, though the "what" statement is somewhat implicit and a few natural synonyms are missing. Overall a strong description with minor room for improvement.

Suggestions

State the skill's function more directly in the first sentence (e.g., "Guide component selection and composition using...") so the "what" is as explicit as the "when".

Add a few more natural trigger terms users would say, such as "buttons", "dropdowns", "toggles", or "UI components".

Add a short distinguishing clause (e.g., "for control implementation, not visual direction") to reduce overlap with the closely related frontend-design skill.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("choosing or composing standard controls, implementing dialogs, menus, or forms, or changing component variants and theme tokens") with only minor coverage gaps, matching the 'several specific actions' anchor better than the fully comprehensive anchor.

4 / 5

Completeness

An explicit "Use when..." clause with concrete triggers is present, but the "what" ("Using the app's local UI adapter and Toolkit or shadcn primitives") describes the domain rather than clearly stating the skill's function, so it falls between the 4 and 5 anchors — closer to 4.

4 / 5

Trigger Term Quality

Natural trigger terms are present ("dialogs, menus, or forms", "component variants", "theme tokens", "shadcn"), but a few common user phrases like "buttons", "dropdowns", or "toggle" are missing, fitting the 'good keyword coverage; a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (local UI adapter / shadcn primitives, control composition) but "changing component variants and theme tokens" carries minor overlap risk with the closely related frontend-design skill, matching the 'mostly distinct; minor overlap risk' anchor.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

BuilderIO/agent-native

Path

.agents/skills/shadcn-ui/SKILL.md

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.