color-contrast-checker
Color Contrast Checker - Auto-activating skill for Frontend Development. Triggers on: color contrast checker, color contrast checker Part of the Frontend Development skill category.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill color-contrast-checkerOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It repeats the skill name as trigger terms and fails to describe what the skill actually does or when Claude should use it. The description relies entirely on the skill name to convey meaning rather than providing actionable details.
Suggestions
Add specific actions the skill performs, e.g., 'Checks color combinations against WCAG accessibility standards, calculates contrast ratios, and suggests accessible color alternatives.'
Include a 'Use when...' clause with natural trigger scenarios like 'Use when checking if text is readable against backgrounds, verifying WCAG compliance, or when users mention accessibility, contrast ratio, or color readability.'
Expand trigger terms to include natural variations: 'accessibility', 'WCAG', 'readable text', 'contrast ratio', 'a11y colors', 'text visibility'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Color Contrast Checker') without describing any concrete actions. It doesn't explain what the skill actually does - no mention of checking contrast ratios, WCAG compliance, suggesting alternatives, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and provides no explicit 'when to use' guidance. The 'Triggers on' section is just the skill name repeated, not meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('color contrast checker' listed twice) and lack natural variations users might say like 'accessibility', 'WCAG', 'readable colors', 'contrast ratio', or 'a11y'. | 1 / 3 |
Distinctiveness Conflict Risk | The skill name 'Color Contrast Checker' is fairly specific to a niche function, which provides some distinctiveness. However, without describing actual capabilities, it could still conflict with general accessibility or color-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill is entirely placeholder content with no actual substance. It contains zero information about how to check color contrast - no WCAG guidelines, no contrast ratio calculations, no code examples, no tools. The content is generic boilerplate that could apply to any skill topic by simply swapping the phrase 'color contrast checker'.
Suggestions
Add the WCAG contrast ratio requirements (4.5:1 for normal text, 3:1 for large text) and the formula for calculating relative luminance
Include executable code examples showing how to calculate contrast ratios between two colors (e.g., using hex values)
Provide concrete tool recommendations or library code (e.g., using the `color-contrast` npm package or a Python implementation)
Add example inputs and outputs showing color pairs that pass/fail accessibility thresholds
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual information about color contrast checking. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler that waste tokens. | 1 / 3 |
Actionability | There is zero concrete guidance - no code, no formulas for calculating contrast ratios, no WCAG thresholds, no tools or libraries mentioned. The skill describes what it claims to do rather than actually instructing how to check color contrast. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. A color contrast checker skill should include steps like: get color values, calculate relative luminance, compute contrast ratio, compare against WCAG thresholds. None of this is present. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic placeholder text with no meaningful structure. There are no references to detailed materials, no examples, and no organized sections with actual content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
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.