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.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/unused-css/SKILL.md

Quality

Content

65%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 content is a well-structured overview with excellent progressive disclosure, but it is light on executable guidance and lacks the validation feedback loops that a batch CSS-removal workflow demands.

Suggestions

Add at least one inline copy-paste-ready example (e.g., a minimal PurgeCSS or PostCSS config snippet) so the skill is actionable without opening the reference.

Add explicit validation checkpoints to the Fix workflow: after purging, rebuild, verify the site still renders, and check for broken styles at key breakpoints.

Remove the redundancy between Quick Reference and the Check/Fix/Explain sections to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is short and mostly lean, but the Check/Fix sections restate the Quick Reference bullets and the Explain section restates why unused CSS is bad — minor over-explanation that could be trimmed.	4 / 5
Actionability	Names concrete tools (PurgeCSS, UnCSS, Chrome DevTools Coverage) and build integrations (Webpack, Vite, PostCSS), but provides no executable code or commands inline — the actionable detail is deferred to the reference file, leaving key details missing from SKILL.md.	3 / 5
Workflow Clarity	Check/Fix/Explain/Code Review sections give a rough sequence but no numbered steps or validation checkpoints; for a project-wide batch operation like CSS removal, the missing verify-build/test-rendering feedback loop caps this at 3.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with a single, clearly signaled, one-level-deep reference to references/rule.md (confirmed to exist), with well-organized sections — matching the clear-overview anchor.	5 / 5
	Total	15 / 20 Passed

Description

70%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 clearly states both what the skill does and when to use it, with mostly natural trigger terms and a distinct CSS-review niche. It could improve by adding more concrete actions and common synonyms/extensions users would actually say.

Suggestions

Add concrete remediation actions to the description (e.g., "run PurgeCSS/UnCSS and safelist dynamic classes") so specificity reaches comprehensive coverage.

Include common user-facing synonyms and file extensions in the trigger (e.g., "dead CSS", "unused selectors", ".css files", "PurgeCSS").

Tighten the "Use when" clause to name the specific outcome (reducing CSS bundle size) rather than only the review activity.

Dimension	Reasoning	Score
Specificity	Names the CSS domain and two concrete actions ("reviewing stylesheets, component styles, and responsive behavior", "Check the rendered layout across breakpoints and interaction states"), matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	Provides both an explicit "Use when..." trigger and a clear what (review stylesheets/responsive behavior, check rendered layout), but the when could be more specific and the what is review-oriented rather than action-comprehensive.	4 / 5
Trigger Term Quality	Includes natural terms like "stylesheets", "responsive behavior", "breakpoints", and "interaction states", but misses common synonyms and file extensions a user might say (e.g., "unused CSS", "dead CSS", "PurgeCSS", .css).	4 / 5
Distinctiveness Conflict Risk	Scoped to unused-CSS review with specific triggers, making it mostly distinct with only minor overlap risk against broader CSS or performance-review skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/unused-css/SKILL.md
Commit: 30756a7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.