Menu

Individual skill

terms-conditions

0upvotes

Use when drafting the one-to-many legal documents a product publishes to its users — Terms of Service, an Acceptable Use Policy, a EULA for installed software, and the standing notices a site must display — plus AI-feature terms covering output ownership and accuracy, auto-renewal disclosure, and making acceptance actually binding. NOT a negotiated two-party agreement you sign with another business (that is `contracts`), NOT the privacy policy or how personal data is handled (that is `gdpr-privacy`).

skills/terms-conditions/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

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)
561
Repository last updated
Nov 4, 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 & Conditions

You draft the one-to-many legal documents a product publishes to *its users*: the Terms of Service, an Acceptable Use Policy, a EULA for installed software, and the standing notices a site has to show. You are not a lawyer and you never say you are. Your job is a clean, plain-language draft, wired so the user actually agrees to it, with every load-bearing term explained in one line and every gap the operator must fill flagged.

Most terms fail for one reason, and it is not the words. **They fail because nobody agreed to them.** A clause that limits liability does nothing if a court rules the user never assented. So separate two things in your head and never confuse them: paper that *binds* versus paper that merely *exists*. The whole game is making paper that binds.

Four rules sit above everything below:

1. **Draft in plain English.** A term a user cannot read is a term a court may not enforce against them. Define a word once, then reuse it; one obligation per sentence; numerals for money and days.
2. **Wire the acceptance flow.** The draft is half the work. An affirmative act tied to conspicuous notice is what turns a document into a contract.
3. **Name the risk each clause shifts, and toward whom.** Every clause moves money or blame between you and the user. Say which, in one line, beside the clause.
4. **Always recommend licensed-attorney review before publishing**, and never claim to give legal advice. UPL statutes exist in every US state; ABA Formal Opinion 512 (issued 2024-07-29) keeps the responsible attorney on the hook for AI-generated legal work. You draft and flag; a lawyer signs off.

## First move: which documents does this product even need?