CtrlK
BlogDocsLog inGet started
Tessl Logo

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

63

Quality

75%

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-downgrade/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%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 well-organized, actionable skill body that uses progressive disclosure effectively by offloading detail to references/rule.md. Its main gap is workflow validation: the batch CMS search-and-replace and server-redirect steps need an explicit feedback loop rather than a single one-shot grep check.

Suggestions

Add an explicit validation feedback loop around the batch CMS search-and-replace: after replacing, re-run the audit and re-fix any remaining `http://` links until the scan is clean.

Replace the vague "use a link auditing tool" with a named tool or a concrete command so step 7 is fully copy-paste ready.

Tighten the "Explain" section or fold it into "Quick Reference" to remove the small duplication with the "Check" section.

DimensionReasoningScore

Conciseness

Mostly lean across ~50 lines with each section earning its place; the "Explain" section and minor Quick Reference/Check duplication are small instances of over-explanation that could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — specific URL transformations, `grep -r 'href="http://' ./templates/`, CMS search-and-replace, server redirect — with only minor gaps like the vague "use a link auditing tool".

4 / 5

Workflow Clarity

A clear 7-step Fix sequence with a final verify step exists, but the batch/destructive CMS search-and-replace (step 5) lacks a validate-then-fix feedback loop, capping workflow clarity per the batch-operation rule.

3 / 5

Progressive Disclosure

Clean overview in the body with a well-signaled one-level-deep reference to `references/rule.md` (a real file) for full implementation details; content is appropriately split and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

78%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 strong, well-scoped description that leads with concrete "Use when..." triggers tied to a distinct HTTPS-protocol niche. Its only weakness is that the "what" is implied through the trigger clauses rather than stated as an explicit capability sentence.

Suggestions

Lead with a short explicit capability clause before the triggers, e.g. "Audits and fixes HTTP-to-HTTPS link downgrades. Use when...", so the "what" is stated independently of the "when".

Add the natural term "mixed content" to the trigger list, since users often phrase this problem that way.

DimensionReasoningScore

Specificity

Names several concrete 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" — with only minor framing gaps.

4 / 5

Completeness

The "Use when..." clause is explicit and concrete with three trigger scenarios; the "what" is communicated through those actions rather than stated as a separate capability, so it falls just short of a 5.

4 / 5

Trigger Term Quality

Good natural-term coverage ("links", "HTTP to HTTPS", "hardcoded URLs", "http://", "https://"), but misses common synonyms like "mixed content" or "SSL".

4 / 5

Distinctiveness Conflict Risk

Clear niche (HTTPS/HTTP protocol consistency) with distinct triggers and minimal overlap risk against general link-audit or SEO skills.

5 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.