CtrlK
BlogDocsLog inGet started
Tessl Logo

css-minification

Use when reviewing stylesheets, component styles, and responsive behavior related to Minify all CSS files. Check the rendered layout across breakpoints and interaction states before proposing a fix.

52

Quality

59%

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

Quality

Content

60%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 lean, well-structured single-purpose skill that correctly offloads detail to one real reference file. Its main weaknesses are conceptual padding and a lack of executable config/code examples that would make the guidance copy-paste ready.

Suggestions

Replace the conceptual opening sentence with a concrete build-config snippet (e.g., a Vite or PostCSS+cssnano config block) so the guidance is executable.

Trim the redundant Check/Fix/Explain prose to a single actionable section, keeping only what Claude would not already know.

Add a brief verification step (e.g., confirm the production bundle contains minified CSS / check file-size delta) to strengthen the workflow.

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening 'Unminified CSS wastes bandwidth with whitespace, comments...' explains a concept Claude already knows, and the Check/Fix/Explain sections overlap somewhat with Quick Reference.

3 / 5

Actionability

Names concrete tools (cssnano, lightningcss, CleanCSS, Vite, webpack) but gives no executable config or command snippets; guidance is high-level rather than copy-paste ready.

3 / 5

Workflow Clarity

The single minification task is unambiguous and the Check/Fix/Explain/Code Review sections sequence a coherent review flow; no validation checkpoint is needed for this non-destructive task, so the simple-skill exception holds.

4 / 5

Progressive Disclosure

The body is a concise overview with a single, clearly signaled one-level-deep reference to references/rule.md (which exists), and sections are well organized.

4 / 5

Total

14

/

20

Passed

Description

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

The description includes an explicit trigger and concrete review actions, but entangles the 'what' with the 'when' and omits the most natural keywords (CSS, minify). It is distinct enough but reads awkwardly due to the embedded rule title.

Suggestions

Rewrite as a clean third-person statement of what the skill does, then a separate 'Use when...' clause (e.g., 'Reviews CSS files for unminified output and checks rendered layout across breakpoints. Use when reviewing stylesheets, responsive behavior, or CSS performance.')

Add the natural trigger terms users would actually say: 'CSS', 'minify', 'minification', 'stylesheets', '.css'.

Remove the embedded rule title 'Minify all CSS files' from mid-sentence so the capability reads as a coherent action.

DimensionReasoningScore

Specificity

Names the CSS domain plus concrete review actions ('reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states'), but coverage is not comprehensive.

3 / 5

Completeness

Has an explicit 'Use when...' trigger and a what ('reviewing ... related to Minify all CSS files', 'Check ... before proposing a fix'); both are present though the 'what' is awkwardly entangled with the trigger.

4 / 5

Trigger Term Quality

Relevant keywords like 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'interaction states' are present, but common natural terms ('CSS', 'minify', file extensions) are missing.

3 / 5

Distinctiveness Conflict Risk

The CSS-minification niche is somewhat specific, but the broad 'reviewing stylesheets and responsive behavior' framing could overlap with general CSS or layout-review skills.

3 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.