🇺🇸English

Pages: Terms of Service

Guides Terms of Service page content, structure, and compliance.

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 type : SaaS, e-commerce, content, marketplace
2. Jurisdiction : Governing law, dispute resolution
3. User types : B2B, B2C, both
4. Indexing : Typically noindex for legal pages

Best Practices

Required Sections

Content Principles

• Clear language : Plain English where possible
• Structure : Headings, table of contents
• Updates : Date; version if needed
• Legal review : Have lawyer review

Placement

• Footer : Link on every page
• Signup : Require acceptance (checkbox)
• Checkout : Link before purchase

SEO

• Noindex : Common for terms
• Canonical : If multiple versions

Output Format

• Outline (sections)
• Key points per section
• Acceptance flow (signup, checkout)
• Disclaimer : Recommend legal review

Related Skills

• legal-page-generator : Terms is a legal page type
• privacy-page-generator : Often linked together
• contact-page-generator : Contact for terms questions
• indexing : noindex for terms

Weekly Installs

229

Repository

kostja94/market…g-skills

GitHub Stars

239

First Seen

Mar 1, 2026

Security Audits

Gen Agent Trust HubPassSocketPassSnykPass

Installed on

kimi-cli211

cursor211

gemini-cli210

codex210

github-copilot210

amp210