Guide · Agent skill
How to use the HTTP/2 and HTTP/3 Audit agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The http2 skill is a checklist that teaches an AI agent to audit one web performance topic: whether a site loads its files over the newer HTTP/2 or HTTP/3 protocols. It is aimed at developers and site owners whose pages load slowly, and at front-end teams running a performance review before launch. After following this guide you will know what the skill does, how to install it, how to ask for it in plain language, and what to check in its output.
HTTP/2 and HTTP/3 Auditthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Get the http2 skill ZIP from the directory page.
- 2Unzip into a skills folder. Place it in ~/.claude/skills/ for all projects, or in a project's .claude/skills/ folder for one project.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill.
- 4Describe the slow page. Ask in plain words about slow loads, heavy assets, or rendering delays, mentioning HTTP/2 or HTTP/3.
- 5Check the protocol in DevTools. Open the Network tab, enable the Protocol column, and look for h2 or h3.
- 6Review recommendations. Confirm the bottleneck with DevTools, Lighthouse, or field data before changing server settings.
What is an agent skill and what does the http2 skill make the agent do?
An agent skill is a folder with a SKILL.md file that gives an AI agent specific instructions for one kind of task. When this skill is active, the agent works from a checklist about enabling HTTP/2 or HTTP/3 on a website.
The skill asks the agent to check whether the server already serves resources over HTTP/2 or HTTP/3, explain in plain terms why these protocols help compared with HTTP/1.1 (multiplexing and header compression), and suggest enabling them in a web server such as Nginx or Apache, or through a CDN or load balancer. It also tells the agent to confirm the real bottleneck first using DevTools, Lighthouse, or field data.
- Checks the protocol the server uses for resources
- Explains multiplexing and header compression in plain language
- Recommends enabling HTTP/2 or HTTP/3 in Nginx, Apache, or a CDN/load balancer
- Asks for measurement before recommending changes
How do you install the http2 skill?
Download the ZIP for the skill from the directory page. Then unzip it into one of these locations: ~/.claude/skills/ to make it available across your projects, or a project's .claude/skills/ folder to limit it to that project.
If you use the Claude apps instead, open Settings, go to Capabilities, and upload the skill under Skills.
- Personal: unzip into ~/.claude/skills/
- Project only: unzip into the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload
How do you trigger the skill with a natural request?
You do not need a special command. Describe the problem in ordinary words that match the skill's purpose: slow page loads, heavy assets, or rendering delays, and mention HTTP/2 or HTTP/3 if you suspect the protocol. The skill's description covers auditing slow page loads, heavy assets, and rendering delays related to enabling HTTP/2 or HTTP/3.
Asking for a verification step in the same request helps, because the skill is written to confirm the bottleneck before recommending changes.
- "My landing page is slow. Is HTTP/2 or HTTP/3 part of the problem?"
- "Check whether our site serves resources over HTTP/2 or HTTP/3 and tell me what to measure."
How do you verify the protocol yourself in Chrome DevTools?
The skill's reference material shows a manual check you can run alongside the agent. Open DevTools, go to the Network tab, right-click the table header and enable the Protocol column. Look for h2 (HTTP/2) or h3 (HTTP/3) on each request.
Use this to confirm what the agent reports. If your requests show HTTP/1.1, the protocol is a candidate for a server change.
- Open DevTools > Network
- Right-click the table header and check Protocol
- Look for h2 or h3 in the column
What does the server configuration look like?
The reference file gives an Nginx example. HTTP/2 requires HTTPS in almost all browsers, so an SSL certificate must be configured first. The protocol is enabled on the listen directive with the http2 parameter.
Apache and CDN or load balancer settings are named in the skill but not shown in the reviewed material, so ask the agent for the exact steps for your platform and check them against your provider's documentation.
server {
listen 443 ssl http2;
server_name example.com;
ssl_certificate /path/to/cert.pem;
ssl_certificate_key /path/to/key.pem;
# ... other configuration
}What does the skill need and what are the safety notes?
The skill lists no required tools, does not run scripts, and does not use the network. It only gives the agent guidance, so it cannot itself test or deploy changes to your server.
Treat its suggestions as recommendations. Review any configuration change before applying it to a live server, and confirm the result with the same DevTools check.
- Requires: nothing listed
- Runs scripts: no
- Uses network: no
- Recommends changes only; it does not verify or deploy them
What people use it for
- Checking whether a site's requests are served over HTTP/2 or HTTP/3 before a launch
- Explaining to a non-specialist team why multiplexing and header compression matter
- Drafting an Nginx listen directive change for review, after confirming HTTPS is set up
- Deciding whether a slow page is more likely caused by protocol setup or by other factors
Frequently asked questions
How do I install the http2 agent skill?
Download the ZIP from the directory page and unzip it into ~/.claude/skills/ for personal use, or into a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings → Capabilities → Skills instead.
What do I need to use the http2 skill?
The skill lists no requirements, runs no scripts, and uses no network access. You do need an agent that supports skills, and a site you can inspect with DevTools to confirm the results.
Is the http2 skill free?
The skill is published under the MIT licence. The source material reviewed here does not describe pricing, so check the directory page for any details.
Why does my site still show HTTP/1.1 after I ran the audit?
HTTP/2 is generally required to run over HTTPS, so check that an SSL certificate is configured. Then confirm the protocol with the DevTools Protocol column, since the server setting may not have been applied or reloaded.
Will enabling HTTP/2 or HTTP/3 fix my slow page?
Not necessarily. The skill itself says to verify the actual bottleneck in DevTools, Lighthouse, or field data first, because the cause of slowness is often elsewhere, especially if the site already serves HTTP/2 or HTTP/3 correctly.
How does the http2 skill compare with other performance skills?
This skill covers only the HTTP/2 and HTTP/3 topic. It does not give framework-specific configuration, and its detailed reference file was not reviewed for this summary, so use a broader performance skill or your platform's documentation for other areas.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you want an agent to check whether your site's protocol setup is part of a slow-loading problem, and to explain HTTP/2 and HTTP/3 in plain terms. Skip it if your site already serves HTTP/2 or HTTP/3 correctly, or if you need detailed framework-specific configuration, and always review its recommendations before changing a live server.
Download the skill