CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mixed-content

Use when reviewing an HTTPS page for resources (scripts, images, stylesheets, iframes) that are loaded over plain HTTP.

Quality

79%

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/mixed-content/SKILL.md
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.

A well-structured, appropriately brief overview body with concrete audit guidance and proper progressive disclosure to an existing reference file. The main issues are duplicated Quick Reference content and the absence of any executable snippet or example header.

Suggestions

De-duplicate the Quick Reference: merge the two 'upgrade-insecure-requests' bullets into one, and remove the repetition of the active/passive distinction (it reappears in the Explain section).

Add one concrete example, such as the literal header line 'Content-Security-Policy: upgrade-insecure-requests' as an HTTP response header, or a grep command for scanning source files for http:// URLs.

In the Code Review section, state what to do when verification fails (fix and re-verify) to close the workflow feedback loop.

DimensionReasoningScore

Conciseness

The body is mostly lean, but 'upgrade-insecure-requests' appears three times (two Quick Reference bullets plus the Fix section) and the active/passive mixed-content distinction is repeated in both Quick Reference and Explain. This redundancy goes beyond the minor trimming of anchor 4.

3 / 5

Actionability

Concrete instruction-only guidance: exact attributes to inspect ('<script src>, <img src>, <link href>, <iframe src>, and CSS url() values for http:// URLs') and a specific fix directive ('Content-Security-Policy: upgrade-insecure-requests'). Minor gaps — no example CSP header line or concrete scan command — keep it below 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review section order forms a clear sequence, and the Code Review section adds a verification checkpoint ('verify them against the effective production-like response'). No explicit feedback loop for failed verification, so not 5.

4 / 5

Progressive Disclosure

The ~45-line body is a well-sectioned overview (Quick Reference, Check, Fix, Explain, Code Review) that delegates implementation details, code examples, and framework guidance to a clearly signaled one-level-deep pointer ('see references/rule.md'), which exists in the bundle.

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 concise, specific, third-person description with an explicit 'Use when...' clause and a well-scoped niche. Its main weaknesses are the missing canonical trigger term 'mixed content' and the fusion of what and when into one clause.

Suggestions

Include the term 'mixed content' in the description, since users asking for this skill will most naturally say 'fix mixed content' or 'check for mixed content'.

Separate the capability statement from the trigger, e.g. 'Detects mixed content (scripts, images, stylesheets, iframes) loaded over plain HTTP on HTTPS pages. Use when the user mentions mixed content, insecure resources, or HTTP sub-resources on an HTTPS page.'

DimensionReasoningScore

Specificity

The description specifies one concrete action ('reviewing an HTTPS page for resources') with the target resource types explicitly enumerated ('scripts, images, stylesheets, iframes that are loaded over plain HTTP'). It lists several specifics with minor gaps rather than the multiple distinct actions needed for a 5.

4 / 5

Completeness

Both what (review an HTTPS page for plain-HTTP resources) and when ('Use when reviewing an HTTPS page...') are present, but they are fused into a single clause rather than a separate explicit trigger phrase. Anchor 4 fits; the when is explicit, so not 3, but less separated than the anchor-5 pattern.

4 / 5

Trigger Term Quality

Natural keywords like 'HTTPS page', 'scripts', 'images', 'stylesheets', 'iframes', and 'plain HTTP' are covered well, but the canonical term users actually say for this problem — 'mixed content' — is absent. Good coverage with a few natural terms missing matches anchor 4.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — auditing plain-HTTP sub-resources on HTTPS pages — with distinct, unambiguous triggers (HTTPS/HTTP, specific resource types), so it is unlikely to fire for the wrong skill.

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.

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