Skip to content
Back to skills

Terms Page Generator

ASecurity

When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.

  • 16 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added June 8, 2026
ai-agentsgogitsecurity

Security analysis

A100/100

Scanned June 8, 2026

npx -y skills add ThomasMoreAI/legal-skills-open --skill terms-page-generator --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Terms Page Generator?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Terms Page Generator
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-terms-page-generator/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-terms-page-generator)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: terms-page-generator
title: 'Pages: Terms of Service'
description: When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
author: kostja94
author_url: https://github.com/kostja94/marketing-skills/tree/main/skills/pages/legal/terms
license: MIT
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: contracts
language: en
---

# 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

| Section | Content |
|---------|---------|
| **Acceptance** | How agreement is formed (signup, use) |
| **Service description** | What you provide |
| **User obligations** | Acceptable use, account security |
| **Intellectual property** | Who owns what |
| **Payment** | If applicable; billing, refunds |
| **Liability** | Limitations, disclaimers |
| **Termination** | When and how accounts end |
| **Governing law** | Jurisdiction, dispute resolution |
| **Changes** | How you'll notify of updates |
| **Contact** | How to reach you about terms |

### 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…