CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-critical

Use when reviewing stylesheets, component styles, and responsive behavior related to Inline critical CSS for faster rendering. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

74%

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

Quality

Content

72%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 lean, well-structured overview for an instruction-only review skill: it gives concrete tool names, budgets, and a clear Check-then-Fix flow, and defers all framework code to a single verified reference file at one level of depth. The main gap is workflow validation — no post-fix verification step is surfaced in the body, even though the reference file contains one.

Suggestions

Add an explicit post-fix validation step to the body, e.g. 'Verify: re-run Lighthouse and confirm no render-blocking stylesheets remain in <head> and layout is intact across breakpoints' — the reference file's Verification section already exists and just needs surfacing.

Trim the duplicated rationale: the intro sentence and the 'Explain' section both restate the render-blocking/LCP/FCP explanation Claude already knows.

Include one copy-paste-ready command in the Quick Reference (e.g. an npx critical or critters invocation) so the most common case is executable directly from the body.

DimensionReasoningScore

Conciseness

The body is efficient overall: the Quick Reference bullets are dense and specific, and Check/Fix sections are single-sentence directives. Minor over-explanation remains — the intro sentence and the 'Explain' section both restate the render-blocking/LCP/FCP rationale Claude already knows. Not 5 because that duplicated rationale could be trimmed.

4 / 5

Actionability

Concrete, specific guidance: names exact tools ('critical, critters, or Lighthouse'), a concrete budget ('~14KB of critical above-the-fold CSS in <head>'), and explicit handling for the remainder ('Load remaining CSS asynchronously after page load'). As an instruction-only skill the absence of code in the body is acceptable, and full executable examples are properly deferred to references/rule.md. Not 5 because the body itself contains no copy-paste command (e.g. an npx critical invocation).

4 / 5

Workflow Clarity

A sequence is present (Check analyzes the CSS loading strategy, Fix extracts and inlines), but validation checkpoints are missing or implicit — the body has no post-fix verification step (the reference file's Verification section is never surfaced in the body). Fits anchor 3: steps listed but sequence checkpoints absent. This is not a destructive or batch operation, so no hard cap applies, but it clearly does not meet anchor 4's 'most checkpoints present'.

3 / 5

Progressive Disclosure

Clear overview body (~33 lines) with well-organized sections, and a single well-signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — verified to exist (574 lines of framework implementations, build-tool integration, and verification guidance) with no nested references. Content is appropriately split between overview and detail, matching the anchor 5 pattern for a single-reference bundle.

5 / 5

Total

16

/

20

Passed

Description

66%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 trigger clause and reasonable keyword coverage, but the 'what' is indirect: it frames the skill around reviewing and checking rendered layout while leaving the actual critical-CSS action unstated, and its broad leading trigger clause creates overlap risk with the wider CSS review space.

Suggestions

State the core capability explicitly in third-person imperative form, e.g. 'Extracts and inlines ~14KB of critical above-the-fold CSS and defers the rest asynchronously' — this would raise specificity and completeness.

Narrow the leading trigger clause so it does not fire on generic CSS review requests, e.g. 'Use when a page has render-blocking stylesheets or when the user mentions critical CSS, render-blocking resources, or slow first paint'.

Add missing natural trigger synonyms such as 'render-blocking', 'page speed', 'LCP/FCP', and 'Core Web Vitals' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain ('stylesheets, component styles, and responsive behavior') and 1-2 concrete actions ('Check the rendered layout across breakpoints and interaction states'), but the core action around critical CSS is only topical ('related to Inline critical CSS for faster rendering') — what the skill actually does with critical CSS is never stated. Not 4 because it does not list several specific actions; not 2 because it goes beyond minimal/generic domain naming.

3 / 5

Completeness

Has an explicit 'Use when...' clause ('Use when reviewing stylesheets... related to Inline critical CSS for faster rendering') and a 'what' ('Check the rendered layout across breakpoints and interaction states before proposing a fix'). Not 5 because the 'what' is indirect — the actual fix action (inlining critical CSS) is only implied by the topic phrase rather than stated as a capability.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'rendered layout', 'Inline critical CSS'. A few natural terms users would say are missing, such as 'render-blocking', 'page speed', 'LCP', or 'Core Web Vitals'. Fits anchor 4 rather than 5 due to missing synonyms and variations.

4 / 5

Distinctiveness Conflict Risk

The leading trigger clause 'reviewing stylesheets, component styles, and responsive behavior' is broad enough to overlap with virtually any CSS or responsive-design review skill; only the trailing 'related to Inline critical CSS for faster rendering' qualifier narrows it to this niche. Fits anchor 3 (somewhat specific but could still overlap with similar skills) rather than 4, since the overlap is not limited to closely related skills.

3 / 5

Total

14

/

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-critical/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.