Guide · Agent skill
How to use the HTTP Request Minimization Audit agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The http-requests skill is an agent skill that teaches an AI agent to review a web page for slow loading caused by too many separate network requests, such as many CSS, JavaScript, image or icon files. It is written for front-end developers, teams preparing a performance review, and anyone who wants a checklist-style check of asset loading. After reading this guide you will know what the skill does, how to install it, how to ask for an audit, and what its limits are.
HTTP Request Minimization Auditthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Download the http-requests skill ZIP from this page.
- 2Unzip into a skills folder. Unzip so the http-requests folder sits in ~/.claude/skills/ for personal use, or in .claude/skills/ inside a project.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the ZIP.
- 4Gather measurement data. Collect a request list from browser DevTools or a Lighthouse report for the page.
- 5Ask for an audit. Describe the slow page and ask the agent to count requests and suggest reductions.
- 6Verify and apply. Confirm each finding against your measurements, then make changes and re-measure.
What is an agent skill, and what does this one make the agent do?
An agent skill is a folder containing a SKILL.md file and any supporting reference files. When it is installed, an AI agent can load its instructions when your request matches the skill's description. This skill covers one topic: minimizing HTTP requests.
Each HTTP request adds network overhead, including DNS lookup, TCP connection and TLS handshake time. The skill tells the agent to count the requests a page makes, look for files it can combine or inline, and recommend fixes such as bundling files or using SVG sprites for icons. It also tells the agent to confirm the real bottleneck with browser DevTools, Lighthouse or field data before suggesting changes.
- Counts the HTTP requests a page makes and identifies where they can be reduced
- Recommends bundling critical CSS and JavaScript, and using SVG sprites for icons
- Suggests inlining critical resources and using HTTP/2, which reduces but does not eliminate request overhead
- Flags a target of under 50 requests for initial page load
How do you install the http-requests skill?
Download the ZIP for the skill from this page. Unzip it so the http-requests folder (containing SKILL.md and references/rule.md) lands in one of these locations:
For a personal skill available across your projects, unzip into ~/.claude/skills/. For a skill limited to one project, unzip into the .claude/skills/ folder inside that project.
In the Claude apps, you can instead upload the ZIP under Settings → Capabilities → Skills.
- Personal install: ~/.claude/skills/http-requests/
- Project install: .claude/skills/http-requests/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
How do you trigger the skill with a natural request?
You do not need a special command. The skill is meant to be used when you ask about slow page loads, heavy assets or rendering delays related to too many requests. Describe the page and the symptom, and say what you want back.
Because the skill advises checking the real bottleneck first, it works best when you also mention the tools you have, such as DevTools, Lighthouse or field data.
- "My landing page feels slow on first load. Audit how many requests it makes and suggest what to combine."
- "Review our product page's CSS, JavaScript and icon files for request count problems before launch."
- "Lighthouse flags too many requests on the homepage. Check whether request count is really the bottleneck."
What do you need before you start?
The skill does not list any requirements, does not run scripts and does not use the network. It works from your page files and whatever measurement data you supply. For a useful audit, have access to the page's source files and, ideally, a request list from browser DevTools or a Lighthouse report.
- Requires: nothing listed by the skill
- Runs scripts: no
- Uses network: no
What should you check in the audit's output?
The skill asks the agent to flag exact files, requests or rendering steps that add unnecessary network, CPU or layout cost, and to describe the measurement method used to confirm the issue. Treat the output as recommendations. The skill does not measure anything itself, and it does not make changes to your code automatically.
Review each suggestion against your own measurements before acting on it.
- Check that each flagged request is real in DevTools or a Lighthouse run
- Confirm the stated measurement method matches what you actually observed
- Apply changes yourself and re-measure afterwards
Tips and limits
The skill targets request count, not payload size. If your bottleneck is already known to be large images or JavaScript execution, this skill will not address it directly. It also does not cover deep server or database performance problems.
For full implementation details and framework-specific guidance, the skill points to references/rule.md, which includes examples such as a Vite manualChunks configuration and inlining critical CSS in the head.
- Use it for asset loading problems, not server or database issues
- Pair it with a payload or image audit if size is the real problem
- Read references/rule.md for code examples before editing build config
What people use it for
- Reviewing a landing page for many separate CSS, JavaScript or icon files before launch
- Checking whether a slow homepage is really caused by request count or by something else
- Suggesting SVG sprites to replace many small icon image requests
- Preparing a checklist-style asset loading review for a team performance check
Frequently asked questions
How do I install the http-requests agent skill?
Download the ZIP from this page and unzip the http-requests folder into ~/.claude/skills/ for personal use, or into .claude/skills/ in a project. In the Claude apps, you can upload the ZIP under Settings → Capabilities → Skills.
Is the http-requests skill free to use?
The skill is published under the MIT licence, as listed on this page. Check the licence file in the source repository for the full terms.
What does the skill require to run?
The skill lists no requirements. It does not run scripts and does not use the network, so it works from the page files and any measurement data you provide.
Will the skill change my code automatically?
No. The skill describes recommendations and does not run measurements or edit your code. You apply any changes yourself.
How is this different from Lighthouse or DevTools?
Lighthouse and DevTools measure your page, while this skill guides an agent to review assets for request-count problems and recommend fixes. The skill itself tells the agent to confirm the bottleneck with those tools before suggesting changes.
Why doesn't the skill help with my slow server responses?
The checklist covers request count and asset loading only. Deep server or database performance problems are outside its scope, so you need a different audit for those.
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 are a front-end developer or a team preparing a checklist-style review of asset loading and request count. Pick something else if your bottleneck is server or database speed, large image or JavaScript payloads, or if you expect the agent to make changes to your code automatically.
Download the skill