CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

https

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

Quality

78%

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/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.

The body is a well-organized, appropriately sized overview with concrete audit criteria, named tools, and a clean one-level-deep pointer to references/rule.md. It scores strongly across all dimensions, with only minor trims available (the motivational opening sentence) and an implied rather than explicit post-fix re-check step.

DimensionReasoningScore

Conciseness

The body is lean and fact-dense ('All HTTP traffic must redirect to HTTPS with a 301 (permanent) redirect', 'Verify the certificate chain with SSL Labs'), with only minor over-explanation: the opening sentence about ISPs, Wi-Fi operators, and MITM attackers reading passwords covers a concept Claude already knows. Anchor 4 fits — efficient with minor trims possible; not 5 because of that motivational opener and the somewhat redundant 'Explain' meta-section.

4 / 5

Actionability

Guidance names concrete tools and expected values: 'Let's Encrypt/Certbot', '301 status code', 'SSL Labs (ssllabs.com/ssltest) — aim for A or A+', 'cover all hostnames (including www)'. Not 5 because executable commands and server configs live in references/rule.md rather than the body; not 3 because the direction is specific and complete enough to execute rather than vague.

4 / 5

Workflow Clarity

A coherent Check → Fix → Explain → Code Review sequence with validation embedded in Check ('Verify the TLS certificate is valid, not expired, and covers all hostnames. Confirm HTTP requests redirect to HTTPS with a 301 status code') plus an SSL Labs checkpoint. Not 5 because no explicit re-verification loop after Fix (fix → re-check is implied, not stated); not 3 because validation steps are present and the sequence is well-ordered — and this non-destructive audit skill has no batch/destructive cap.

4 / 5

Progressive Disclosure

A 46-line overview split into Quick Reference and task sections, with one clearly signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — and that file exists, contains the implementation detail (Nginx/Apache/Cloudflare configs, pitfalls, verification), and points to no further local files. Matches anchor 5: clear overview, well-signaled one-level-deep references, appropriate split.

5 / 5

Total

17

/

20

Passed

Description

70%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.

The description clearly defines a niche audit skill with an explicit 'Use when' trigger and good natural keywords like 'HTTPS' and 'valid certificate'. Its weaknesses are a single-verb action statement without enumerating the concrete checks, and missing common synonyms (SSL/TLS, mixed content) that users often say.

Suggestions

Enumerate the concrete audit actions in the description — e.g., 'verify 301 redirects, check certificate validity and hostname coverage, and detect mixed content' — to raise specificity beyond the single generic verb 'auditing'.

Add natural trigger synonyms such as 'SSL/TLS certificate', 'secure connection', or 'mixed content' so users who phrase the need differently still match the skill.

State the 'what' as its own clause before the trigger (e.g., 'Audits whether a site serves all pages over HTTPS with a valid certificate. Use when auditing websites or when the user mentions HTTPS, SSL, or certificate errors.') to make both halves explicit.

DimensionReasoningScore

Specificity

'auditing whether a website or web application serves content exclusively over HTTPS with a valid certificate' names the domain and one action with two facets (HTTPS coverage, cert validity) but does not enumerate the concrete checks (301 redirects, certificate chain, mixed content). Anchor 3 fits — domain plus 1-2 concrete actions, not comprehensive; not 4 because several specific actions are not listed, and not 2 because it is more concrete than a minimal domain mention.

3 / 5

Completeness

An explicit 'Use when auditing...' trigger is present, and the 'what' (auditing HTTPS coverage plus certificate validity) is clear but folded into the same clause. Anchor 4 fits — both what and when present, with the when restating the what rather than giving distinct user-context trigger phrases; not 5 for that reason, and not 3 because both elements are explicit.

4 / 5

Trigger Term Quality

Natural terms users would say are present: 'HTTPS', 'website or web application', 'valid certificate', 'auditing'. A few common variations are missing — 'SSL', 'TLS', 'mixed content', 'secure connection' — which matches anchor 4 (good keyword coverage, a few natural terms missing); not 5 due to those missing synonyms, and not 3 because coverage goes beyond merely relevant keywords.

4 / 5

Distinctiveness Conflict Risk

A clear niche — site-wide HTTPS coverage and certificate validity auditing — distinguishable from generic web-security skills, with minor overlap risk against closely related skills (TLS configuration, security headers, HSTS). Anchor 4 fits; not 5 because of that adjacent trigger space, and not 3 because the niche is well-defined rather than merely somewhat specific.

4 / 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/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.