static-site-optimizerlisted

# Static Site Optimizer ## Overview Takes a folder of plain static sites and, for each one, makes the site load **entirely from its own origin**: every stylesheet, script, font and image pulled from a CDN is downloaded into `assets/` and the reference rewritten to the local copy. On top of that it applies a fixed list of mechanical hygiene fixes, runs Lighthouse, and writes a per-site `AUDIT.md` plus an aggregated dashboard Artifact. The whole pass is driven by `scripts/optimize.js` (Node, no runtime dependencies). Only `--compress-images` and the Lighthouse step reach for external tooling via `npx`. Why this matters — GDPR exposure, one source of truth, one DNS resolution, supply-chain risk, visitors behind blockers — is set out in `reference/why-self-hosting.md`. Read it before arguing with a user who wants to keep a CDN reference, and cite it in `AUDIT.md` when a tracker or embed stays. **This skill is deliberately narrow.** Left to a generic "improve this site" instruction, a capable agent will rewrite contact forms, guess the site's real domain, edit business content, convert image formats and fix application bugs it happens to notice — all plausible, all outside what a hygiene pass should touch without a human's sign-off. This skill replaces that free-for-all with the fixed procedure and fix list below. ## When NOT to use - Sites with a build pipeline (React/Vue/bundlers) — this targets plain HTML/CSS/JS served as-is, with no build step to invert. - When the us