CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

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

The body is a clean, token-efficient overview with excellent progressive disclosure to a real, appropriately scoped reference file. Its weaknesses are in-body actionability and workflow completeness: no executable examples or commands appear in the SKILL.md itself, and the workflow lacks a post-fix validation step to confirm improvements.

Suggestions

Inline one minimal executable example in the Fix section (e.g., a `<link rel="preload" ...>` tag or the Lighthouse audit command) so the body is actionable without opening the reference.

Add a post-fix validation step such as "Re-run the Lighthouse audit or field-data check to confirm the chain depth and render timing improved".

Drop or merge the one-line concept introduction and the thin "Explain" section, which restate knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no padded passages. Minor trimmable content remains: the opening sentence "Long chains of dependent requests delay the initial rendering of the page..." explains a concept Claude already knows, and the "Explain" section ("Explain how critical request chains impact the Time to First Paint...") adds little instructional value. This places it at anchor 4 (efficient, minor over-explanation) rather than 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete elements are named — tools ("Lighthouse or WebPageTest") and techniques ("Inline critical CSS", "Use `preload` hints") — but the body contains no code, commands, or specific steps; all executable detail is deferred to references/rule.md. This matches anchor 3 (some concrete guidance but incomplete, missing key details) rather than 2, since the named tools and techniques go beyond purely high-level hints.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a present sequence, and "describe the measurement method used to confirm the issue" adds a verify-before-flagging discipline. However, there is no post-fix validation checkpoint (e.g., re-run the measurement to confirm improvement), fitting anchor 3 (sequence present, checkpoints missing) rather than 4.

3 / 5

Progressive Disclosure

The body is a clear, well-organized overview that appropriately delegates implementation detail to a single well-signaled, one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"). The referenced file exists and contains exactly the promised code examples and framework guidance, matching anchor 5.

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.

The description has a strong, explicit trigger clause and a useful measurement-first directive with named tools, making it clearly usable for routing. Its main weakness is capability coverage: it says when to use the skill and how to verify the problem, but not what the skill actually delivers for fixing critical request chains.

Suggestions

Add the skill's core fix-side capabilities to the description, e.g., "identifies dependent resource chains and recommends flattening them via inlined critical CSS and preload hints".

Include one or two common user synonyms such as "page speed" or "rendering path" to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

"Verify the actual bottleneck in DevTools, Lighthouse, or field data" is a concrete action naming specific tools, but the description stops at auditing/verifying and never states the skill's fix-side capabilities (e.g., inlining critical CSS or adding preload hints). This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions with only minor gaps.

3 / 5

Completeness

The "when" is explicit and concrete ("Use when auditing slow page loads, heavy assets, or rendering delays related to Minimize critical request chains"), and a "what" is stated ("Verify the actual bottleneck... before recommending changes"). It falls short of anchor 5 because the stated action covers only measurement discipline, not the skill's main capability of guiding the optimization itself.

4 / 5

Trigger Term Quality

Natural phrases users would say are present: "slow page loads", "heavy assets", "rendering delays", plus tool names "DevTools", "Lighthouse". A few common variations are missing ("page speed", "site performance", "LCP", "Core Web Vitals"), so it fits anchor 4 (good keyword coverage, a few natural terms missing) rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

Anchoring to the named rule "Minimize critical request chains" plus measurement-specific triggers (DevTools, Lighthouse, field data) gives it a mostly distinct niche. There is minor overlap risk with sibling performance-audit skills that would also trigger on "slow page loads" or "heavy assets", matching anchor 4 rather than 5's minimal-conflict profile.

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