coss-particles

Index of all COSS UI particle examples. Use when implementing UI features to find copy-paste-ready component patterns built on coss primitives. Each particle has a description and a JSON URL for easy installation.

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/coss-particles/SKILL.md

Quality

Content

71%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 a well-structured, lean index with a clear usage workflow and concrete, fetchable URLs. Its main weakness is architectural: the entire 484-particle catalog is inlined monolithically in SKILL.md rather than split across one-level-deep per-component reference files, which both inflates token cost and limits navigability.

Suggestions

Split the per-particle catalog into per-component-type reference files (e.g. references/button.md, references/dialog.md) and keep SKILL.md as a lean component-type TOC with pointers, so only the relevant ~10-40 entries load into context per use.

Add a brief note on what the fetched JSON manifest contains and a validation step for the workflow (e.g. what to do if the particle JSON is missing or depends on primitives not installed), which would also raise workflow clarity.

Remove the duplicated component-type list (the '## Component types' TOC restates every '### <type>' heading) or replace the per-section headings with anchors only, trimming redundant tokens.

Dimension	Reasoning	Score
Conciseness	The intro sections are lean with no concept over-explanation, and every per-particle line ("Basic accordion \| [JSON](...)") earns its place. Minor waste remains: the component-type TOC duplicates the section headings, and all ~640 lines of entries load into context on every skill invocation.	4 / 5
Actionability	Guidance is executable: an exact JSON URL pattern ("https://coss.com/ui/r/<particle-name>.json") with a copy-paste example, a real generator command ("node apps/ui/scripts/generate-particle-index.cjs"), and a repo path for source files. A worked example of the fetched JSON's structure and how to adapt it would make it fully copy-paste ready.	4 / 5
Workflow Clarity	A clear 4-step numbered sequence ("1. Describe the UI you need... 2. Search this index... 3. Fetch the JSON URL... 4. Adapt the particle code") with an explicit pointer to browsing visually. No validation checkpoint for the fetch step (e.g. handling a missing particle or incompatible code) prevents a 5.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), yet ~640 lines of per-particle entries are inlined in SKILL.md — content that clearly belongs in per-component-type reference files is inline, even though section structure and a TOC are present.	3 / 5
	Total	15 / 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.

A strong third-person description that explicitly states both what the skill is (an index of copy-paste-ready COSS UI particle patterns with JSON install URLs) and when to use it (when implementing UI features). Its main gap is the absence of concrete component-level trigger phrases that users would naturally say.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "Index of all COSS UI particle examples", "find copy-paste-ready component patterns", "a JSON URL for easy installation" — with only minor gaps (no mention of adapting the fetched code).	4 / 5
Completeness	Both parts are explicit: what ("Index of all COSS UI particle examples... Each particle has a description and a JSON URL") and when ("Use when implementing UI features to find copy-paste-ready component patterns"). The when-clause lacks concrete user-utterance triggers, keeping it below a 5.	4 / 5
Trigger Term Quality	"implementing UI features", "component patterns", and "copy-paste-ready" are natural phrases users would say, though common component-level terms users actually utter (button, dialog, form, tabs) are missing.	4 / 5
Distinctiveness Conflict Risk	The niche is clearly delimited by "coss primitives" and "COSS UI particles", but the broad trigger phrase "implementing UI features" carries minor overlap risk with generic UI/frontend component skills.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (738 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: crafter-station/petdex
Path: .agents/skills/coss-particles/SKILL.md
Commit: 7e32703

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