Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
A skill your agent uses when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
MITAuto-check passed
Install HTTP To Https
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install thedaviddias/Front-End-Checklist http-to-https --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/http-to-https .claude/skills/http-to-https && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .claude/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-httpsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install thedaviddias/Front-End-Checklist http-to-https --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/http-to-https .agents/skills/http-to-https && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .agents/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install thedaviddias/Front-End-Checklist http-to-https --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/http-to-https .cursor/skills/http-to-https && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .cursor/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/thedaviddias/Front-End-Checklist.git --path skills/http-to-https--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install thedaviddias/Front-End-Checklist http-to-https --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/http-to-https .gemini/skills/http-to-https && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .gemini/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install thedaviddias/Front-End-Checklist http-to-httpsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/http-to-https .github/skills/http-to-https && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .github/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install thedaviddias/Front-End-Checklist http-to-https --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/thedaviddias/Front-End-Checklist.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/http-to-https .opencode/skills/http-to-https && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "http-to-https" agent skill from https://github.com/thedaviddias/Front-End-Checklist/tree/main/skills/http-to-https into .opencode/skills/http-to-https/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "http-to-https", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
http-to-https- GitHub stars
- 74k
- Token cost
- ~512 tokens
- SKILL.md length
- 235 words
- Files
- 2 (incl. references)
- Skills in repo
- 390
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
- Checking whether a web server is configured to redirect all HTTP traffic to HTTPS
- SKILL.md covers Quick Reference, Check, Fix and Explain, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
HTTP To Https is an agent skill from thedaviddias/Front-End-Checklist. Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
Its SKILL.md is about 510 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/rule.md`).
The repository describes itself as: 🗂 The essential checklist for modern web development, for humans and AI agents. The licence is MIT.
When your agent uses it
- Checking whether a web server is configured to redirect all HTTP traffic to HTTPS
Example prompts
- “/http-to-https”
What it can do on your machine
Read from SKILL.md and the folder at commit e8d14d0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
frontendchecklist.io
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
HTTP To Https loads about 512 tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 26 tokens; SKILL.md has 235 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from thedaviddias/Front-End-Checklist at commit e8d14d0, republished under its MIT licence (© thedaviddias). 235 words, ~512 tokens.
Download SKILL.mdSave it as
.claude/skills/http-to-https/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- http-to-https
- description
- Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
- metadata.category
- security
- metadata.priority
- critical
- metadata.difficulty
- beginner
- metadata.estimatedTime
- 10
- metadata.source
- frontendchecklist.io
- metadata.url
- https://frontendchecklist.io/rules/security/http-to-https
Redirect HTTP to HTTPS
Without an HTTP-to-HTTPS redirect, users who type the domain without https:// or follow old links land on the insecure version of the site, exposing session cookies and form data to network attackers.
Quick Reference
- Redirect
http://example.comtohttps://example.comwith HTTP 301 (permanent redirect) - Preserve the full path and query string in the redirect:
https://$host$request_uri - Use 301 (not 302) so browsers and search engines cache the redirect and future requests go directly to HTTPS
- Configure redirects at the server/CDN level — never rely on client-side JavaScript for security redirects
- After validating HTTPS works, add HSTS to eliminate future HTTP requests entirely
Check
Test whether http://example.com redirects to https://example.com with a 301 status code. Check that the full URL path and query string are preserved in the redirect Location header.
Fix
Configure the web server to redirect all HTTP requests to HTTPS with a 301 status code, preserving the full request path. Verify the redirect with curl -I http://example.com.
Explain
Explain why redirecting HTTP to HTTPS is necessary, the difference between 301 and 302 redirects, and how HSTS can eliminate the redirect for returning users.
Code Review
Review server config, headers, forms, and integration points related to Redirect HTTP to HTTPS. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/rules/security/http-to-https
© thedaviddias, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/http-to-https of thedaviddias/Front-End-Checklist.
- SKILL.md
- references/rule.md
Open the folder on GitHubat commit e8d14d0
Compare with similar skills
HTTP To Https next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| HTTP To Https this skillthedaviddias/Front-End-Checklist | 74k | — | ~512 | Automated safety check: Pass | MIT | |
| Configure Channelopenclaw/openclaw | 392k | — | ~946 | Automated safety check: Pass | MIT | |
| Checking HTTP Security Headersjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.6k | Automated safety check: Pass | MIT | |
| Check PRpaperclipai/paperclip | 99k | — | ~3.6k | Automated safety check: Pass | MIT | |
| Configuration HTTP Integrationsgreenpau/caddy-security | 2.3k | — | ~3.2k | Automated safety check: Pass | Apache-2.0 | |
| Checkdavepoon/buildwithclaude | 3.6k | — | ~680 | Automated safety check: Pass | MIT |
Similar skills
Checking HTTP Security Headers
jeremylongshore/tons-of-skills-marketplace
Audit a target's HTTP security headers — CSP, HSTS, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, and the Cross-Origin trio (COOP, COEP, CORP).
Check PR
paperclipai/paperclip
Check a GitHub, GitLab, or Perforce PR/MR/CL for review comments, failing checks, and PR-body gaps.
Configuration HTTP Integrations
greenpau/caddy-security
Mount authenticate and authorize handlers, separate portal and protected routes, align auth URLs, and preserve trusted proxy metadata.
Check
davepoon/buildwithclaude
Run CIAgent regression checks after changing an AI agent's code, prompts, or knowledge base in a repo that has agentcispec.yaml, and interpret the results.
Configuration
BuilderIO/agent-native
Where a configuration value belongs — app config schema, agent-native.config.ts, or an environment variable — and how the layers resolve.
More from thedaviddias/Front-End-Checklist
All 390 skills in this repoContent Dates Audit
thedaviddias/Front-End-Checklist
Audits article and blog pages for visible publish dates, Article JSON-LD with datePublished and dateModified, and Open Graph time tags, then fixes what is missing.
FAQPage Schema Markup
thedaviddias/Front-End-Checklist
Adds, checks and fixes FAQPage JSON-LD on pages with visible question-and-answer sections so it matches what readers see and can qualify for rich results.
Favicon Audit and Setup
thedaviddias/Front-End-Checklist
Checks that a site's favicon is linked, reachable and large enough for Google search results, and sets up ICO, SVG and Apple touch icon files when they are missing.
Content Freshness Signals
thedaviddias/Front-End-Checklist
Audits article pages for freshness signals, covering the Last-Modified header, Article JSON-LD dateModified and a visible last-updated date, and fixes mismatches.
Geo Meta Tags Audit
thedaviddias/Front-End-Checklist
Audits and fixes geo.region, geo.placename and geo.position meta tags on regional pages, noting where they help (Bing) and where they do not (Google).
Improve a Front-End Checklist Rule
thedaviddias/Front-End-Checklist
Scores and rewrites a Front-End Checklist rule MDX file against a scored quality rubric, replacing generic stub prompts with specific, actionable ones.
Questions about HTTP To Https
What does HTTP To Https do?
A skill your agent uses when checking whether a web server is configured to redirect all HTTP traffic to HTTPS. HTTP To Https is an agent skill from thedaviddias/Front-End-Checklist. Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
When should I use HTTP To Https?
HTTP To Https fits situations like: checking whether a web server is configured to redirect all HTTP traffic to HTTPS.
How do I install HTTP To Https in Claude Code?
Run `npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a claude-code`. Or copy the skill folder (skills/http-to-https in thedaviddias/Front-End-Checklist) into .claude/skills/http-to-https in your project. Claude Code loads it when a task matches its description.
How do I install HTTP To Https in Codex?
Run `npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a codex`. Or copy the skill folder (skills/http-to-https in thedaviddias/Front-End-Checklist) into .agents/skills/http-to-https in your project. Codex loads it when a task matches its description.
Can I use HTTP To Https in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add thedaviddias/Front-End-Checklist --skill http-to-https -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/http-to-https, .gemini/skills/http-to-https, .github/skills/http-to-https and .opencode/skills/http-to-https in your project.
What does HTTP To Https need to run?
SKILL.md names no scripts, command-line tools or credentials: HTTP To Https is instructions for the agent only.
Does HTTP To Https access the network?
SKILL.md names 1 domain. As links in the text: frontendchecklist.io. This is read from the text; nothing was executed.
Is HTTP To Https safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does HTTP To Https use?
HTTP To Https is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does HTTP To Https use?
About 512 tokens (SKILL.md is roughly 2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to HTTP To Https?
Skills that share tags, products or a category with HTTP To Https: Configure Channel (openclaw/openclaw, 392k stars), Checking HTTP Security Headers (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), Check PR (paperclipai/paperclip, 99k stars) and Configuration HTTP Integrations (greenpau/caddy-security, 2.3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains HTTP To Https?
thedaviddias (a GitHub user) maintains it in thedaviddias/Front-End-Checklist, which has 74,398 GitHub stars. The repository holds 390 skills in this directory. The repository was last updated on October 6, 2026.
Source: thedaviddias/Front-End-Checklist on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.