Menu

Individual skill

terms-of-service

0upvotes

Drafts plain-English Terms of Service and Privacy Policies for SaaS products using a clause-by-clause checklist, flagging every business decision and lawyer-review item explicitly. Use when someone asks "write terms of service for my app", "I need a privacy policy", "draft my ToS", "what sections does a SaaS ToS need", or is preparing legal pages before launch. Do NOT use for employee offer letters, NDAs, or employment agreements - use employment-contract instead. Do NOT use for assessing which regulations apply to a product or market - use regulatory-scan instead.

skills/terms-of-service/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Terms of Service

Draft Terms of Service and Privacy Policies for SaaS products in plain English. Readable beats clever: users and regulators both reward clarity, and courts have voided clauses buried in impenetrable prose. The two costly failures this skill prevents are shipping a ToS with a missing load-bearing section (no liability cap, no termination clause) and publishing a privacy policy that describes practices the product does not actually have - the second is worse, because a false privacy promise is an FTC deception claim waiting to happen.

The output is a strong first draft, not legal advice. Every draft must state, prominently, that a qualified attorney must review before publishing - this is a hard rule, not a courtesy line.

## Operating procedure

### Step 1: Gather inputs

Collect before drafting. Where the user does not know, propose a default and label it [DECISION NEEDED].

1. Product name and one-sentence description of what it does.
2. Who can use it: minimum age (default 13 in the US due to COPPA; 16 in parts of the EU), geographies served.
Back to top