CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

52

Quality

58%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/color-expert/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

50%

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

This is a thin catalogue pointer rather than a runnable skill: the body is concise and well-structured but provides no executable guidance and ships none of the reference material it advertises. It works as an index entry but fails as actionable instruction.

Suggestions

Either bundle the upstream references/scripts locally or replace the 'inspect the README' hand-wave with concrete install/clone commands and verified paths.

Add a minimal executable quick-start (e.g. a working OKLCH palette or contrast-check snippet) so the skill is usable without leaving SKILL.md.

Clarify the install workflow with explicit checkpoints (verify bundle present, confirm skill registered) before asking the agent to invoke it.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it avoids explaining what color science is and every line carries information, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It offers no concrete executable code or commands, only 'open https://github.com/...' and 'ask the agent to invoke this skill by name', which describes rather than instructs — the vague/abstract anchor.

1 / 3

Workflow Clarity

A loose sequence is present (inspect README, install bundle, invoke by name/trigger), but steps are shallow with no validation checkpoints; below the explicit-checklist anchor yet above missing/unclear.

2 / 3

Progressive Disclosure

Sections are well-organized, but the advertised '286K words of reference material' is not bundled here and no references/scripts/assets exist, so the disclosure promise is only partially realized.

2 / 3

Total

8

/

12

Passed

Description

67%

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 is specific and distinctive about its color-science niche but stops short of an explicit 'Use when...' trigger clause, relying on a separate triggers list for when-guidance. Tightening completeness would push it from good to excellent.

Suggestions

Add an explicit 'Use when ...' clause to the description covering palette generation, contrast/accessibility checks, and color-theory questions so when-guidance is self-contained.

Broaden the trigger terms with common phrasings users actually say (e.g. 'color picker', 'accessible colors', 'WCAG contrast', 'color scheme').

DimensionReasoningScore

Specificity

Lists multiple concrete domains — 'OKLCH/OKLAB, palette generation, accessibility/contrast, color naming, pigment mixing, and historical color theory' — matching the anchor for several specific concrete actions rather than vague language.

3 / 3

Completeness

It clearly answers 'what' but lacks an explicit 'Use when...' clause; the when-guidance exists only as a separate triggers list, so per the rubric guideline completeness is capped at 2.

2 / 3

Trigger Term Quality

The frontmatter triggers ('color theory', 'palette generator', 'color science', 'oklch palette', 'contrast check') are reasonably natural, but common user variations are missing and the description field itself contains no trigger keywords.

2 / 3

Distinctiveness Conflict Risk

It carves a clear niche (color science / OKLCH) with distinct triggers, making it unlikely to fire for an unrelated skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
Reviewed

Table of Contents

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.