Legal Page Generator
Plan and structure Privacy, Terms, Cookie, and related legal pages with jurisdiction, product-type, and indexing guidance before you ship or list on platforms.
Overview
Legal Page Generator is an agent skill most often used in Ship (also Validate, Launch) that guides legal page structure, jurisdiction, indexing, and platform readiness for AI and SaaS products.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill legal-page-generatorWhat is this skill?
- Initial assessment for product category, page type, jurisdiction, indexing, and platform dependencies
- Product-category matrix covering freemium SaaS, API/developer, marketplace, mobile app, and AI agent/MCP offerings
- Jurisdiction decision framework and indexing (index vs noindex) strategy
- Routes specialized work to privacy-page-generator, terms-page-generator, and cookie-policy-page-generator
- Versioned skill metadata (1.2.0) with structured compliance-oriented sections
- Skill metadata version 1.2.0
Adoption & trust: 916 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship or list a product but are unsure which legal pages you need, for which countries, and whether they should be indexed or hidden.
Who is it for?
Founders structuring legal sections before launch, app-store submission, or payment-processor review across multiple product shapes.
Skip if: Replacing a licensed attorney, generating final privacy text without privacy-page-generator, or pure security penetration testing.
When should I use this skill?
User wants to create, optimize, or structure legal pages or mentions privacy policy, terms of service, legal pages, cookie policy, legal footer, compliance pages, or legal requirements.
What do I get? / Deliverables
You leave with a categorized legal-page plan, jurisdiction and indexing choices, and clear handoffs to Privacy, Terms, or Cookie specialist skills for final copy.
- Legal page inventory and structure outline
- Jurisdiction and indexing recommendations
- Pointers to specialized policy generator skills
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Legal pages are a canonical Ship concern because they gate public launch, store listings, and payment processors—even when planning starts earlier. Launch subphase covers go-live readiness: policies, footer links, and platform-mandated legal URLs.
Where it fits
Map which policies apply before you commit to freemium plus API billing in the EU and US.
Define footer legal links and noindex rules before flipping production traffic on.
Align Privacy and Terms URLs with app-store and payment-platform checklist requirements.
How it compares
Use as a compliance-oriented page planner—not a generic markdown footer snippet or a hosting-only terms template.
Common Questions / FAQ
Who is legal-page-generator for?
Indie SaaS and API builders, marketplace operators, and AI-product founders who need a systematic legal-page checklist aligned to how their product collects data and monetizes.
When should I use legal-page-generator?
In Validate when scoping compliance requirements; in Ship/Launch when preparing footer links and store submissions; and in Launch when aligning indexing and platform-mandated policy URLs.
Is legal-page-generator safe to install?
It is documentation and workflow guidance; review the Security Audits panel on this page and treat outputs as drafts to validate with counsel for your jurisdictions.
Workflow Chain
Then invoke: privacy page generator, terms page generator
SKILL.md
READMESKILL.md - Legal Page Generator
# Pages: Legal Guides legal page content, structure, compliance, and platform readiness for AI/SaaS products. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment Identify: 1. **Product category**: Free anonymous, free with account, freemium, subscription SaaS, enterprise/B2B, API/developer, marketplace/platform, e-commerce, content/media, mobile app, AI agent/MCP — see §Product Categories 2. **Page type**: Privacy Policy, Terms of Service, Cookie Policy, etc. 3. **Jurisdiction needs**: Which countries' laws apply — see §Jurisdiction Decision Framework 4. **Indexing strategy**: Index or noindex — see §Indexing Strategy 5. **Platform dependencies**: Which external platforms require these pages — see §Platform Dependencies --- ## Product Categories The legal page structure depends heavily on the product category. Identify which one applies before drafting: | Category | Key Legal Characteristics | Sections to INCLUDE | Sections to SKIP | |---|---|---|---| | **Free Anonymous** | No accounts, no payment, no persistent storage, GA4 analytics | What we DON'T collect, no-training statement, fair-use limits, free/no-SLA | Payment, account responsibilities, refund, data portability | | **Free with Account** | Login required, user data stored, may have social features | Account security, data access/portability, user responsibilities | Payment, billing, refund | | **Freemium** | Free + paid tiers, payment data, auto-renewal | Payment terms, billing, tier differences, data handling per tier | — | | **Subscription SaaS** | Recurring billing, auto-renewal, cancellation | Payment, billing cycles, auto-renewal disclosure, cancellation process | — | | **Enterprise / B2B** | DPA, SOC 2, zero-training guarantees, SCCs | DPA reference, sub-processor list, security certifications, data processing roles, custom retention | Fair-use limits (usually N/A) | | **API / Developer** | Data processor role, rate limits, API keys | Rate limits, API key security, data processor terms, uptime/SLA | End-user account sections | | **Marketplace / Platform** | Multi-party, UGC responsibility, submission licensing | Content moderation, takedown process, submitter licenses, third-party content disclaimer | — | | **E-commerce** | Physical/digital goods, refunds, shipping | Refund policy, shipping policy, consumer rights, payment security | — | | **Content / Media** | Copyright, DMCA, content licensing | DMCA contact, content ownership, republication terms | Payment (unless paid content) | | **Mobile App** | App store review, privacy nutrition labels, permissions | App store compliance notes, permission justifications, data collection summary | — | | **AI Agent / MCP** | Automated decisions, tool invocation, sub-processor chains | AI decision transparency, sub-processor chain disclosure, autonomous action limits | — | --- ## Platform Dependencies Many external platforms **require** posted Privacy Policy and/or Terms of Service before the product can be listed, advertised, or operate in compliance. These should be flagged to the user during generation. ### Submission & Directory Platforms Most AI tool directories, MCP/Skills marketplaces, and software directories require both Privacy Policy and Terms of Service to be publicly accessible bef