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

Low

Low-risk findings worth noting

Quality

Content

85%Weight 40%Scale 1-3

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

The content is a well-structured navigation/index skill with lean prose, a clear workflow, an output checklist, and verified one-level-deep references. Its only weakness is actionability: most concrete code lives in external reference files and the manual install guidance is prose rather than executable detail.

Suggestions

Add a minimal inline import/composition example (e.g. a Dialog trigger/content skeleton) so the body is copy-paste ready without first opening a reference file.

Expand the manual-install bullets with a concrete example dependency line and an import-rewrite snippet rather than prose-only steps.

Collapse the overlapping guidance between 'Principles for agent output' and 'Critical usage rules' to remove mild redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what a component library is or how Tailwind works; every section (rules, discovery, workflow, checklist) serves navigation or instruction. It is not below 3 because there is no concept-padding, only occasional mild overlap between 'Principles for agent output' and 'Critical usage rules'.	3 / 3
Actionability	Provides a copy-paste CLI snippet ('npx shadcn@latest add @coss/<component>') and a concrete 6-step workflow, but most guidance directs to reference files and the manual-install path is prose bullets ('install dependencies listed in the component docs page', 'copy required component file(s)') rather than executable detail. Not 3 because the body is not copy-paste ready throughout; not 1 because the CLI command and workflow are concrete.	2 / 3
Workflow Clarity	A clear sequenced 6-step 'Usage workflow' is paired with an 'Output Checklist' that acts as an explicit verification gate before returning code (imports/props match, composition valid, a11y present, migration flows verified). The task is UI-code authoring, not a destructive/batch operation, so the checklist suffices as the feedback loop.	3 / 3
Progressive Disclosure	The body is a well-organized overview pointing one level deep to verified real files: 53 primitive guides under references/primitives/, rules/ guides, cli.md, component-registry.md, and portal-props.md, with a registry index for discovery. Not below 3 because references are clearly signaled, single-level, and the overview content is appropriately split out.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong: it names concrete actions, includes natural trigger terms, explicitly answers both what and when, and occupies a distinct niche. It is concise without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions: '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', and 'troubleshooting coss component behavior'. Matches the anchor for listing several specific concrete actions.	3 / 3
Completeness	Explicitly states both what ('Helps implement coss UI components correctly', 'Covers imports, accessibility, Tailwind styling, and common pitfalls') and when ('Use when building UIs with coss primitives..., migrating..., composing trigger-based overlays, or troubleshooting...'). Matches the anchor for clearly answering both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Uses natural user vocabulary ('buttons, dialogs, selects, forms, menus, tabs, inputs, toasts', 'shadcn/Radix', 'Tailwind styling') a user would say when needing this skill. Not below 3 because common component-name variations are well covered; no first/second-person pronouns are present to penalize.	3 / 3
Distinctiveness Conflict Risk	The niche is clearly scoped to coss primitives and 'migrating from shadcn/Radix to coss/Base UI', with distinct triggers unlikely to fire for unrelated skills. Matches the clear-niche anchor.	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: crafter-station/petdex
Path: .agents/skills/coss/SKILL.md
Commit: 2d6b567

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