CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

77%

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/http2/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-structured, appropriately split overview whose main weakness is that its inline guidance stays at the tool-name level: both the check and the fix defer all executable detail to references/rule.md, and the body adds a redundant concept explanation up front. The workflow is sequenced and measurement-first but stops short of an explicit post-fix verification step.

Suggestions

Inline the minimal executable check and fix — e.g., DevTools → Network → Protocol column (look for h2/h3) and the Nginx `listen 443 ssl http2;` directive — so the body is actionable without opening the reference.

Add an explicit post-fix verification step (re-run Lighthouse/PageSpeed Insights and confirm the Protocol column shows h2/h3 on affected resources) to close the validation loop.

Cut the redundant overlap between the intro paragraph and the Quick Reference bullets — both restate multiplexing/header-compression benefits Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean overall, but the intro paragraph ("Modern HTTP protocols significantly reduce the impact of latency and allow multiple resources to be downloaded simultaneously...") explains protocol concepts Claude already knows, and the Quick Reference bullets ("Enable HTTP/2 or HTTP/3 for request multiplexing", "Reduce overhead with header compression") duplicate that same content. Not 5 because of this redundant explanation; not 3 because the padding is minor and confined to the opening.

4 / 5

Actionability

"Verify that the server is serving resources over HTTP/2 or HTTP/3 using browser DevTools or online checkers" and "Enable HTTP/2 or HTTP/3 in your web server (Nginx, Apache) or via a CDN/load balancer" name specific tools but give no executable steps, commands, or config inline; the concrete detail (nginx `listen 443 ssl http2;`, DevTools Protocol column) lives only in references/rule.md. Not 4 because the body alone lacks copy-paste-ready guidance for either the check or the fix; not 2 because tools and targets are named and the reference path is explicit.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a clear sequence with a verify-first checkpoint ("Verify that the server is serving resources over HTTP/2 or HTTP/3") and the Code Review section asks to "describe the measurement method used to confirm the issue". Not 5 because there is no explicit post-fix re-validation step in the body (it only exists in the reference's Verification section); not 3 because the sequence and the pre-fix measurement checkpoint are present and unambiguous.

4 / 5

Progressive Disclosure

The ~30-line overview splits cleanly to a single well-signaled reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists, is one level deep, and holds the implementation detail (nginx config, verification tools). This matches the clear-overview anchor exactly.

5 / 5

Total

16

/

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 strong description with an explicit 'Use when' trigger clause, third-person-imperative voice, and concrete tool names for the verification workflow. Its main gap is that it only describes the diagnosis half of the skill — the enablement/fix action is never mentioned — and it lacks a few common performance synonyms.

Suggestions

State the fix capability explicitly (e.g., "Enable HTTP/2 or HTTP/3 in Nginx/Apache config or via a CDN/load balancer") so the description answers 'what' fully rather than only the verification step.

Add common trigger synonyms such as "page speed", "site performance", or "network latency" to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

"Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" plus "auditing slow page loads, heavy assets, or rendering delays" lists several concrete actions with named tools. Not 5 because the core fixing capability (enabling the protocol in server config or a CDN) is never stated; not 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

Both halves are explicit: "Use when auditing slow page loads, heavy assets, or rendering delays related to Enable HTTP/2 or HTTP/3" answers 'when' with concrete triggers, and "Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes" answers 'what'. Not 5 because the stated 'what' covers only verification — what the skill does to fix (enable HTTP/2/3 in Nginx, Apache, or a CDN) is absent; not 4→3 because both what and when are present and specific.

4 / 5

Trigger Term Quality

Natural phrases include "slow page loads", "heavy assets", "rendering delays", "DevTools", "Lighthouse", and "field data" — terms a user would plausibly say. Not 5 because common variations like "page speed", "site performance", or "network latency" are missing; not 3 because coverage is broad and user-natural rather than a couple of generic keywords.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche (HTTP/2/HTTP/3 protocol enablement) with distinct triggers ("DevTools", "Lighthouse", "HTTP/2 or HTTP/3"). Not 5 because generic performance triggers ("slow page loads", "rendering delays") are shared with sibling performance-audit skills (image optimization, lazy loading, etc.), creating minor overlap risk; not 3 because the protocol-specific scoping keeps it mostly distinct.

4 / 5

Total

16

/

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/http2/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.