http-to-https

Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is well-organized, concise, and uses progressive disclosure effectively by pointing to a single real reference file. The main gap is actionability: the body relies on the reference for the complete executable server-config examples rather than including a copy-paste-ready block inline.

Suggestions

Inline one minimal executable server-config example (e.g. a 3-line nginx 'return 301 https://$host$request_uri;' block) so the body is copy-paste ready without opening the reference.

Add a brief validation feedback loop in the Check/Fix sections (e.g. 'if the Location header drops the query string, fix the redirect target and re-run curl -I') to make error recovery explicit.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned (Quick Reference, Check, Fix, Explain, Code Review) with no padding explaining concepts Claude already knows; it defers full detail to the reference.	3 / 3
Actionability	It gives concrete specifics (301 status, 'https://$host$request_uri', 'curl -I http://example.com') but the complete executable server-config code blocks live in references/rule.md rather than inline, so the body's guidance is partially complete.	2 / 3
Workflow Clarity	The Check → Fix → Code Review sequence is clearly ordered with an explicit validation checkpoint ('Verify the redirect with curl -I') and a verification step for the redirect response.	3 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep reference to references/rule.md (a real file containing the full content), with content appropriately split and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, uses an explicit 'Use when...' trigger, and names a concrete, distinguishable action. Its only weakness is that it describes a single checking action rather than enumerating multiple capabilities, capping specificity at 2.

Suggestions

Optionally broaden specificity by listing the concrete actions the skill performs (e.g. 'check, verify, and explain HTTP-to-HTTPS redirect configuration') so the description conveys multiple capabilities rather than one.

Dimension	Reasoning	Score
Specificity	The description names a single concrete action ('checking whether a web server is configured to redirect all HTTP traffic to HTTPS'), which names the domain and an action but is not comprehensive across multiple actions.	2 / 3
Completeness	It explicitly answers both what (checking the redirect configuration) and when ('Use when checking whether a web server is configured to redirect all HTTP traffic to HTTPS') with an explicit trigger.	3 / 3
Trigger Term Quality	It uses natural terms a user would say — 'HTTP traffic', 'HTTPS', 'redirect', 'web server' — anchored by an explicit 'Use when...' trigger clause.	3 / 3
Distinctiveness Conflict Risk	The HTTP-to-HTTPS redirect check is a clear niche with distinct triggers unlikely to overlap with unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/http-to-https/SKILL.md
Commit: 48405aa

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

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.