CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-custom-properties

Use when reviewing stylesheets, component styles, and responsive behavior related to Use CSS custom properties for design tokens. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

72%

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/css-custom-properties/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 overview with an excellent one-level reference split to references/rule.md. It loses points for restating CSS fundamentals Claude already knows (intro + Quick Reference), lacking in-body executable detail or a detection method, and omitting post-fix validation for what is a batch find-and-replace operation.

Suggestions

Trim the intro paragraph and the 'Quick Reference' section — Claude already knows custom properties cascade/inherit and var() fallback syntax; keep only the rule-specific directives.

Add a post-fix validation step to the Fix workflow (e.g., 'After replacing usages, verify the rendered layout is unchanged across breakpoints and interaction states') to create a feedback loop for this batch edit.

Add a concrete detection method or minimal before/after code snippet to the Check section (e.g., grep for hex colors and px/rem literals) so the guidance is executable without opening the reference file.

DimensionReasoningScore

Conciseness

The intro paragraph ("Hard-coded color values and magic numbers scattered across CSS files make global changes... require finding and updating dozens of individual lines") and the Quick Reference bullets ("Custom properties cascade and inherit", "Use var(--name, fallback) to provide fallback values") restate CSS fundamentals Claude already knows. The Check/Fix/Review directives themselves are tight, so this is more 'some unnecessary explanation' (anchor 3) than 'several padded sections' (anchor 2).

3 / 5

Actionability

Check and Fix give concrete direction ("Find hard-coded color values, spacing values, and font sizes", "Extract repeated and meaningful values into CSS custom properties on :root and replace all usages with var() references") but include no detection method (grep pattern, devtools check) and no in-body code example — the executable specifics are entirely deferred to references/rule.md. This sits between anchor 2's high-level hints and anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clearly ordered, but the Fix step ('replace all usages with var() references') is a batch edit with no post-fix validation — the rendered-layout check appears only in the description, not in the workflow. Per the batch-operation cap, workflow clarity cannot exceed 3 without a feedback loop.

3 / 5

Progressive Disclosure

A short (~45 line) overview body with a single clearly signaled, one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists and contains the full implementation with code examples. Content is appropriately split with easy navigation, matching anchor 5.

5 / 5

Total

14

/

20

Passed

Description

75%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 solid description with an explicit 'Use when' clause, a clearly named domain, and several concrete actions. Main gaps are missing common synonyms ('CSS variables', 'theming') and a when-clause framed as tasks rather than natural user trigger phrases.

DimensionReasoningScore

Specificity

Names the domain ("stylesheets, component styles, and responsive behavior", "CSS custom properties for design tokens") and lists several concrete actions ("reviewing", "Check the rendered layout across breakpoints and interaction states before proposing a fix"). It falls short of anchor 5 because the core remediation action (extracting hard-coded values into tokens) is only implied via the embedded title phrase, not stated as a capability.

4 / 5

Completeness

Both parts are present: the what (reviewing stylesheets/component styles/responsive behavior, checking rendered layout across breakpoints and interaction states) and an explicit when ("Use when reviewing stylesheets, component styles, and responsive behavior related to..."). It is not anchor 5 because the when-clause describes tasks rather than concrete user-facing trigger phrases (e.g., 'when the user mentions CSS variables, hard-coded colors, or theming').

4 / 5

Trigger Term Quality

Good natural keyword coverage: "stylesheets", "component styles", "responsive behavior", "breakpoints", "design tokens". A few natural terms users would say are missing — the synonym "CSS variables", "theming"/"dark mode", and file extensions like .css — so it matches anchor 4 rather than 5, and is clearly above anchor 3's 'some relevant keywords' since multiple natural phrases are present.

4 / 5

Distinctiveness Conflict Risk

Scoped to a distinct niche — CSS custom properties/design tokens — with specific triggers like "breakpoints" and "design tokens", so conflict risk is minor. It is not anchor 5 because "reviewing stylesheets, component styles, and responsive behavior" is broad enough to overlap with general CSS-review or theming skills.

4 / 5

Total

16

/

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/css-custom-properties/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.