Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing an HTTPS page for resources (scripts, images, stylesheets, iframes) that are loaded over plain HTTP.
.claude/skills/thedaviddias-mixed-content/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-12 | ✓→✗ | ▼ Worse | -14% | 0% |
| case-01 | ✓→✓ | ＝ Same ✓ | -7% | 0% |
| case-02 | ✓→✓ | ＝ Same ✓ | -11% | 0% |
| case-03 | ✓→✓ | ＝ Same ✓ | 77% | 0% |
| case-04 | ✓→✓ | ＝ Same ✓ | -1% | 0% |
Active mixed content (scripts loaded over HTTP into an HTTPS page) gives network attackers the ability to execute arbitrary JavaScript on your page — the same power as XSS, despite the page itself being served over HTTPS.
upgrade-insecure-requests CSP directive to automatically upgrade HTTP sub-resources to HTTPShttp:// URLs in HTML, CSS, and JavaScriptContent-Security-Policy: upgrade-insecure-requests directive is the most practical fix for legacy contentScan the page source and network requests for any HTTP resources loaded on an HTTPS page. Check <script src>, <img src>, <link href>, <iframe src>, and CSS url() values for http:// URLs. Also check the Content-Security-Policy header for the upgrade-insecure-requests directive.
Replace all http:// resource URLs with https:// equivalents. If the resource provider does not support HTTPS, host the resource yourself or find an alternative. Add Content-Security-Policy: upgrade-insecure-requests as a safety net for any remaining HTTP URLs.
Explain the difference between active and passive mixed content, why active mixed content is blocked by browsers, and how the upgrade-insecure-requests CSP directive works.
Review server config, headers, forms, and integration points related to Avoid mixed content on HTTPS pages. Flag exact responses, cookies, or browser behaviors that violate the rule, and verify them against the effective production-like response.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/security/mixed-content
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | pass→pass | 11,837 | 8,182 | -31% | 1 | 1 | 0% | 2,131 | 1,978 | -7% | 0 | 0 | — |
case-02 | pass→pass | 10,459 | 7,473 | -29% | 1 | 1 | 0% | 1,999 | 1,776 | -11% | 0 | 0 | — |
case-03 | pass→pass | 5,319 | 6,528 | +23% | 1 | 1 | 0% | 929 | 1,642 | +77% | 0 | 0 | — |
case-04 | pass→pass | 10,408 | 7,863 | -24% | 1 | 1 | 0% | 1,959 | 1,946 | -1% | 0 | 0 | — |
case-05 | pass→pass | 10,271 | 6,325 | -38% | 1 | 1 | 0% | 1,792 | 1,562 | -13% | 0 | 0 | — |
case-06 | pass→pass | 12,411 | 9,873 | -20% | 1 | 1 | 0% | 2,319 | 2,257 | -3% | 0 | 0 | — |
case-07 | pass→pass | 9,955 | 7,151 | -28% | 1 | 1 | 0% | 1,806 | 1,658 | -8% | 0 | 0 | — |
case-08 | fail→fail | 10,733 | 6,412 | -40% | 1 | 1 | 0% | 1,887 | 1,622 | -14% | 0 | 0 | — |
case-09 | pass→pass | 14,441 | 12,033 | -17% | 1 | 1 | 0% | 2,700 | 2,774 | +3% | 0 | 0 | — |
case-10 | pass→pass | 12,557 | 9,565 | -24% | 1 | 1 | 0% | 1,994 | 2,096 | +5% | 0 | 0 | — |
case-11 | pass→pass | 12,848 | 8,872 | -31% | 1 | 1 | 0% | 2,064 | 1,952 | -5% | 0 | 0 | — |
case-12 | pass→fail | 10,058 | 5,733 | -43% | 1 | 1 | 0% | 1,749 | 1,506 | -14% | 0 | 0 | — |
case-13 | pass→pass | 10,376 | 6,862 | -34% | 1 | 1 | 0% | 1,832 | 1,674 | -9% | 0 | 0 | — |
case-14 | pass→pass | 13,687 | 11,963 | -13% | 1 | 1 | 0% | 2,402 | 2,604 | +8% | 0 | 0 | — |
case-15 | pass→pass | 12,223 | 9,221 | -25% | 1 | 1 | 0% | 2,046 | 1,952 | -5% | 0 | 0 | — |
case-16 | pass→pass | 10,942 | 6,466 | -41% | 1 | 1 | 0% | 1,967 | 1,543 | -22% | 0 | 0 | — |
case-17 | fail→fail | 3,522 | 4,930 | +40% | 1 | 1 | 0% | 641 | 1,286 | +101% | 0 | 0 | — |
case-18 | fail→fail | 14,120 | 10,419 | -26% | 1 | 1 | 0% | 2,397 | 2,269 | -5% | 0 | 0 | — |
case-19 | fail→fail | 19,815 | 17,792 | -10% | 1 | 1 | 0% | 3,567 | 3,749 | +5% | 0 | 0 | — |
case-20 | pass→pass | 12,131 | 7,810 | -36% | 1 | 1 | 0% | 1,870 | 1,737 | -7% | 0 | 0 | — |
case-21 | pass→pass | 11,319 | 9,972 | -12% | 1 | 1 | 0% | 2,149 | 2,242 | +4% | 0 | 0 | — |
case-22 | pass→pass | 11,649 | 10,428 | -10% | 1 | 1 | 0% | 2,166 | 2,328 | +7% | 0 | 0 | — |
case-23 | pass→pass | 7,727 | 7,260 | -6% | 1 | 1 | 0% | 1,680 | 2,138 | +27% | 0 | 0 | — |
case-24 | pass→pass | 2,511 | 2,733 | +9% | 1 | 1 | 0% | 438 | 938 | +114% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 24 cases were attempted. The headline lift of -100 percentage points is the difference between those two pass rates over the 24 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Other measured skills in the registry, with their headline benchmark lift.