critical-request-chains

Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize critical request chains. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/critical-request-chains/SKILL.md

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-organized overview that uses progressive disclosure effectively, but the body itself offers only directional guidance with no executable examples and an implicit rather than explicit validate-after-fix checkpoint.

Suggestions

Add one small executable snippet (e.g., a preload link tag or an inline critical-CSS example) to the body so core actions are actionable without opening the reference.

Make the validation feedback loop explicit in the body (e.g., after Fix: re-measure in Lighthouse/DevTools to confirm the chain depth dropped before reporting done).

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned (Quick Reference, Check, Fix, Explain, Code Review), assumes Claude's competence, and defers depth to references/rule.md rather than padding with explanations Claude already knows.	3 / 3
Actionability	Guidance is directionally concrete ('Inline critical CSS', 'Use preload hints', 'Flatten the request chain') but the body contains no executable code or commands — all code lives in the reference — so it is incomplete rather than copy-paste ready.	2 / 3
Workflow Clarity	A clear Check → Fix → Explain → Code Review sequence exists and Check names measurement tools, but there is no explicit validate-after-fix checkpoint in the body; the feedback loop is implicit and lives only in the reference's Verification section.	2 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep pointer ('see references/rule.md') to the real file that exists in the bundle, with content appropriately split and easy navigation.	3 / 3
	Total	10 / 12 Passed

Description

77%

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 well-structured description with an explicit Use-when trigger and concrete tooling, but its trigger terms are broad enough to risk overlap with sibling performance skills and miss common variations like 'Core Web Vitals' or 'page speed'.

Suggestions

Add common natural trigger terms (e.g., 'page speed', 'Core Web Vitals', 'LCP', 'load time') to broaden natural-language coverage.

Tie the trigger more tightly to the distinctive concept (critical request chains / dependent-resource depth) to reduce overlap with general performance skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes' — naming both the actions and the specific tools used.	3 / 3
Completeness	Clearly answers both what (audit/verify the bottleneck before recommending changes) and when via an explicit 'Use when auditing slow page loads, heavy assets, or rendering delays' trigger clause.	3 / 3
Trigger Term Quality	Includes natural terms a user would say ('slow page loads', 'heavy assets', 'rendering delays', 'DevTools', 'Lighthouse'), but misses common variations such as 'page speed', 'Core Web Vitals', 'LCP', or 'load time'.	2 / 3
Distinctiveness Conflict Risk	The 'Minimize critical request chains' niche is named, but the trigger terms ('slow page loads', 'heavy assets', 'rendering delays') are broad and could overlap with general web-performance skills.	2 / 3
	Total	10 / 12 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/critical-request-chains/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours 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.