https

Use when auditing whether a website or web application serves content exclusively over HTTPS with a valid certificate.

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/https/SKILL.md

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-structured, actionable, and uses progressive disclosure effectively with a real one-level reference. The only weakness is mild redundancy of the redirect guidance and a brief conceptual preamble that could be tightened.

Dimension	Reasoning	Score
Conciseness	The body is generally lean, but it restates the 301-redirect requirement across the Quick Reference, Check, and Fix sections, and opens with a 'Plain HTTP exposes every request...' preamble that explains a concept Claude already knows; matching the 'mostly efficient but could be tightened' anchor rather than the fully lean score-3 example.	2 / 3
Actionability	It gives concrete, actionable guidance — named tools ('Let's Encrypt/Certbot', 'SSL Labs (ssllabs.com/ssltest)'), a specific '301 (permanent) redirect', and concrete Check/Fix steps — which per the scoring note is not penalized for lacking code in an instruction-oriented skill; matching the actionable score-3 anchor.	3 / 3
Workflow Clarity	The Check → Fix → Explain → Code Review sequence is clearly ordered, and Code Review includes an explicit verification checkpoint ('verify them against the effective production-like response'), matching the score-3 anchor for a clear sequence with validation.	3 / 3
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep reference ('see references/rule.md'), and that referenced file actually exists in the bundle, matching the score-3 anchor.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 well-formed with an explicit 'Use when' trigger and a distinct security-audit niche, but it describes only one action and omits common trigger variations like SSL/TLS. It is solid but could be broadened to cover more natural terms and additional actions.

Suggestions

Add common trigger variations users actually say, e.g. 'SSL certificate', 'TLS', 'secure', or 'redirect HTTP to HTTPS', so the skill surfaces for those phrasings.

Broaden specificity beyond a single audit action — e.g. 'Audit HTTPS enforcement, verify the TLS certificate chain, and confirm HTTP-to-HTTPS redirects' — to list multiple concrete actions.

Dimension	Reasoning	Score
Specificity	It names the domain and a concrete action — 'auditing whether a website or web application serves content exclusively over HTTPS with a valid certificate' — but lists only a single audit action rather than multiple specific concrete actions, matching the anchor for score 2 and falling short of the score-3 multi-action example.	2 / 3
Completeness	It explicitly answers both what ('auditing whether a website or web application serves content exclusively over HTTPS with a valid certificate') and when via an explicit 'Use when...' trigger, matching the score-3 anchor; it is not capped at 2 because the 'Use when' clause is present.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('HTTPS', 'valid certificate', 'website', 'web application', 'auditing'), but misses common variations users would say such as 'SSL', 'TLS', 'secure', or 'HTTP to HTTPS', matching the 'some relevant keywords but missing common variations' anchor.	2 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (HTTPS/certificate auditing) with distinct triggers and is unlikely to fire for unrelated skills, matching the score-3 anchor.	3 / 3
	Total	10 / 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/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.