Terms page generator
Skill bg-szy/TOP-SKILLS/skills/superskills/terms-page-generator
全球最大的 Claude Code 技能聚合库 · 收录 3900+ 来自 12+ 来源的技能，提供在线搜索与趋势分析看板 / The world's largest Claude Code skill aggregation hub — 3900+ skills from 12+ sources with online search and trend dashboard
npx -y skills add bg-szy/TOP-SKILLS --skill terms-page-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 4 stars4 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
2.3 KB, 464 tokens by cl100k_base, as published. Nobody here has run it
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:
- Product type: SaaS, e-commerce, content, marketplace
- Jurisdiction: Governing law, dispute resolution
- User types: B2B, B2C, both
- 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