CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

http-to-https

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

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/http-to-https/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

A compact, well-structured body that follows a clear check/fix/explain flow with concrete commands (curl -I, $host$request_uri) and a properly signaled one-level reference file. The only real gaps are minor over-explanation in the rationale sentences and the absence of an inline copy-paste server config, which is acceptably deferred to the reference.

DimensionReasoningScore

Conciseness

The body is lean with specific bullets (301 vs 302 caching rationale, `https://$host$request_uri`, 'never rely on client-side JavaScript'), but the one-sentence attack rationale ('exposing session cookies and form data to network attackers') and the 301-vs-302 explanation are minor over-explanation Claude could infer. This matches anchor 4's 'minor instances that could be trimmed' rather than anchor 5's every-token-earns-its-place.

4 / 5

Actionability

Concrete, executable guidance is present: 'curl -I http://example.com' for verification, 'https://$host$request_uri' for path preservation, and the 301 status code, with the Check section giving a specific test. It falls short of anchor 5 because no complete copy-paste server configuration appears inline — full configs are deferred to references/rule.md.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent sequence with an explicit verification checkpoint ('Verify the redirect with curl -I http://example.com'). It matches anchor 4's 'clear sequence with most checkpoints present' rather than anchor 5, which requires explicit validate-fix-retry feedback loops.

4 / 5

Progressive Disclosure

The ~45-line body is well-sectioned and keeps implementation detail appropriately out of line, closing with a clearly signaled one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — a file that exists in the bundle. This matches anchor 5's clear overview with well-signaled references and easy navigation.

5 / 5

Total

17

/

20

Passed

Description

65%Weight 40%Scale 1-5

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

A tight, natural trigger description with excellent distinctiveness, but it is purely a 'Use when' clause: the skill's capabilities are only implied through the trigger, and it omits common synonym terms like SSL/TLS or 'force HTTPS'. Adding a short capability statement before the trigger would lift completeness and specificity.

Suggestions

State the 'what' explicitly before the trigger, e.g. 'Checks that a web server 301-redirects all HTTP traffic to HTTPS and helps configure the redirect. Use when...'

Include common synonyms and variations users actually say — 'force HTTPS', 'SSL/TLS', 'insecure site', 'HTTP to HTTPS redirect' — to broaden trigger coverage.

Reflect the skill's full capability set (check, fix, verify with curl) in the description rather than only the checking action.

DimensionReasoningScore

Specificity

The description names the domain ("web server", "redirect all HTTP traffic to HTTPS") and one concrete action ("checking whether"), matching the anchor for 1-2 concrete actions without comprehensive coverage. It does not list several actions, so it falls below anchor 4.

3 / 5

Completeness

The 'when' is explicit ("Use when checking whether..."), but the 'what' is never stated as a capability — it only exists fused inside the trigger clause, and the skill's fix/explain functions are unmentioned. This sits between anchor 2 (only 'when' present) and anchor 4 (both present separately), because the trigger clause does embed a concrete action.

3 / 5

Trigger Term Quality

"HTTP traffic", "HTTPS", "redirect", and "web server" are natural phrases a user would say when needing this check, giving good keyword coverage. A few natural terms are missing (e.g., "SSL/TLS", "force HTTPS", "insecure"), so it stops short of anchor 5 but is above anchor 3's generic coverage.

4 / 5

Distinctiveness Conflict Risk

"Redirect all HTTP traffic to HTTPS" on a "web server" defines a clear niche with distinct, unambiguous triggers and minimal overlap with any other skill. This clearly matches the anchor-5 example of a clear niche with distinct triggers.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/http-to-https/SKILL.md

Reviewed

Table of Contents

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.