CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-file-size

Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize CSS file size. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

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

Quality

Content

71%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 well-structured, brief overview with a concrete audit threshold, a Check→Fix workflow with an up-front measurement checkpoint, and an exemplary one-level-deep pointer to a reference file that actually contains the executable code. Its main weakness is redundancy: the opening CSSOM sentence and the free-standing 'Explain' section teach Claude things it already knows, and there is no step to re-measure after applying fixes.

Suggestions

Delete the opening sentence about render-blocking and CSSOM construction (Claude already knows this) or compress it to a fragment in the Check section.

Remove or fold the 'Explain' section into the Check/Fix steps instead of devoting a section to explaining a concept Claude already understands.

Close the workflow loop: add a post-fix re-measurement step (e.g. re-run Lighthouse or re-check gzip size after minifying/purging) to confirm the change actually improved the metric.

DimensionReasoningScore

Conciseness

The body is mostly efficient (short bullet lists, a one-line Check criterion), but it includes unnecessary explanation of concepts Claude already knows: the opening sentence "Large CSS files block rendering and increase the time it takes for the browser to construct the CSSOM, leading to a slower First Contentful Paint" and the entire "Explain" section ("Explain how CSS file size affects the critical rendering path and browser performance") restate common knowledge. Not score 2 because the padding is limited to these two spots rather than pervasive; not score 4 because both the intro and the Explain section could be trimmed outright.

3 / 5

Actionability

The guidance is mostly executable: a concrete measurable threshold ("exceeding recommended limits (e.g., > 50KB gzipped)"), named tools ("minification and remove unused CSS (PurgeCSS)", "modular CSS or Tailwind"), and a specific verification method ("DevTools, Lighthouse, or field data"), with copy-paste-ready code deferred to the verified `references/rule.md`. Per the rubric's instruction-only note, absence of inline code is not penalized since the guidance is actionable; not score 5 because the body gives no quick inline command or config snippet for the most common case, pushing all execution details one hop away.

4 / 5

Workflow Clarity

There is a clear Check → Fix sequence with a measurement checkpoint ("Audit the size of CSS files and identify those exceeding recommended limits") and the Code Review section demands evidence ("describe the measurement method used to confirm the issue"). Not score 3 because the sequence is coherent and a validation step exists up front; not score 5 because there is no post-fix verification loop (re-measuring after minifying/purging) to confirm the fix worked.

4 / 5

Progressive Disclosure

The body is a concise ~30-line overview and defers all implementation detail through a single, clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists in the bundle (87 lines with executable PurgeCSS/postcss configs). No nested references, no content that should be split out is inlined; this matches the anchor-5 pattern of a clear overview with well-signaled references.

5 / 5

Total

16

/

20

Passed

Description

57%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 has an explicit, well-formed trigger clause with good natural keywords and concrete tool references, but it never states what the skill actually does — the optimization capabilities (minify, purge unused CSS, split stylesheets) are absent, leaving the "what" implied rather than declared. Its broad performance triggers ("slow page loads", "heavy assets") also create real overlap risk with other front-end performance skills.

Suggestions

Open the description with an explicit capability statement in third person before the 'Use when' clause, e.g. 'Minifies CSS, removes unused styles, and splits large stylesheets. Use when auditing slow page loads... related to CSS file size.'

Add missing natural trigger terms and synonyms such as 'stylesheets', 'unused CSS', 'minify CSS', or 'render-blocking CSS' so the trigger coverage matches the anchor-5 pattern.

Tie the trigger conditions more tightly to CSS (e.g. 'slow page loads traced to large or render-blocking CSS') to reduce conflict with sibling performance skills like JS bundle or image optimization.

DimensionReasoningScore

Specificity

The description names the domain and 1-2 concrete actions — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data" — with specific tool names, but it never states the skill's core capabilities (minifying CSS, purging unused styles, splitting stylesheets). It is not score 2 because the actions go beyond generic (concrete tools and a verify-before-recommend step), and not score 4 because the action list is not comprehensive — the actual optimization work is omitted.

3 / 5

Completeness

The "when" is explicit and strong ("Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize CSS file size"), but the "what" is only implied — the description never states what the skill does (minify, purge, split CSS); the closest is the behavioral instruction "Verify the actual bottleneck... before recommending changes". Not score 2 because the when clause and the verify instruction together weakly imply the what; not score 4 because the what is never explicitly stated as a capability.

3 / 5

Trigger Term Quality

Good natural keyword coverage: "slow page loads", "heavy assets", "rendering delays", "DevTools", "Lighthouse", and "CSS file size" are phrases users would plausibly say when needing this skill. Not score 5 because common synonyms and variations are missing — "stylesheets", "minify CSS", "unused CSS", "render-blocking", or a ".css" extension — while the bad-overall-example failure modes are clearly avoided.

4 / 5

Distinctiveness Conflict Risk

The niche is somewhat specific — "Optimize CSS file size", "DevTools", "Lighthouse", "field data" — but the broad triggers "slow page loads" and "heavy assets" do not mention CSS, so this description would plausibly fire for sibling web-performance skills (JS bundle size, image optimization, general page-speed audits). Not score 4 because the overlap risk with closely related performance skills is more than minor.

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.

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-file-size/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.