CtrlK
BlogDocsLog inGet started
Tessl Logo

unused-css

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

58

Quality

67%

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

Quality

Content

57%

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 well-structured, progressive-disclosure-friendly overview that points cleanly to one reference, but it lacks executable guidance and validation checkpoints, relying on naming tools rather than giving copy-paste-ready steps.

Suggestions

Add at least one executable example (e.g., a PurgeCSS/PostCSS config snippet or CLI command) so the body is actionable without forcing a jump to the reference.

Include an explicit sequenced workflow with a validation checkpoint — e.g., after purging, verify the site renders across breakpoints; if styles break, expand the safelist and re-run.

Trim the motivation intro and the meta "Explain" section, and de-duplicate the overlapping Check and Fix content, to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is short, but the intro motivation sentence ("Most projects use only 10-25% of their CSS...") and the meta "Explain" section state things Claude already knows, and the Check and Fix sections overlap — it could be tightened.

2 / 3

Actionability

Names concrete tools (PurgeCSS, UnCSS, Chrome DevTools Coverage, Webpack, Vite, PostCSS) but provides no executable commands, config snippets, or safelist examples; all copy-paste-ready content is deferred to references/rule.md, leaving key details missing.

2 / 3

Workflow Clarity

The Check→Fix sections imply a loose sequence, but there is no explicit step ordering and no validation/feedback loop (e.g., verify rendering after purging, expand safelist on breakage) for a batch operation that can break styles, capping clarity at 2.

2 / 3

Progressive Disclosure

A concise overview with well-organized sections that clearly signals a single one-level-deep reference (references/rule.md, verified to exist) for full implementation details, matching the well-signaled one-level-deep anchor.

3 / 3

Total

9

/

12

Passed

Description

77%

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 has an explicit Use-when trigger and names concrete actions, but its trigger terms and action framing drift toward responsive-design review rather than the skill's actual unused-CSS-removal purpose, raising conflict risk.

Suggestions

Replace the responsive-layout framing with unused-CSS-specific actions (e.g., "Identify and purge unused selectors, safelist dynamic classes, integrate removal into the build pipeline") so the description matches the skill's purpose.

Add natural trigger terms users would say for this task, such as "dead CSS", "CSS bundle size", "PurgeCSS", or "Chrome DevTools Coverage".

Drop "responsive behavior" and "interaction states" from the trigger clause to reduce overlap with responsive-design review skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "reviewing stylesheets, component styles, and responsive behavior", "Check the rendered layout across breakpoints and interaction states", and "proposing a fix" — matching the multiple-specific-actions anchor.

3 / 3

Completeness

Explicit "Use when reviewing stylesheets..." trigger answers when, and "Check the rendered layout... before proposing a fix" answers what, satisfying both halves with an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes some natural terms ("unused CSS", "stylesheets", "breakpoints") but several ("responsive behavior", "interaction states") belong to responsive-design rather than unused-CSS removal, and common variations like "dead CSS", "PurgeCSS", or "bundle size" are missing.

2 / 3

Distinctiveness Conflict Risk

The "Remove unused CSS rules" anchor is a distinct niche, but the responsive-layout/breakpoint language is tangential to unused-CSS removal and could overlap with general CSS or responsive-review skills.

2 / 3

Total

10

/

12

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.