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

77%

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

Fix and improve this skill with Tessl

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

Quality

Content

77%

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

The skill is highly actionable with a clear usage workflow and concrete URLs/commands. Its main weakness is progressive disclosure and conciseness: the entire 480-particle catalog is inlined in SKILL.md rather than referenced as a separate, navigable file.

Suggestions

Move the full enumerated particle catalog into a separate references file (e.g. PARTICLES.md) and keep SKILL.md as a concise overview that links to it, preserving only the component-type index and counts inline.

Confirm the referenced source path and generator script actually exist in the bundle, or note clearly that they live in the external coss repo so Claude is not directed to look for missing local files.

Dimension	Reasoning	Score
Conciseness	The how-to, URL pattern, source, and update sections are lean, but the full 480-entry particle catalog is inlined directly in SKILL.md; while it is functional data rather than explanatory fluff, the volume is large and could be trimmed or moved.	2 / 3
Actionability	Provides copy-paste-ready, executable specifics: the JSON URL pattern with an example, the repo path, and a concrete generator command, plus a clear 4-step usage sequence.	3 / 3
Workflow Clarity	The "How to use this skill" section gives a clear, unambiguous 4-step sequence; this is a low-risk lookup/install task so absent validation checkpoints are not penalized.	3 / 3
Progressive Disclosure	No bundle files exist and the body is well-organized with an anchor-linked component-type index, but at ~737 lines the bulk is an inline catalog that would be better split into a separate references file rather than kept monolithic in SKILL.md.	2 / 3
	Total	10 / 12 Passed

Description

77%

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 concise third-person description that clearly states both capability and an explicit trigger. It is specific and complete, but trigger-term coverage and distinctiveness are limited by reliance on the specialized "coss" brand and a somewhat generic UI trigger.

Suggestions

Broaden trigger terms with natural synonyms users would say, e.g. "UI components", "widgets", "design system", or "component library".

Sharpen the trigger to reduce conflict with general UI skills, e.g. "Use when building UI with the coss component library and you need a ready-made pattern."

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Index of all COSS UI particle examples", "find copy-paste-ready component patterns", "a description and a JSON URL for easy installation" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what it does (index of copy-paste-ready particle patterns with JSON URLs) and when to use it via an explicit "Use when implementing UI features..." trigger clause.	3 / 3
Trigger Term Quality	Has natural terms like "implementing UI features" and "component patterns", but leans on the specialized brand term "coss/particle" and omits common variations such as "UI components", "widgets", or "design system".	2 / 3
Distinctiveness Conflict Risk	The coss/particle niche is reasonably specific, but the broad trigger "implementing UI features" could overlap with general UI or design-system skills.	2 / 3
	Total	10 / 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 (737 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: MapleTechLabs/maple
Path: .agents/skills/coss-particles/SKILL.md
Commit: 8d347f8

Reviewed: about 13 hours 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.