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

81%

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

75%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 skill is highly actionable and well-structured for finding copy-paste component patterns, with concrete URLs and commands. Its main weakness is conciseness and progressive disclosure: the entire 480-entry catalog is inlined as a long repeated listing rather than offloaded to a bundled reference.

Suggestions

Move the full 480-particle catalog into a bundled reference file (e.g. references/particles.md) and keep SKILL.md as an overview pointing to it, reversing the inlining that hurts conciseness and progressive_disclosure.

Compress the per-component particle listings in the overview to representative examples plus counts, since the component-type index already enumerates every type with tallies.

Add a short note on how to adapt a fetched particle (e.g. dependency install step or import expectation) so the final 'adapt the particle code' step is as concrete as the fetch step.

Dimension	Reasoning	Score
Conciseness	The prose sections (how-to, JSON URL pattern, update instructions) are lean, but the ~700-line verbatim catalog of 480 particles repeats the same line pattern hundreds of times, inlining bulk content that consumes significant context tokens.	3 / 5
Actionability	Provides the exact JSON URL pattern with a concrete example, the precise generator script command, the source-file repo path, and a numbered usage flow that is directly executable.	5 / 5
Workflow Clarity	The four-step "How to use" sequence is clearly ordered and unambiguous for a single-purpose lookup skill; no destructive or batch operations require validation checkpoints, so the absence of explicit validation does not lower it further.	4 / 5
Progressive Disclosure	Good structure with a component-type index (with counts), per-component sections, and one-level-deep JSON links plus a clear external browse URL and repo path; the main gap is that the full 480-particle catalog is inlined in SKILL.md rather than split into a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

87%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 concise, third-person description that clearly states what the skill provides and when to use it, anchored to a distinct niche. It is slightly shy of full marks only on trigger-term breadth and action comprehensiveness.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions ("Index of all COSS UI particle examples", "find copy-paste-ready component patterns", "JSON URL for easy installation"), with only minor gaps in coverage rather than a comprehensive action list.	4 / 5
Completeness	Explicitly answers both what ("Index of all COSS UI particle examples ... copy-paste-ready component patterns built on coss primitives") and when ("Use when implementing UI features to find ... patterns") with concrete trigger phrasing.	5 / 5
Trigger Term Quality	"Use when implementing UI features" is a natural trigger phrase and "component patterns" is relevant, but common component-level synonyms a user would say (form, dialog, tabs, component library) and the .json extension are missing.	4 / 5
Distinctiveness Conflict Risk	The scoped COSS/coss-primitives niche with particle-specific terminology gives a clear, distinct trigger set with minimal overlap risk against unrelated skills.	5 / 5
	Total	18 / 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 (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: db18120

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.