CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

69

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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-structured overview skill that leans on a real, verified bundle of one-level-deep references and provides a concrete workflow plus output checklist. Main weaknesses are mild redundancy between the Principles and Critical usage rules sections and the lack of an explicit error-recovery feedback loop.

Suggestions

Consolidate overlapping guidance between the 'Principles for agent output' and 'Critical usage rules' sections to remove redundancy (e.g., 'use existing primitives first' vs 'do not invent coss APIs').

Add an explicit validate→fix→retry feedback loop in the Usage workflow (e.g., 'if the self-check fails, revise imports/composition and re-check before returning code').

Merge the 'Component discovery' and 'Primitive Guidance' sections, which both restate that every primitive has a guide at ./references/primitives/<name>.md and point to the component registry.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding concept explanations, but the Principles and Critical usage rules sections overlap ('Use existing primitives first' vs 'Do not invent coss APIs') and component-discovery guidance is restated in the Primitive Guidance section.

4 / 5

Actionability

Provides concrete executable guidance — 'npx shadcn@latest add @coss/<component>', specific particle file paths 'p-<name>-<N>.tsx', and explicit reference paths — though most copy-paste code lives in the referenced files rather than inline.

4 / 5

Workflow Clarity

A clear numbered 6-step Usage workflow and an Output Checklist provide a well-sequenced process with a self-check checkpoint, but there is no explicit validate→fix→retry feedback loop for error recovery.

4 / 5

Progressive Disclosure

SKILL.md is a well-organized overview with clearly signaled one-level-deep references (./references/primitives/*.md, ./references/rules/*.md, component-registry, cli, portal-props), all of which exist as real files, making navigation easy.

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 strong, third-person description that concretely states capabilities and provides explicit 'Use when' trigger guidance covering building, migrating, composing, and troubleshooting. Only minor gap is the absence of file-extension/synonym trigger terms.

DimensionReasoningScore

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), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly answers 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...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage with concrete component names (buttons, dialogs, selects, forms, menus, tabs, inputs, toasts) and synonym pairs (shadcn/Radix, coss/Base UI), but lacks file extensions or further synonym variations that would push it to the top anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (coss component library on Base UI) with distinct triggers (coss primitives, shadcn/Radix migration) and minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
crafter-station/petdex
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.