http2

Use when auditing slow page loads, heavy assets, or rendering delays related to Enable HTTP/2 or HTTP/3. 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

Medium

Suggest reviewing before use

Fix and improve this skill with Tessl

tessl review fix ./skills/http2/SKILL.md

Quality

Content

57%

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

A well-organized overview with excellent progressive disclosure pointing to a real reference file, but the body is held back by concept explanation Claude already knows, vague (non-executable) Fix/Check guidance, and a workflow lacking explicit validation checkpoints.

Suggestions

Replace the intro paragraph and benefit-restating Quick Reference bullets with a one-line rationale or remove them, since Claude already knows what HTTP/2 multiplexing and header compression do.

Add at least one concrete, executable snippet to the body (e.g., an Nginx `listen 443 ssl http2;` block or a curl/DevTools verification command) instead of only naming the tools, so the Fix section is actionable without opening the reference.

Turn Check -> Fix into an explicit validated workflow: verify the current protocol, apply the change, then re-verify that requests are now served over HTTP/2 or HTTP/3 before considering the issue resolved.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and well-sectioned, but the opening paragraph ('Modern HTTP protocols significantly reduce the impact of latency... much faster page loads') and parts of the Quick Reference explain HTTP/2 benefits Claude already knows, so it could be tightened.	2 / 3
Actionability	It names concrete tools (Nginx, Apache, CDN, DevTools, online checkers) but provides no executable commands or config in the body — 'Enable HTTP/2 or HTTP/3 in your web server' is direction rather than instruction, with the actual code deferred to references/rule.md.	2 / 3
Workflow Clarity	Check and Fix imply a light sequence, but there are no explicit validation checkpoints or feedback loops (e.g., re-verify protocol after enabling), matching the anchor for steps present but checkpoints missing or implicit.	2 / 3
Progressive Disclosure	The body is a clear sectioned overview that ends with a well-signaled one-level-deep reference ('see references/rule.md'), and that file exists on disk, so content is appropriately split with easy navigation.	3 / 3
	Total	9 / 12 Passed

Description

92%

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 strong description with explicit 'Use when' triggers, natural keywords, and concrete actions covering both what and when. Its only weakness is that the leading performance trigger terms are shared with many sibling performance skills, slightly raising conflict risk.

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'), matching the anchor for several specific concrete actions rather than just a domain plus a few actions.	3 / 3
Completeness	Explicitly answers both 'when' ('Use when auditing slow page loads...') and 'what' ('Verify the actual bottleneck... before recommending changes'), matching the anchor that clearly answers both with explicit triggers.	3 / 3
Trigger Term Quality	Natural user phrasings like 'slow page loads', 'heavy assets', 'rendering delays', 'DevTools', and 'Lighthouse' give good coverage of terms a user would actually say, matching the high-coverage anchor.	3 / 3
Distinctiveness Conflict Risk	The 'related to Enable HTTP/2 or HTTP/3' qualifier gives a niche, but the leading trigger terms ('slow page loads, heavy assets, rendering delays') are generic across many sibling performance skills, so it could overlap with similar skills rather than being unmistakably distinct.	2 / 3
	Total	11 / 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/http2/SKILL.md
Commit: 48405aa

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