agentleFS
JakeLabateJakeLabate/Claude-SEO-Skills/skills/mixed-content-audit/SKILL.md

mixed-content-audit

Skill3 starsChanged 5 months agoMITView on GitHub

Audit an HTTPS website for mixed content and insecure resources. Crawls pages and inspects every subresource to find active mixed content (http scripts, stylesheets, iframes, objects browsers block on https pages), insecure form actions that submit over http, passive mixed content (http images, audio, video), legacy protocol-relative (//) resource URLs, and pages still served over http. Use when the user asks to audit, check, or fix mixed content, insecure resources, the padlock / not-secure warning, an incomplete HTTPS migration, or http resources on an https site.

  • Installs packages

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when the user asks to:

    line 14
  2. Distinctive:

    Verify an HTTPS migration is complete

    line 18
  3. Very specific:

    Write a report following references/report-template.md: summary by severity, active mixed content and insecure forms first, then passive, …

    line 64
  4. Very specific:

    If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file …

    line 83
  5. Very specific:

    If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's …

    line 93

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Mixed Content / HTTPS Audit

Audit an HTTPS site for insecure (http://) resources and produce an actionable report. Mixed content breaks pages and strips the padlock; this skill finds every instance and groups it by root cause.

When to use this skill

Use this skill when the user asks to:

  • Audit or fix mixed content / the browser "Not secure" warning
  • Find http:// scripts, styles, iframes, images, or media on https:// pages
  • Verify an HTTPS migration is complete
  • Find insecure form actions

Inputs to collect

  1. Site URL or URL list: a live https:// site root to crawl (auto-seeds from /sitemap.xml), or a text file with --url-list.
  2. Scope: pages to crawl (default 500, --max-pages).

Workflow

Step 1: Crawl and inventory subresources

Use scripts/extract_resources.py:

python3 scripts/extract_resources.py https://example.com --max-pages 500 --output resource_inventory.json
# already crawled once (e.g. in a full SEO audit)? skip the crawl and reuse the shared cache:
# python3 scripts/fetch_pages.py https://example.com --output page_cache.json
# python3 scripts/extract_resources.py --from-cache page_cache.json --output resource_inventory.json

For every page it records each subresource (scripts, stylesheets, images, iframes, media, embeds, form actions) with its tag, attribute, resolved URL, and scheme.

Step 2: Run the audit checks

python3 scripts/audit_resources.py resource_inventory.json --output audit_report.json

Step 3: Evaluate the audit checks

Evaluate each check in references/audit-checks.md. Core checks:

CheckSeverity
Active mixed content (script/style/iframe/object over http)High
Insecure form action (http)High
Passive mixed content (img/audio/video over http)Medium
Protocol-relative (//) resourceLow
Page served over httpInfo

Step 4: Produce the report

Write a report following references/report-template.md: summary by severity, active mixed content and insecure forms first, then passive, grouped by the host serving the insecure resource, and a prioritized action list.

Step 5: Recommend fixes

  • Active/passive mixed content: load the resource over https:// (most hosts already support it, just change the scheme), self-host it, or remove it.
  • Insecure form action: change the action to https://.
  • Protocol-relative URLs: make them explicit https://.
  • Insecure pages: fix the site-wide HTTPS redirect at the source (cross-check the redirect-audit skill).
  • Group fixes by host: one insecure CDN usually explains many rows.
  • Base every recommendation on the crawled inventory; never invent URLs.

Optional: export the report

As a Word document (.docx)

If the user wants the report as a .docx (for example, to share with stakeholders or attach to a ticket), save the Markdown report to a file and convert it:

python3 scripts/md_to_docx.py report.md --output report.docx

scripts/md_to_docx.py uses only the Python standard library (no pip install) and renders headings, tables, lists, links, bold/italic, and code blocks. Offer this whenever a user asks for a Word doc, a .docx, or a shareable/downloadable report.

As a CSV of findings (.csv)

If the user wants the raw findings as a spreadsheet (for filtering, sorting, or triage in Sheets or Excel), convert the audit's audit_report.json directly:

python3 scripts/findings_to_csv.py audit_report.json --output findings.csv

scripts/findings_to_csv.py is also standard-library only. It writes one row per finding, with check and severity columns prepended and list fields (e.g. the pages sharing a duplicate value) joined with ; . Unlike the .docx, which reformats the written report, the CSV is a direct dump of the structured findings: offer it whenever a user wants the data itself, a spreadsheet, or to slice findings by check or severity.

Resources

  • scripts/md_to_docx.py: convert the Markdown report into a Word (.docx) document (standard library only)
  • scripts/findings_to_csv.py: flatten the audit findings JSON into a CSV, one row per finding (standard library only)
  • references/audit-checks.md: full definitions and rationale
  • references/report-template.md: report output structure
  • scripts/extract_resources.py: crawl and inventory subresources
  • scripts/audit_resources.py: run mixed-content audit checks

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.