CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

css-non-blocking

Use when reviewing stylesheets, component styles, and responsive behavior related to Load CSS without blocking render. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

79%

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-non-blocking/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.

A well-structured, token-efficient overview skill that correctly delegates implementation detail to a single real reference file. Its weaknesses are the motivational opening sentence and — more importantly — a Check/Fix workflow with no validation step to confirm the non-blocking change renders correctly.

Suggestions

Add an explicit verification step after Fix, e.g. "Verify: confirm no FOUC/unstyled flash after switching to async loading; re-check rendering at each breakpoint" — and note that references/rule.md contains a Verification section.

Delete or trim the opening FCP explanation sentence; Claude already knows why render-blocking CSS is bad.

Inline one minimal copy-paste example of the preload+onload pattern in the Quick Reference to make the body fully self-sufficient for the common case.

DimensionReasoningScore

Conciseness

The body is a lean ~30 lines with a tight Quick Reference of four one-line techniques; the only trimmable over-explanation is the opening motivation sentence ("Render-blocking CSS delays First Contentful Paint—users see a blank screen..."), a concept Claude already knows. This is a minor instance of over-explanation (anchor 4) rather than the 'some unnecessary explanation' of anchor 3.

4 / 5

Actionability

Concrete, specific guidance throughout: "<link rel=\"preload\" as=\"style\"> with onload handler", "Inline critical CSS, defer non-critical styles", "media attributes and loadCSS polyfill" — named techniques and attributes Claude can execute directly. It stops short of anchor 5 because the body contains no complete copy-paste-ready example (code examples are deferred to references/rule.md), leaving minor gaps.

4 / 5

Workflow Clarity

A rough sequence exists (Check → Fix, plus Explain and Code Review sections), but there are no validation checkpoints — nothing instructs verifying that the async-loading change doesn't introduce FOUC or unstyled content, and the reference's verification guidance is not surfaced in the body. This matches anchor 3 (sequence present, checkpoints missing/implicit); it exceeds anchor 2 because the steps are defined, and the operation is neither destructive nor batch so no hard cap applies, but anchor 4 requires most checkpoints present.

3 / 5

Progressive Disclosure

A clear overview body (~30 lines) with a single well-signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — the file exists (282 lines) and delivers exactly what is promised (code examples, framework-specific sections, verification checks), with no nested references. Content split and navigation match anchor 5.

5 / 5

Total

16

/

20

Passed

Description

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

A solid description with an explicit and specific trigger clause and a clear statement of the checking/fixing action. Its main gaps are modest action coverage and missing common trigger synonyms (notably "CSS" itself, "render-blocking", ".css").

Suggestions

Add one more concrete capability to broaden action coverage, e.g. "Analyzes stylesheet loading (preload, media-split, critical CSS inlining) and flags render-blocking <link> tags".

Include the natural trigger terms users would actually type: "CSS", ".css files", "render-blocking stylesheets", and "page load performance / First Contentful Paint".

Lead with the third-person capability statement before the "Use when" clause so the "what" is stated as a skill capability rather than only as review guidance.

DimensionReasoningScore

Specificity

Names the domain (render-blocking CSS review) and roughly two concrete actions — "Check the rendered layout across breakpoints and interaction states" and "proposing a fix" — but coverage is not comprehensive (no mention of analyzing/fixing the actual loading implementation). It does not reach anchor 4, which expects several specific listed actions, and exceeds anchor 2 because the actions are concrete rather than generic.

3 / 5

Completeness

Explicitly answers both questions: the "what" is "Check the rendered layout across breakpoints and interaction states before proposing a fix", and the "when" is the explicit "Use when reviewing stylesheets, component styles, and responsive behavior related to Load CSS without blocking render" clause with concrete trigger phrases. This matches the anchor-5 example pattern (action statement + explicit Use-when with triggers), and is not merely the weaker 'when could be more explicit' case of anchor 4.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "stylesheets", "component styles", "responsive behavior", "breakpoints", "interaction states", "rendered layout" — phrases a front-end developer would plausibly say. It falls short of anchor 5 because common variations are missing: the standalone term "CSS", ".css", "render-blocking", and "page speed/performance" never appear as triggers.

4 / 5

Distinctiveness Conflict Risk

The qualifier "related to Load CSS without blocking render" gives it a clear niche distinct from general CSS or accessibility skills, but the broad opening terms ("stylesheets", "component styles", "responsive behavior") create minor overlap risk with general stylesheet-review and responsive-design skills. Mostly distinct with minor overlap, matching anchor 4 rather than the clear-niche-minimal-conflict of anchor 5.

4 / 5

Total

16

/

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-non-blocking/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.