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

83%

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

Quality

Content

80%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 concise and well-structured with proper progressive disclosure into a real reference file and specific actionable directives. Its weakest point is workflow clarity, where the diagnostic workflow lacks an explicit validation/feedback checkpoint in the SKILL.md body.

Suggestions

Add an explicit validation step in the body (e.g., "After applying a change, re-run Lighthouse/DevTools and confirm FCP/render-start improves before declaring the issue fixed") to turn the audit-then-fix flow into a real feedback loop.

Include one or two short inline code snippets for the highest-value fixes (defer/async script tags, critical-CSS inline block) so the most common cases are copy-paste ready without opening rule.md.

Number the Check → Fix → Explain → Code Review steps or label the verification checkpoint so the sequence and its gate are unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized — brief framing, tight Quick Reference bullets, and short Check/Fix/Explain/Code Review sections — with every token earning its place and no padding of concepts Claude already knows.	5 / 5
Actionability	Concrete, executable directives like "Load non-critical CSS and JS asynchronously using `defer`, `async`, or media queries" and "Inline critical CSS", though no runnable code examples are kept inline (they live in rule.md), leaving minor gaps.	4 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections give a rough sequence and the description urges verifying the bottleneck first, but there is no explicit validation checkpoint or fix-retry feedback loop in the body for this audit-then-recommend process.	3 / 5
Progressive Disclosure	Clear overview with a well-signaled one-level-deep reference ("see `references/rule.md`"), confirmed to exist as a real bundle file, and content appropriately split between overview and detail.	5 / 5
	Total	17 / 20 Passed

Description

87%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 is strong: it gives concrete actions, natural trigger terms, an explicit "Use when" clause, and a distinct niche with low conflict risk. The main gap is that capability coverage is good rather than exhaustive, capping specificity at 4.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "auditing slow page loads, heavy assets, or rendering delays" and "Verify the actual bottleneck in DevTools, Lighthouse, or field data" with named tools — but coverage is not fully comprehensive enough for a 5.	4 / 5
Completeness	Explicitly answers both what (audit/verify/recommend changes to render-blocking resources) and when ("Use when auditing slow page loads...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user phrases ("slow page loads", "heavy assets", "rendering delays") plus tools ("DevTools", "Lighthouse"), giving good keyword coverage, though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — render-blocking resources tied to specific diagnostic tools — with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	18 / 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/render-blocking/SKILL.md
Commit: 30756a7

Reviewed: 15 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.