terms-page-generator
The terms-page-generator Claude Code skill guides users through creating compliant Terms of Service pages by identifying product category, jurisdiction, and AI involvement, then structuring content across eighteen required sections including agreement terms, service description, eligibility requirements, acceptable use policies, intellectual property rights, limitation of liability, and AI-specific clauses. Use this skill when users request help drafting, optimizing, or organizing a ToS page or mention related terminology like "terms and conditions," "user agreement," or "service agreement."
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/terms-page-generator && cp -r /tmp/terms-page-generator/skills/pages/legal/terms ~/.claude/skills/terms-page-generatorSKILL.md
# 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 commercial use
- **AI caveat**: Because output is AI-generated, user is responsible for:
- Verifying accuracy, artifacts, mis-rendered text
- Ensuring output doesn't infringe third-party trademarks, copyrighted imagery, or likenesses
- Complying with terms of any website whose URL was submitted
- **Copyright note**: AI-generated content may not qualify for copyright protection in all jurisdictions
- **Image disclaimer**: AI-generated images are not photographs of real individuals; resemblance is coincidental
### 8. AI Disclaimer (Standalone Section)
- "Output is produced by probabilistic AI models"
- "May contain artifacts, inaccuracies, hallucinated text, or unexpected visual results"
- "Verify all content before publishing"
- "[Product] is a creative tool, not a source of factual representation"
- Not liable for decisions made based on AI output
### 9. Third-Party Services
- List AI model providers used (Google Gemini, OpenAI, etc.)
- **Their terms also apply**: Users' data submitted for generation is subject to those providers' terms and policies
- Link to each provider's Terms of Service and Privacy Policy
- For API/enterprise products: note sub-processor commitments and DPA availability
### 10. Free Service / No SLA (If Applicable)
For free products:
- "Provided free of charge on a best-effort basis"
- No guarantee of: uninterrupted operation, feature availability, response time, output quality
- "We may rate-limit, suspend, or discontinue features at our discretion without prior notice"
- Not liable for unavailability or discontinuation
For paid products:
- Uptime commitment (e.g., 99.9% SLA)
- Service credits for downtime
- Scheduled maintenance windows
### 11. Intellectual Property
- Operator owns: name, logo, website design, source code, UI, templates, curated content
- User-owned items explicitly excluded: user-submitted content and user-generated output
- No license to copy, modify, or redistribute operator IP without permission
### 12. Termination
- Operator may block IPs/sessions that violate §5 (Acceptable Use)
- Termination does not affect provisions that by nature survive (disclaimers, liability, indemnity, governing law)
- For account-based products: user may terminate by deleting account; operator may terminate for ToS violations
### 13. Disclaimer of Warranties
Standard US-style all-caps paragraphWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.