coss

Helps implement coss UI components correctly. Use when building UIs with coss primitives (buttons, dialogs, selects, forms, menus, tabs, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior. Covers imports, accessibility, Tailwind styling, and common pitfalls.

Quality

92%

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

85%

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

A well-structured, lean overview that offloads detail to a genuine, well-organized reference bundle with a clear sequenced workflow and validation checklist. The main weakness is actionability: most guidance routes to references rather than providing inline executable patterns.

Suggestions

Add one or two inline, copy-paste code examples (e.g. a minimal Dialog or Select composition) so the body is actionable without first opening a reference file.

Make the manual install pattern concrete: list the typical dependencies (e.g. @base-ui/react, Tailwind v4) and show the import-alias rewrite step instead of deferring to 'the component docs page'.

Tighten the minor repetition of the component-registry pointer (referenced in 'Source of truth', 'Component discovery', 'Usage workflow', and 'Primitive Guidance') to a single canonical mention.

Dimension	Reasoning	Score
Conciseness	Bullet-driven and lean; it assumes Claude's competence and does not explain what a component library or Tailwind is. Not the 2 level because there is little padding — every section (principles, critical rules, workflow, checklist) earns its place despite minor repetition of the registry pointer.	3 / 3
Actionability	Provides one concrete executable command ('npx shadcn@latest add @coss/<component>') and specific reference paths, but the manual install pattern stays vague ('install dependencies listed in the component docs page') and most guidance is 'consult X reference' rather than inline copy-paste code. Not the 3 level because executable, complete code is sparse; not the 1 level because the CLI snippet and exact file paths are concrete.	2 / 3
Workflow Clarity	The 'Usage workflow' is a clearly sequenced 6-step process ending in a self-check, reinforced by an explicit 'Output Checklist' validation gate covering imports, composition, a11y, and migration-sensitive flows. Not the 2 level because validation checkpoints are explicit rather than implicit.	3 / 3
Progressive Disclosure	SKILL.md is an overview with well-signaled, one-level-deep references (rules/, primitives/<name>.md, cli.md, component-registry.md, portal-props.md), all of which exist as real files, each annotated with what it covers. Not the 2 level because references are clearly signaled, shallow, and navigation is easy.	3 / 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 strong, third-person description with explicit 'Use when' triggers, concrete named capabilities, and good natural-term coverage. It clearly distinguishes the coss niche via migration framing and is unlikely to misfire.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'implement coss UI components', 'migrating from shadcn/Radix to coss/Base UI', 'composing trigger-based overlays', 'troubleshooting coss component behavior' — plus coverage areas (imports, accessibility, Tailwind styling, pitfalls). Not the 2 level because it goes beyond naming a domain to enumerating specific capabilities.	3 / 3
Completeness	Explicitly answers both: what ('Helps implement coss UI components correctly') and when ('Use when building UIs with coss primitives..., migrating..., composing..., or troubleshooting...'). Not the 2 level because the 'Use when' trigger clause is present and explicit, not merely implied.	3 / 3
Trigger Term Quality	Strong natural-term coverage a user would actually say: 'buttons, dialogs, selects, forms, menus, tabs, inputs, toasts', 'shadcn/Radix', 'coss/Base UI', 'trigger-based overlays'. Not the 2 level because it includes many common component-name variations rather than a single generic keyword.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to the coss component registry with migration-specific triggers (shadcn/Radix → coss/Base UI), making conflict with other skills unlikely. Not the 2 level because the library name and migration framing carve out a distinct trigger surface.	3 / 3
	Total	12 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: MapleTechLabs/maple
Path: .agents/skills/coss/SKILL.md
Commit: 8d347f8

Reviewed: about 12 hours 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.