
Terms Page Generator
Generate and structure a Terms of Service page with the right sections, jurisdiction language, and AI clauses before you go live.
Overview
Terms-page-generator is an agent skill for the Ship phase that structures and drafts Terms of Service pages for solo-built products.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill terms-page-generatorWhat is this skill?
- 18-section Terms of Service framework with required Agreement, services, accounts, and liability blocks
- Initial assessment for product category, jurisdiction, AI involvement, B2B vs B2C, and indexing
- AI-specific clauses when models generate output or third-party model terms apply
- Cross-links legal-page-generator for product categories, jurisdiction framework, and indexing strategy
- Triggers on terms of service, ToS, terms and conditions, user agreement, and service agreement requests
- 18-section framework
Adoption & trust: 890 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to launch but only have a blank legal page or generic template that ignores your product category, jurisdiction, and AI features.
Who is it for?
Indie SaaS, API, marketplace, or app founders drafting ToS before first paying users or app-store submission.
Skip if: Enterprises needing counsel-reviewed bespoke agreements, or teams that only need a high-level legal overview page—use legal-page-generator instead.
When should I use this skill?
User wants to create, optimize, or structure a Terms of Service page, or mentions terms of service, ToS, terms and conditions, or user agreement.
What do I get? / Deliverables
You get a sectioned ToS draft aligned to an 18-part framework and assessment notes so you can publish and iterate with counsel.
- Structured ToS section outline
- Draft terms copy blocks
- AI and jurisdiction assessment notes
Recommended Skills
Journey fit
ToS is a launch-readiness legal artifact—you add it when preparing to ship, not while still ideating. Launch prep under Ship is where solo builders finalize user agreements alongside privacy and other legal pages.
How it compares
Structured legal-page copy skill, not a hosted policy generator or compliance SaaS.
Common Questions / FAQ
Who is terms-page-generator for?
Solo and indie builders shipping web apps, APIs, marketplaces, or mobile products who need a serious ToS outline fast.
When should I use terms-page-generator?
During Ship launch prep when you mention terms of service, ToS, terms and conditions, or user agreement—or when optimizing an existing terms page for AI or dual jurisdiction.
Is terms-page-generator safe to install?
Review the Security Audits panel on this Prism page before installing; the skill guides copy structure and does not replace licensed legal advice.
Workflow Chain
Requires first: legal page generator
SKILL.md
READMESKILL.md - Terms Page Generator
# Pages: Terms of Service Guides Terms of Service page content, structure, compliance, and AI-specific clauses. **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, e-commerce, content/media, mobile app, AI agent/MCP — see legal-page-generator §Product Categories 2. **Jurisdiction**: Governing law, dispute resolution, whether dual-jurisdiction fallback is needed — see legal-page-generator §Jurisdiction Decision Framework 3. **AI involvement**: Whether AI models generate output, and whether third-party model terms apply — see §AI Clauses 4. **User types**: B2B, B2C, or both 5. **Indexing**: Typically index (see legal-page-generator §Indexing Strategy) --- ## Required Sections (18-Section Framework) ### 1. Agreement - "By accessing or using [domain], you agree to be bound by these Terms" - "If you do not agree, please do not use the service" - Reference to other incorporated documents (Privacy Policy, AUP, Community Guidelines) ### 2. The Service - What the product does in one paragraph - **Fair-use limits**: If applicable, state daily/monthly quotas with rationale ("to keep the service fair and available for all users") - Whether the service is free or paid ### 3. Eligibility - Minimum age: 13 (US/COPPA) or 16 (EEA/GDPR) - Statement: "By using [Product], you confirm that you meet this age requirement" - Additional restrictions if applicable (e.g., not available in certain countries) ### 4. No Accounts (If Applicable) For products without user accounts: - "No account or sign-up is required" - User is solely responsible for: content submitted, output generated, compliance with these Terms each session - User bears the risk of browser/local data loss For products with accounts: - Account security: user responsible for credentials, notify of unauthorized access - Accurate information: provide truthful registration data ### 5. Acceptable Use List specific prohibited content and behaviors: **Prohibited Content**: - Illegal content under applicable law - Child sexual abuse material (CSAM) or content exploiting minors - Content that infringes intellectual property, privacy, or publicity rights - Content that promotes violence, harassment, or hate **Prohibited Behaviors**: - Scraping, crawling, or automating access beyond normal browser use - Attempting to bypass quotas, rate limits, or security measures - Reverse engineering, decompiling, or jailbreaking the service - Submitting URLs or content the user does not have the legal right to access or reproduce - Using the service for high-risk automated decisions affecting individuals **Enforcement**: Right to investigate, block IPs/sessions, and take legal action. ### 6. Your Content - User retains ownership of submitted content (URLs, prompts, uploads) - User grants a **limited, non-exclusive, request-scoped license** to process content solely to provide the service - Statement: "We do not store Your Content after the request completes" (if true) - Statement: "We do not use Your Content to train AI models" (if true — significant trust signal) - User warrants they have the right to submit the content and doing so doesn't violate third-party rights ### 7. Generated Output - **Ownership**: User owns the output and may use it for any lawful purpose, including com