http-requests

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

Quality

70%

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/http-requests/SKILL.md

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 concise, well-structured overview that uses progressive disclosure effectively by pointing to references/rule.md. Its main weakness is actionability and workflow rigor: the body gives high-level technique names with no inline executable code and only an implicit measurement checkpoint.

Suggestions

Add a small inline code snippet or one concrete DevTools/Lighthouse command in the Check or Fix section so the body is actionable without opening the reference.

Make the validation loop explicit, e.g. after applying a fix, re-count requests in DevTools/Lighthouse to confirm the reduction before reporting success.

De-duplicate the latency explanation that appears in both the opening paragraph and the first Quick Reference bullet to tighten token use.

Dimension	Reasoning	Score
Conciseness	The body is lean with one-sentence sections and a tight Quick Reference; minor redundancy between the opening latency sentence and the first Quick Reference bullet keeps it just short of fully efficient.	4 / 5
Actionability	Names concrete techniques ('combining files, using sprites, inlining critical resources, implementing HTTP/2') but the body itself contains no executable code or commands, deferring those to references/rule.md.	3 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is present and the Code Review section asks for a measurement method to confirm the issue, but there is no explicit post-fix re-measurement feedback loop and checkpoints are mostly implicit.	3 / 5
Progressive Disclosure	The body is a clear overview that defers full implementation details, code examples, and framework guidance to a single well-signaled one-level-deep reference ('see references/rule.md'), which exists in the bundle.	5 / 5
	Total	15 / 20 Passed

Description

75%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 well-constructed description with an explicit trigger clause, concrete auditing actions, and named measurement tools. It is specific and distinct, though the 'what' is folded into the 'when' and could be stated more independently.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data') with specific tools, but coverage is limited to audit + verify rather than comprehensive.	4 / 5
Completeness	Explicit 'Use when...' trigger answers 'when' clearly, and the 'what' (auditing/verifying the bottleneck) is present but embedded in the trigger clause rather than stated as a standalone capability.	4 / 5
Trigger Term Quality	Includes natural phrases users say ('slow page loads', 'heavy assets', 'rendering delays', 'DevTools', 'Lighthouse', 'field data'); a few common synonyms are missing, so it stops short of fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoped to a specific rule ('Minimize HTTP requests') with concrete triggers and tools, but adjacent frontend-performance rules (image optimization, render-blocking resources) pose minor overlap risk.	4 / 5
	Total	16 / 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/http-requests/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.