color-expert

Color science expert skill with 286K words of reference material covering OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory.

Quality

57%

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 ./skills/color-expert/SKILL.md

Quality

Content

61%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 clean, well-structured catalogue entry that efficiently points users to the upstream bundle, but it functions mostly as a pointer — actual executable guidance and the bulk of the reference material live in the external repository rather than in the skill. Structure and brevity are good; substance is thin.

Suggestions

Add a minimal local quick-start example (e.g. a one-line OKLCH palette or contrast check) so the skill is usable without first consulting the upstream README.

Replace or supplement the external URL with a clearly signaled local reference file path when the upstream bundle is installed, so navigation is one level deep.

Tighten the 'How to use' steps into an explicit ordered sequence with the concrete install command rather than 'inspect the upstream README for exact paths'.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows; the only padding is the verbatim re-print of the frontmatter description under 'What it does' and the marginal 'Curated from @meodai' line.	4 / 5
Actionability	It gives one concrete command (`open https://github.com/meodai/skill.color-expert`) and clear high-level steps, but the real executable guidance is deferred to the upstream README, so the skill itself does not provide the specific steps to perform its capabilities.	3 / 5
Workflow Clarity	A rough sequence is present (inspect upstream README, install the bundle, invoke by name or triggers), but the steps are loose and the 'inspect the upstream README for exact paths' step leaves the actual follow-up implicit; no checkpoints are needed since this is not a destructive or batch operation.	3 / 5
Progressive Disclosure	Sections are well-organized with clear headers and the external reference is clearly signaled, but no local reference files exist and the advertised '286K words of reference material' is only reachable via an external URL rather than one-level-deep local references.	4 / 5
	Total	14 / 20 Passed

Description

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

The description clearly conveys the skill's domain and breadth of reference material but reads as a content inventory rather than a statement of capabilities, and lacks any explicit 'when to use' guidance. It is distinctive but not yet actionable as a trigger description.

Suggestions

Reframe the description around concrete actions (e.g. 'Generate OKLCH palettes, check WCAG contrast, name and mix pigments') rather than describing reference material coverage.

Add an explicit 'Use when...' clause naming the natural trigger phrases a user would say (palette generation, contrast checking, OKLCH conversion).

Fold the most relevant trigger terms and any file extensions into the description itself instead of relying solely on the separate `triggers:` field.

Dimension	Reasoning	Score
Specificity	The description names the color-science domain and several concrete sub-areas ('OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory'), but frames them as topics the reference material 'covers' rather than concrete actions the skill performs.	3 / 5
Completeness	It gives a clear 'what' (a color science expert skill with reference material across named topics) but offers no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It surfaces some natural terms a user might say ('palette generation', 'contrast'), but misses common variations, synonyms, and file extensions; the explicit trigger phrases live in the separate `triggers:` field rather than the description itself.	3 / 5
Distinctiveness Conflict Risk	The niche is fairly distinct — 'color science expert' anchored by specialized terms like OKLCH and pigment mixing — with only minor overlap risk against general design/brand skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/color-expert/SKILL.md
Commit: 1a7a23d

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