CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

dark-mode-css

Use when reviewing stylesheets, component styles, and responsive behavior related to Support dark mode with prefers-color-scheme. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

70%

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

Quality

Content

53%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 compact, well-sectioned overview that correctly pushes executable detail to a single one-level-deep reference file. Its weaknesses are motivational padding duplicated from the reference, the absence of any code or concrete token example in the body itself, and an implicit rather than explicit check→fix→verify sequence with validation steps buried in the reference.

Suggestions

Replace the opening 'why it matters' paragraph (duplicated verbatim from references/rule.md) with a minimal executable snippet, e.g. the :root custom-property block plus the prefers-color-scheme: dark redefinition, so the core fix is actionable without opening the reference.

Make the workflow explicit and ordered (1. Check for prefers-color-scheme/data-theme usage and hard-coded colors → 2. Fix by extracting to custom properties → 3. Verify rendered layout at affected breakpoints and interaction states), surfacing the Verification steps that currently live only in references/rule.md.

Merge the overlapping Check and Code Review sections into one, and reference the rule.md sections by name (e.g. 'see the Verification and Manual Toggle sections in references/rule.md') so navigation into the reference is section-level rather than a single general pointer.

DimensionReasoningScore

Conciseness

The sectioned body is mostly lean, but the opening motivational paragraph ('More than half of users prefer dark mode for reduced eye strain... Users with photosensitivity rely on it') is padding Claude does not need and is duplicated verbatim in references/rule.md's 'Why It Matters'; the Check and Code Review sections also overlap heavily. Fits anchor 3's 'mostly efficient but includes some unnecessary explanation' better than anchor 4, since the duplication and redundant sections are noticeable rather than minor.

3 / 5

Actionability

The Quick Reference names exact techniques ('@media (prefers-color-scheme: dark)', 'CSS custom properties on :root', 'localStorage... data-theme attribute', 'WCAG contrast ratios') and Fix gives a specific approach, but the body contains no code, selectors, or token examples — all executable detail is deferred to references/rule.md. This matches anchor 3's 'some concrete guidance but incomplete; missing key details' rather than anchor 2, since the named APIs are specific rather than high-level hints.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections imply a rough sequence but are not explicitly ordered, and validation is implicit: the 'check the rendered layout... before proposing a fix' checkpoint lives in the description, while the Verification steps in references/rule.md are never surfaced in the body. This is anchor 3 ('sequence present but checkpoints missing or implicit'); it is above anchor 2 because the sections do define distinct, relevant steps, and this is not a destructive/batch operation so no hard cap applies.

3 / 5

Progressive Disclosure

The body is a short, well-organized overview with clearly labeled sections and a well-signaled, real, one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'). It falls short of anchor 5 only through minor organization gaps: the 'Why It Matters' paragraph is duplicated verbatim between body and reference, and the reference pointer sits as a plain-text path at the bottom rather than integrated navigation.

4 / 5

Total

13

/

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 and concrete review/check actions centered on dark mode. Its main weaknesses are the awkward mid-sentence rule title, a 'what' that under-represents the implementation capabilities the skill actually covers, and missing common synonyms like 'night mode' or 'theme toggle'.

Suggestions

Rewrite the trigger clause in natural phrasing, e.g. 'Use when the user mentions dark mode, night mode, theme toggling, or prefers-color-scheme, or when reviewing stylesheets for dark-mode support' — removing the jammed rule title 'related to Support dark mode with prefers-color-scheme'.

Broaden the 'what' to name the implementation capability, e.g. 'Implements dark mode via CSS custom properties and the prefers-color-scheme media query, with an optional localStorage-backed toggle, and checks rendered layout across breakpoints before proposing fixes.'

DimensionReasoningScore

Specificity

Names several concrete actions — 'reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states before proposing a fix' — but coverage is not comprehensive: implementing the fix (custom properties, toggle, contrast) is only implied by 'proposing a fix'. This sits above anchor 3 (only 1-2 actions) and below anchor 5 (comprehensive coverage).

4 / 5

Completeness

Both parts are present: an explicit trigger ('Use when reviewing stylesheets, component styles, and responsive behavior related to...') and a concrete what ('Check the rendered layout across breakpoints and interaction states before proposing a fix'). It falls short of anchor 5 because the 'what' is framed narrowly around reviewing/checking rather than the skill's full capability, and the awkwardly jammed rule title ('related to Support dark mode with prefers-color-scheme') blurs the trigger phrasing; it is clearly above anchor 3 since 'when' is explicit, not merely implied.

4 / 5

Trigger Term Quality

Includes strong natural terms users would say — 'dark mode', 'prefers-color-scheme', 'stylesheets', 'breakpoints', 'interaction states' — but misses common synonyms like 'night mode', 'theme toggle', or 'light/dark theme'. Good coverage, just short of anchor 5's comprehensive synonym/extension coverage.

4 / 5

Distinctiveness Conflict Risk

The prefers-color-scheme / dark mode focus is a clear niche, but the broad opener 'reviewing stylesheets, component styles, and responsive behavior' creates minor overlap risk with general CSS-review, responsive-design, or contrast-checking skills. Mostly distinct rather than the minimal-conflict clarity of anchor 5.

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/dark-mode-css/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.