terms-of-service
Skill0 starsChanged 43 days agoMITView on GitHub
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.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- schroneko/skillstheir own version, first seen Oct 29, 2026
- genspark-ai/genofficetheir own version, first seen Oct 25, 2026
- Maudeunfledged834/startup-founder-skillstheir own version, first seen Oct 25, 2026
- moh-obaida/ReadyVibe-Skillstheir own version, first seen Oct 8, 2026
- xcrrr/claude-skillstheir own version, first seen Mar 19, 2026
- shawnpang/startup-founder-skillstheir own version, first seen Mar 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- genspark-ai/genoffice★ 12ksame name
- shawnpang/startup-founder-skills★ 331same name
- Maudeunfledged834/startup-founder-skills★ 8same name
- xcrrr/claude-skills★ 6same name
- moh-obaida/ReadyVibe-Skills★ 2same name
- schroneko/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- employment-contractSkill
- regulatory-scanSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 34
Never merge the two; they have different audiences and different legal weight.
- Distinctive: line 99
Use "you" and "we." Never "the Party of the first part."
- Distinctive: line 109
Do NOT publish-ready-ify the draft by removing the flags.
- Distinctive: line 110
Do NOT claim "we never sell your data" or any practice the product has not verified - false privacy statements create regulatory liability …
- Distinctive: line 111
Do NOT silently pick aggressive terms (arbitration, class waivers, broad IP grabs on user content).
- Distinctive: line 112
Do NOT copy a competitor's ToS.
- Distinctive: line 113
Do NOT merge ToS and Privacy Policy into one document.
- Distinctive: line 114
Do NOT let the processor list in the privacy policy drift from the real subprocessor list.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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].
- Product name and one-sentence description of what it does.
- Who can use it: minimum age (default 13 in the US due to COPPA; 16 in parts of the EU), geographies served.
- Data collected: directly, automatically (analytics, logs), and from third parties.
- Payment model: free, subscription, usage-based; refund stance.
- Third-party processors: payments, analytics, hosting, email - the real list, by name.
- User-generated content: does the product host any, and who owns it.
- Governing-law jurisdiction (default: where the company is incorporated) and dispute preference (courts vs. arbitration - [DECISION NEEDED], never silently chosen).
Step 2: Draft the ToS against the clause checklist
Work through the checklist below in order; every SaaS ToS must cover at minimum the license grant, acceptable use, termination, liability limits, and dispute resolution. A missing clause is a gap the company discovers in its worst week.
Step 3: Draft the Privacy Policy as a separate document
Never merge the two; they have different audiences and different legal weight.
Step 4: Flag, then package
Mark every item needing counsel as [LAWYER REVIEW] and every open business choice as [DECISION NEEDED]. Deliver both documents with an effective-date placeholder and the consolidated flag list on top.
ToS clause-by-clause checklist
[ ] 1. Acceptance of terms - how assent happens (clickwrap beats browsewrap;
courts routinely refuse to enforce terms nobody clicked)
[ ] 2. Description of the service - plain English, one paragraph
[ ] 3. Eligibility - minimum age, account requirements
[ ] 4. User accounts & responsibilities - credential security, one person per seat
[ ] 5. License grant - limited, non-exclusive, non-transferable, revocable right
to use the service; company retains all IP [LOAD-BEARING]
[ ] 6. Acceptable use / prohibited conduct - abuse, scraping, resale, illegal
content, security probing [LOAD-BEARING]
[ ] 7. Subscription, billing & refunds - renewal mechanics, price-change notice,
refund stance [DECISION NEEDED: refund policy]
[ ] 8. User content & IP - user keeps ownership; company gets the license it
needs to operate (host, display, back up) and no more
[ ] 9. Termination & suspension - who can end it, for what, with what notice;
what happens to user data after (export window, deletion timeline)
[LOAD-BEARING]
[ ] 10. Disclaimers & limitation of liability - "as is" disclaimer; cap (commonly
fees paid in the prior 12 months); exclusion of consequential damages
[LOAD-BEARING] [LAWYER REVIEW: caps are unenforceable in some
jurisdictions and against some claim types]
[ ] 11. Indemnification - user indemnifies for their content/misuse
[ ] 12. Governing law & dispute resolution - jurisdiction; courts vs. binding
arbitration; class-action waiver [LOAD-BEARING] [DECISION NEEDED +
LAWYER REVIEW: arbitration and class waivers are business decisions with
enforceability limits]
[ ] 13. Changes to terms - how users are notified, and that material changes
need affirmative notice, not a silent edit
[ ] 14. Contact informationPrivacy Policy section checklist
- What data is collected, and how (directly, automatically, from third parties)
- Why - with legal basis under GDPR where it applies
- How it is used
- Who it is shared with - name the actual processors (analytics, payments, hosting)
- Cookies and tracking
- Data retention periods (real ones, not "as long as necessary" alone)
- User rights - access, deletion, portability, opt-out - and how to exercise them
- Security measures (described honestly, not aspirationally)
- International data transfers [LAWYER REVIEW if EU users]
- Children's data (COPPA if under-13 users are possible)
- Contact / DPO
- Effective date and change notification
Worked contrast: the liability clause
Bad: "In no event shall the Company, its affiliates, or licensors be liable for any indirect, incidental, special, exemplary, consequential or punitive damages howsoever arising under any theory of liability whether in contract, tort or otherwise..."
Good: "We built [FILL: Product] carefully, but we provide it 'as is.' To the extent the law allows: we are not liable for indirect damages (like lost profits or lost data), and our total liability to you is capped at what you paid us in the 12 months before the claim. [LAWYER REVIEW: cap enforceability varies by jurisdiction.] Some places don't allow these limits, so parts of this section may not apply to you."
Both attempt the same protection. Only one will a user read, and only one flags its own enforceability risk.
Plain-English rules
- Short sentences. Define a term once, then use it consistently.
- Use "you" and "we." Never "the Party of the first part."
- Headers and numbered clauses so users (and support teams) can cite sections.
- Where law requires specific language (GDPR rights, auto-renewal disclosures), keep it precise - do not oversimplify away legal meaning.
Deliverable
Produce two documents - ToS and Privacy Policy - each with numbered sections, an effective-date placeholder, and a consolidated list at the top of every [LAWYER REVIEW] and [DECISION NEEDED] item, plus a closing restatement that this is a draft requiring attorney review before publication.
Do NOT
- Do NOT publish-ready-ify the draft by removing the flags; the flags are the product's honesty layer.
- Do NOT claim "we never sell your data" or any practice the product has not verified - false privacy statements create regulatory liability that no ToS can cap.
- Do NOT silently pick aggressive terms (arbitration, class waivers, broad IP grabs on user content); mark them [DECISION NEEDED] and explain the trade-off in one sentence.
- Do NOT copy a competitor's ToS; it encodes their processors, their jurisdiction, and their risk decisions.
- Do NOT merge ToS and Privacy Policy into one document.
- Do NOT let the processor list in the privacy policy drift from the real subprocessor list.
Quality bar
The draft ships only when: all five load-bearing clauses (license grant, acceptable use, termination, liability limits, dispute resolution) are present; every checklist item is either drafted or explicitly marked out-of-scope with a reason; the flag list is consolidated on top; the processor list matches what the user actually named; and the attorney-review requirement appears at both the top and bottom of the deliverable.
Escalation
This is not legal advice, and no draft leaves without saying so. Attorney review is required before publishing in all cases, and is urgent - not optional - when any of these apply: GDPR or CCPA exposure, HIPAA or health data, payment handling beyond a standard processor, users under 13, or regulated industries. For figuring out which regulations apply in the first place, route to regulatory-scan; for employment paperwork, route to employment-contract.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

