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

54%

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

47%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 tidy, brief catalogue entry, but as a SKILL.md it is a stub: it defers all real guidance to an external repo without giving a concrete install command or any executable color-science instruction. A reader cannot act on it without leaving the skill entirely.

Suggestions

Replace the 'open <url>' hint with a concrete, cross-platform install step (e.g., a 'git clone' command plus the target skills-directory path).

Inline a minimal quick-start example (e.g., generating a small OKLCH palette or checking a contrast ratio) so the skill is usable without fetching the upstream bundle.

State explicitly that no local references/scripts/assets ship with this entry, so the '286K words of reference material' claim is not mistaken for on-disk content.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean with clear sections and no padding; the only trimmable redundancy is 'What it does' repeating the frontmatter description verbatim.	4 / 5
Actionability	The sole command is 'open https://github.com/meodai/skill.color-expert', which merely inspects and is not executable on all platforms; the central instruction 'install the upstream bundle into your active agent's skills directory' has no concrete command or path. Not 3 because no executable guidance exists for the skill's actual purpose.	2 / 5
Workflow Clarity	A rough sequence is present (inspect upstream, install the bundle, invoke by name or trigger phrase), but the install step itself is undefined and there are no checkpoints. Not 3 because the gaps are in the step definitions, not merely in validation.	2 / 5
Progressive Disclosure	For a sub-50-line stub, sections are clean and the one reference (the upstream repo link) is clearly signaled and one level deep; however, no local bundle files exist to back the '286K words of reference material' the body advertises.	4 / 5
	Total	12 / 20 Passed

Description

61%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 communicates scope through a concrete topic inventory and is backed by natural trigger phrases, but it never states what the skill actually does in action terms and lacks an explicit 'Use when...' clause. It reads as a content catalogue blurb rather than a capability statement.

Suggestions

Rewrite the description in third-person action form (e.g., 'Generates OKLCH palettes, checks contrast ratios for accessibility, and names/mixes colors...') instead of listing topics with 'covering'.

Add an explicit 'Use when...' clause naming the trigger scenarios (e.g., 'Use when generating color palettes, checking WCAG contrast, or converting colors to OKLCH').

Broaden the trigger list with common synonyms such as 'color palette', 'accessible colors', and 'WCAG contrast'.

Dimension	Reasoning	Score
Specificity	The description names the domain concretely ('covering OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory') but uses no action verbs — it is a topic inventory rather than a list of what the skill does, matching anchor 3 rather than 4.	3 / 5
Completeness	A clear 'what' is present ('286K words of reference material covering...') but the description itself has no 'Use when...' clause, capping completeness at 3 per the judging guideline; the separate frontmatter triggers list keeps it above 2.	3 / 5
Trigger Term Quality	The frontmatter triggers ('color theory', 'palette generator', 'oklch palette', 'contrast check') are natural phrases a user would say, but common variations like 'color palette', 'accessible colors', or 'WCAG' are missing.	4 / 5
Distinctiveness Conflict Risk	Color science is a clear niche with distinct triggers like 'oklch palette', with only minor overlap risk against general design/palette skills.	4 / 5
	Total	14 / 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: 1b47e60

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