Guide · Agent skill
How to use the HTTP to HTTPS Redirect Checker agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The http-to-https agent skill gives an AI agent the standard checklist for confirming that a website sends visitors from the insecure http:// address to the secure https:// address. It is useful for web developers checking HTTPS setup before launch, and for site owners or IT staff auditing whether old http links still land on insecure pages. After this guide you will know what the skill does, how to install it, how to ask for it with plain requests, and what to watch for when it runs checks.
HTTP to HTTPS Redirect Checkerthedaviddias/Front-End-Checklist · MIT Download the skill Quick start
- 1Download the ZIP. Get the http-to-https skill ZIP from this page and unzip it.
- 2Place the folder. Move it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder.
- 3Or upload it in the apps. In the Claude apps, go to Settings → Capabilities → Skills and upload the skill.
- 4Ask in plain language. Request a check of your domain's HTTP to HTTPS redirect, naming the domain.
- 5Run the curl check. Have the agent or yourself run curl -I http://yourdomain against the server and read the status and Location header.
- 6Review the result. Confirm a 301 status and that the path and query string are preserved before relying on the redirect.
What the skill makes the agent do
Agent skills are folders of instructions that an AI agent loads when a task matches their description. This one applies when you are checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
Without that redirect, people who type the domain without https:// or follow old links land on the insecure version of the site, which can expose session cookies and form data to network attackers. The skill tells the agent to test whether http://example.com redirects to https://example.com with a 301 status code, and to check that the full path and query string are preserved in the Location header.
The skill also covers suggested fixes at the server or CDN level, an explanation of the difference between 301 and 302 redirects, and how HSTS can remove the redirect for returning users once HTTPS is confirmed working. It is written as guidance and does not itself contain code that runs.
Install the skill
Download the ZIP for this skill from this page and unzip it. The folder contains SKILL.md and references/rule.md.
For a personal install, unzip it into ~/.claude/skills/. To limit it to one project, unzip it into that project's .claude/skills/ folder.
In the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Single project: .claude/skills/ inside the project
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with natural requests
You do not need a special command. Describe the task in plain language and mention HTTP, HTTPS or redirects so the agent matches the skill to your request.
Good requests name the domain and the goal, for example asking whether http://example.com redirects to https://example.com with a permanent redirect.
- Check whether http://example.com redirects to https://example.com
- Does my site send http traffic to https with a 301?
- Verify that query strings survive the HTTP to HTTPS redirect on my domain
- Review my nginx config for the HTTP to HTTPS redirect
Verify the redirect with curl
The skill's suggested verification step uses curl or a similar command-line HTTP tool. Run the check yourself or ask the agent to run it, then read the status line and the Location header in the response.
The fix instructions assume you control the web server or CDN. The skill's Fix step names curl -I as the command to verify the redirect.
curl -I http://example.comKnow what the skill needs and what it does not do
The skill requires curl or a similar command-line HTTP tool, and it uses the network when the agent runs checks. It does not run scripts on its own.
The skill gives checking steps but does not perform in-depth security scans. Results depend on the agent actually running commands and on your access to the server. If a platform you cannot configure handles the redirect, the fix instructions will not apply directly.
- Requires: curl or similar HTTP tool
- Runs scripts: no
- Uses network: yes
Tips for reliable results
Use 301 rather than 302 so browsers and search engines cache the redirect and future requests go straight to HTTPS. Configure redirects in the server or CDN, not in client-side JavaScript.
Confirm HTTPS works before you add HSTS, since HSTS is the step that removes the redirect for returning users.
- Check both the bare domain and www if you serve both
- Confirm the path and query string appear in the redirect target
- Only add HSTS after HTTPS is validated
What people use it for
- Checking a site's HTTPS setup before launch
- Auditing whether old http links still land on insecure pages
- Reviewing an nginx or Apache redirect configuration
- Learning why HTTPS redirects and HSTS matter
Frequently asked questions
How do I install the http-to-https skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings → Capabilities → Skills.
What does the http-to-https skill require?
It requires curl or a similar command-line HTTP tool, which the suggested verification step uses. It uses the network and does not run scripts.
Is the http-to-https skill free?
The skill is published under the MIT licence. This page does not list any price, so check the repository for licence terms.
Does the skill scan my site for security problems?
No. The skill gives checking steps for the HTTP to HTTPS redirect but does not perform in-depth scans. Results depend on the agent running commands like curl and on your access to the server.
Why does the skill recommend a 301 instead of a 302 redirect?
A 301 is a permanent redirect, so browsers and search engines can cache it and send future requests directly to HTTPS. The skill explains the difference between 301 and 302 redirects.
What if my hosting platform does not let me change redirects?
The fix instructions assume control of the web server or CDN. If a platform you cannot configure handles the redirect, you will need to ask that platform's support or use a setting it provides.
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 configure or audit a web server or CDN and want an agent to follow a consistent checklist for HTTP to HTTPS redirects. Pick something else if you need a deep security scan or if the redirect is controlled by a platform you cannot change.
Download the skill