CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

color-oklch

Use when building a design token system, creating accessible colour palettes, generating colour ramps programmatically, or migrating a design system to support wide-gamut displays.

Quality

79%

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-oklch/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A clean, well-structured overview that delegates implementation detail appropriately to a single real reference file. Its weaknesses are the absence of any inline executable example (even one oklch token or gamut media query) and a fix workflow with no verification step, plus a colour-theory intro that partly re-explains what Claude already knows.

Suggestions

Add one small inline code example in the Fix section — e.g., an oklch() custom-property token pair and the @media (color-gamut: p3) override — so the body's guidance is executable without opening the reference file.

Include a verification checkpoint in the Fix workflow, such as confirming equal perceived lightness across shade steps (or a contrast check for accessible palettes) after conversion.

Trim the opening paragraph's background on sRGB/HSL perceptual non-uniformity to a single sentence, since Claude already knows this and the reference file restates it in full.

DimensionReasoningScore

Conciseness

The ~45-line body is lean with no padding, but the opening paragraph restates colour science Claude already knows ('HSL and hex colours are defined in the sRGB colour space, which is not perceptually uniform...') and the Quick Reference repeats ideas from the intro. Fits anchor 4: efficient with minor over-explanation that could be trimmed; not 5 because some of the explanation is redundant with Claude's existing knowledge.

4 / 5

Actionability

The body gives verbal direction ('Define your colour palette tokens in oklch custom properties', 'Convert the colour token palette from hsl/hex to oklch') with only one concrete spec ('Use @media (color-gamut: p3)'); all executable code is deferred to references/rule.md and nothing in the body is copy-paste ready. Fits anchor 3: some concrete guidance but incomplete; not 4 because there is no executable code or command inline.

3 / 5

Workflow Clarity

As a simple single-purpose review skill, the Check → Fix → Explain → Code Review structure makes the single action (flag hsl/hex token palettes, convert to oklch) unambiguous, so the simple-skill exception applies — but the Fix step includes no validation checkpoint (e.g., verifying perceived-lightness consistency or contrast after conversion). Fits anchor 4: clear sequence with most checkpoints, minor validation gaps; not 5 because no verification step is given.

4 / 5

Progressive Disclosure

A short, well-sectioned overview with one clearly signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), which is a real bundle file containing the code examples. This matches the anchor-5 pattern exactly: clear overview, well-signaled single reference, easy navigation.

5 / 5

Total

16

/

20

Passed

Description

80%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 strong description with explicit, well-scoped trigger conditions and multiple concrete actions. Its main weakness is that the 'what' is carried entirely by the trigger list — the central subject (oklch/oklab CSS colour functions) is never mentioned — and it only uses the British 'colour' spelling, missing the US-spelling trigger terms many users would type.

DimensionReasoningScore

Specificity

Lists four concrete actions ('building a design token system', 'creating accessible colour palettes', 'generating colour ramps programmatically', 'migrating a design system to support wide-gamut displays'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Explicit 'Use when...' clause covers 'when' thoroughly, and the gerund list conveys the domain tasks ('what'), but the core technique — oklch()/oklab() CSS colour functions — is never named, so the 'what' is implied rather than explicit. Fits anchor 4 (both present, one less specific) rather than 5; not 3 since the trigger list does concretely describe the skill's activities.

4 / 5

Trigger Term Quality

Good natural keywords ('design token system', 'colour palettes', 'wide-gamut displays') but misses common variations — notably the US spelling 'color' (only British 'colour' appears) and adjacent terms like 'CSS variables' or 'theme'. Fits anchor 4: good coverage with a few natural terms missing, not 5.

4 / 5

Distinctiveness Conflict Risk

Niche triggers ('wide-gamut displays', 'colour ramps programmatically') make it mostly distinct with only minor overlap risk against general accessibility/contrast-checking skills via 'accessible colour palettes'. Fits anchor 4; not 5 because that phrase could overlap with dedicated contrast-checking skills.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/color-oklch/SKILL.md

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.