CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

render-blocking

Use when auditing slow page loads, heavy assets, or rendering delays related to Eliminate render-blocking resources. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

73%

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

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.

A clean, brief overview that correctly pushes code examples and framework guidance into references/rule.md with a single well-signaled pointer. The body itself is thin on executable guidance and lacks an explicit verify-after-fix checkpoint, leaving actionability and workflow clarity in the middle of the scale.

Suggestions

Include one minimal executable snippet in the Fix section (e.g., `<script defer src="...">` or the `media="print" onload="this.media='all'"` non-critical CSS pattern) so common cases are copy-paste ready without opening references/rule.md.

Make the Check section concrete: name the specific verification step (Lighthouse's "Eliminate render-blocking resources" audit or a DevTools Network waterfall) and add an explicit re-test-after-fix checkpoint so the workflow closes the loop.

Merge the redundant Fix section with the Quick Reference (it currently repeats the same defer/async/inline advice) to tighten the body.

DimensionReasoningScore

Conciseness

The body is lean (~35 lines) with a tight Quick Reference ("Load non-critical CSS and JS asynchronously using `defer`, `async`, or media queries"). Minor trimmable pieces remain: the opening line explains the well-known "white screen" concept, and the Fix section ("using `defer`, `async`, or inlining critical styles") restates the Quick Reference. That is anchor 4 (efficient, minor over-explanation), not anchor 5's every-token-earns-its-place, and well above anchor 3's noticeably unnecessary explanation.

4 / 5

Actionability

Concrete technique names appear (`defer`, `async`, media queries, inline critical CSS, avoid `@import`) but the body contains no executable code or commands — everything runnable lives in references/rule.md. The Check section ("Review the page's resources and identify any CSS or JavaScript files that are blocking") is high-level direction without specific steps, matching anchor 3 (some concrete guidance but incomplete, missing key details) rather than anchor 4's mostly-executable guidance.

3 / 5

Workflow Clarity

A rough Check → Fix → Explain → Code Review sequence exists, and the Code Review section gestures at measurement ("describe the measurement method used to confirm the issue"), but there is no explicit validation checkpoint in the body — nothing says how to confirm the fix worked (e.g., re-run Lighthouse) before finishing. Anchor 3 (sequence present but checkpoints missing or implicit) fits; anchor 4 would require most checkpoints to be explicit.

3 / 5

Progressive Disclosure

The body is a short, well-sectioned overview that delegates all implementation detail via a clearly signaled one-level-deep pointer ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), and that file exists in the bundle with no further nesting. This matches anchor 5 (clear overview, well-signaled one-level references, appropriate split).

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.

A solid description with an explicit "Use when" clause, natural trigger terms, and a distinctive verify-before-recommending stance. Its main weaknesses are a thin "what" statement that leans on the trigger clause and a few missing natural synonyms (e.g., "page speed").

DimensionReasoningScore

Specificity

The description names the domain ("Eliminate render-blocking resources") and gives 1-2 concrete actions ("auditing slow page loads", "Verify the actual bottleneck in DevTools, Lighthouse, or field data"), but coverage is not comprehensive — it never states what it actually does with findings beyond "recommending changes". This matches anchor 3 (domain plus 1-2 concrete actions) rather than anchor 4, which expects several specific listed actions.

3 / 5

Completeness

Both parts are present: an explicit "Use when auditing..." trigger clause and a "what" ("Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes"). The "what" is somewhat folded into the when-clause and could be more explicit (e.g., "Audits and fixes render-blocking CSS/JS"), matching anchor 4 rather than anchor 5's clearly separated and concretely-triggered both-parts example.

4 / 5

Trigger Term Quality

Natural phrases users would say are present ("slow page loads", "heavy assets", "rendering delays", "render-blocking resources"), plus tool names DevTools and Lighthouse. It misses common variations like "page speed", "performance audit", or "white screen", so it fits anchor 4 (good keyword coverage, a few natural terms missing) rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche (render-blocking resources audit) is well-defined with distinct triggers ("rendering delays", "heavy assets", named tools), but terms like "slow page loads" and "heavy assets" overlap with broader web-performance skills, so it is mostly distinct with minor overlap risk — anchor 4, not the minimal-conflict anchor 5.

4 / 5

Total

15

/

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