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

62%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.

A well-structured index skill with a clear lookup workflow and concrete URLs/commands, but it monolithically inlines all 484 particle entries in SKILL.md rather than splitting the catalog into a reference file, and its fetch/install guidance is incomplete. The lookup workflow itself is clear and appropriately free of validation overhead for a read-only operation.

Suggestions

Move the full 484-particle catalog into a reference file (e.g. references/particles.md) and keep SKILL.md as an overview with the component-type index, counts, and a few example entries, so SKILL.md stays a lean entry point.

Add a short example showing what a particle JSON manifest contains and the concrete step to install or adapt it (e.g. a one-line install/registry command or a minimal code snippet), so the fetch-to-usage gap is closed.

Expand the trigger guidance in the body or description with the concrete component types users name (form, dialog, tabs, autocomplete, etc.) to improve natural-term coverage beyond the generic "implementing UI features".

Dimension	Reasoning	Score
Conciseness	The intro sections are lean with no concept explanation, but the full 484-entry catalog is inlined in SKILL.md, a large token load that could be tightened by offloading the bulk listing to a reference file.	2 / 3
Actionability	Concrete artifacts are present (JSON URL pattern, example URL, source path, generator command), but guidance stops at "fetch the JSON URL to get the full source code" with no example of the manifest's contents or how to install/adapt a particle, leaving a key detail missing.	2 / 3
Workflow Clarity	The four-step "How to use this skill" sequence (describe → search → fetch → adapt) is clear and unambiguous, and the read-only index lookup involves no destructive or batch operation that would require validation checkpoints.	3 / 3
Progressive Disclosure	Organization is decent (component-type index with counts, anchor links, per-component sections), but the entire 484-particle catalog is inlined with no bundle/reference files, so content that should be separate lives in SKILL.md.	2 / 3
	Total	9 / 12 Passed

Description

85%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.

A strong, concise description that clearly states purpose, scope, and an explicit use-when trigger tied to a distinct COSS UI niche. Its only weakness is the trigger term being somewhat generic ("implementing UI features") rather than enumerating the concrete UI components it catalogs.

Dimension	Reasoning	Score
Specificity	Names concrete actions — "Index of all COSS UI particle examples", "find copy-paste-ready component patterns", and "a JSON URL for easy installation" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (index of particle examples with descriptions and JSON URLs) and when ("Use when implementing UI features to find copy-paste-ready component patterns"), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	"Use when implementing UI features" is a natural phrase but fairly generic; it lacks common variations users would say (e.g. "UI components", "build a form", specific component names), so it is not the level-3 broad coverage.	2 / 3
Distinctiveness Conflict Risk	The COSS/coss-primitives niche and "particle examples" framing give it a distinct trigger set unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 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.