CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

https-downgrade

Use when auditing a site's internal and external links for protocol consistency, migrating a site from HTTP to HTTPS, or reviewing hardcoded URLs in a codebase that may use `http://` instead of `https://`.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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-structured, actionable overview: concrete fix steps, a runnable grep verification, and a clean one-level pointer to references/rule.md that genuinely holds the deeper code examples and verification detail. Its main weakness is redundancy — the intro, Quick Reference, and Explain sections repeat the same mixed-content and redirect rationale — and the workflow lacks an explicit re-check loop after the batch database search-and-replace.

Suggestions

Merge the intro paragraph, Quick Reference bullets, and Explain section into one brief rationale — the mixed-content warning and redirect-cost points each appear two to three times, costing tokens without adding information.

Add an explicit feedback loop after the batch CMS search-and-replace, e.g. 'Re-run the grep audit after the replace; if HTTP links remain, fix them and re-verify before deploying.'

Replace the vague 'or use a link auditing tool' with a specific named tool or command, or point directly to the verification commands in references/rule.md.

DimensionReasoningScore

Conciseness

Mostly efficient but padded: the intro ('Linking from a secure HTTPS page to an HTTP destination creates a mixed content situation that browsers warn users about'), the Quick Reference bullets, and the Explain section ('HTTPS is a confirmed Google ranking factor... triggering browser warnings') each restate the same mixed-content and redirect-cost rationale, so it fits 'mostly efficient but could be tightened' rather than the lean anchor.

3 / 5

Actionability

Guidance is mostly executable — 'change http://yourdomain.com/path to /path (relative)', "grep -r 'href=\"http://' ./templates/", and named attributes plus JS APIs ('fetch(), axios, or router navigation calls') — with only minor gaps like the vague 'or use a link auditing tool' and no concrete CMS search-and-replace command, keeping it below the fully copy-paste-ready anchor.

4 / 5

Workflow Clarity

The Fix section is a clear 7-step audit-to-verify sequence ending with 'Verify with: grep -r ...', but the batch CMS search-and-replace (step 5) has no explicit re-check loop if verification finds remaining HTTP links, which the anchor requiring feedback loops for error recovery demands.

4 / 5

Progressive Disclosure

The ~36-line body is a well-organized overview (Quick Reference / Check / Fix / Explain / Code Review) with implementation details and code examples correctly split into the real, one-level-deep references/rule.md, clearly signaled via 'see references/rule.md' — matching the 'clear overview with well-signaled one-level-deep references' anchor; no nested references exist in the bundle.

5 / 5

Total

16

/

20

Passed

Description

87%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 explicitly covers both what the skill does and when to use it, with three concrete trigger scenarios and natural keywords like 'HTTP to HTTPS migration' and 'hardcoded URLs' that make it highly distinct from other skills. Trigger coverage is good but stops short of comprehensive, missing common synonyms such as 'mixed content' and 'SSL'.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — 'auditing a site's internal and external links for protocol consistency', 'migrating a site from HTTP to HTTPS', 'reviewing hardcoded URLs in a codebase' — but omits the resource-link/mixed-content checking (<img src>, <script src>) that the body covers, a minor coverage gap that keeps it below the 'comprehensive coverage' anchor.

4 / 5

Completeness

Both are explicitly answered with concrete trigger phrases: the what ('auditing ... links for protocol consistency', 'migrating', 'reviewing hardcoded URLs') and a maximally explicit when (three distinct 'Use when' scenarios). The anchor-4 caveat ('when' could be more explicit or specific) does not apply, so the top anchor fits best.

5 / 5

Trigger Term Quality

Good keyword coverage with natural phrases users would say — 'migrating a site from HTTP to HTTPS', 'hardcoded URLs', literal 'http://' and 'https://' — but common synonyms like 'mixed content', 'SSL', or 'insecure links' are missing, so it falls short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (HTTPS-to-HTTP link consistency) with distinctive triggers like 'protocol consistency', 'hardcoded URLs', and 'http:// instead of https://' that few other skills would match, fitting the 'clear niche with distinct triggers; minimal conflict risk' anchor rather than the minor-overlap anchor below it.

5 / 5

Total

18

/

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