website-legal-pageslisted

Builds and audits the three legal pages every website needs — Privacy Policy, Terms of Service / Terms of Use, and Accessibility Statement — generated from what a site actually does (its real trackers, forms, embeds, payment and booking tools) rather than from boilerplate, using the clause structures that industry-leading companies in that vertical use. Two modes: BUILD (write the pages, drop-in HTML + Markdown, for a site you're working on) and AUDIT (scan someone else's site for missing, stale, broken, or lying legal pages and produce a client-ready gap report you can pitch from). Use this skill whenever the user mentions a privacy policy, terms of service, terms and conditions, terms of use, EULA, cookie policy, accessibility statement, ADA/WCAG compliance, GDPR, CCPA/CPRA, "legal pages", "site footer legal links", or a DMCA/refund/disclaimer page — and also when they are launching, redesigning, handing off, or auditing a website for a client or small business, even if they never say the words "privacy pol
Prxdigy-exe/website-legal-pages · ★ 0 · Web & Frontend · score 58

Install: claude install-skill Prxdigy-exe/website-legal-pages

# Website Legal Pages Three pages sit in nearly every website footer: **Privacy Policy**, **Terms of Service**, **Accessibility Statement**. On small-business sites they are usually absent, copy-pasted from an unrelated company, or actively false — a policy naming "our mobile app" for a business with no app, or an accessibility statement claiming WCAG conformance on a site that fails on the homepage. That last case matters more than an absent page. A missing policy is a gap. A policy that describes practices the business does not follow is a written admission, and an accessibility statement claiming conformance the site does not have is a documented misrepresentation that plaintiffs' firms quote back. **The goal here is accuracy, not coverage.** Every sentence you generate should be something the business could defend. ## Two modes | Mode | Trigger | Produces | |---|---|---| | **BUILD** | "write a privacy policy for…", "this site needs terms", "add legal pages", launching/handing off a site | `privacy-policy`, `terms-of-service`, `accessibility-statement` as Markdown + drop-in HTML, plus a wiring checklist | | **AUDIT** | "check if this site has…", "is this site compliant", "find businesses that need this", prospecting | A scored gap report (HTML + Markdown) with evidence, risk, and remediation | If the user gives you a URL and no clear verb, ask which mode. If they gave you their own site or codebase, assume BUILD. If they gave you someone else's site, assume AUDIT. ##