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

85%

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

78%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-organized overview skill: progressive disclosure is exemplary with verified one-level-deep references, and the workflow plus output checklist give clear sequencing and validation. Slight conciseness redundancy and minimal inline executable code keep it from the top band on those dimensions.

Suggestions

Merge the 'Component discovery' and 'Primitive Guidance' sections into one to remove the duplicated registry/primitive-guide pointers and reduce token cost.

Add one small inline copy-paste primitive example (e.g. a Dialog trigger/content snippet) so the body is self-sufficient for the most common case without requiring a reference read.

Make the validation feedback loop explicit in the workflow, e.g. step 6.1 'If a check fails, fix imports/composition/a11y and re-run the checklist before returning code.'

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence with no concept-explaining padding, but 'Component discovery' and 'Primitive Guidance' overlap (both re-point to the registry/primitive guides) and 'Principles' slightly overlaps 'Critical usage rules', leaving minor tightening room.	4 / 5
Actionability	Provides a concrete CLI command, real particle file-path patterns, and a workflow, but the body itself carries minimal executable component code — actual usage examples are delegated to the reference files, leaving minor gaps for direct copy-paste use.	4 / 5
Workflow Clarity	A clear 6-step sequenced workflow with a self-check step and a reinforcing Output Checklist; falls short of 5 only because the 'if check fails, fix and re-verify' feedback loop is implied rather than spelled out.	4 / 5
Progressive Disclosure	SKILL.md is a genuine overview that splits detail into one-level-deep, clearly signaled references (rules/, primitives/<name>.md, cli.md, component-registry.md, portal-props.md), all verified present, with high-risk primitives called out and a registry index for navigation.	5 / 5
	Total	17 / 20 Passed

Description

92%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 well-crafted description: third-person voice, concrete capabilities, an explicit multi-trigger 'Use when' clause, and a distinct niche anchored to the coss/Base UI ecosystem. Minor keyword-synonym gaps keep trigger_term_quality just below a perfect score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and coverage areas — 'Helps implement coss UI components', 'migrating from shadcn/Radix', 'composing trigger-based overlays', 'troubleshooting', and 'Covers imports, accessibility, Tailwind styling, and common pitfalls' — comprehensive rather than abstract.	5 / 5
Completeness	Explicitly answers both 'what' (implement coss UI components correctly, covering imports/a11y/Tailwind/pitfalls) and 'when' with a concrete 'Use when...' clause enumerating building, migrating, composing, and troubleshooting triggers.	5 / 5
Trigger Term Quality	Strong natural keyword coverage ('buttons, dialogs, selects, forms, menus, tabs, inputs, toasts', 'shadcn/Radix', 'trigger-based overlays') that users would actually say, but misses a few common synonyms (e.g. 'modal', 'dropdown') that would round out coverage.	4 / 5
Distinctiveness Conflict Risk	Clear niche tied to the coss/Base UI ecosystem and the named shadcn/Radix migration path, with triggers specific enough to avoid firing for unrelated UI skills.	5 / 5
	Total	19 / 20 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: 3cb9193

Reviewed: 1 day 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.