Terms of Service
Draft or update Terms of Service for "$ARGUMENTS". Generate a comprehensive, jurisdiction-aware ToS document tailored to the product type and user base.
Note: AI-generated legal content does not constitute legal advice. Consult a qualified attorney.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Draft) of the Legal Lifecycle workflow (legal); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or legal when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}.
Check that .singularskills/legal/<project>/00-assess.md exists. If it does not exist, stop and tell the user:
"Run an Assess skill first (e.g. /legal-risk-assessment <project>) to generate the prerequisite assessment artifact."
Process
Read inputs:
- Read
.singularskills/legal/<project>/00-assess.md for risk and jurisdiction context
- Read
references/contract-template.md for standard contract provisions
Identify product context:
- Product type (web app, mobile app, marketplace, API, SaaS platform, etc.)
- Target audience (consumers, businesses, or both)
- Primary jurisdiction and any additional jurisdictions
- Key features that require specific terms (payments, user content, subscriptions, etc.)
Draft the following sections:
- Acceptance Mechanism — how users accept the terms (clickwrap, browsewrap, sign-in wrap) with enforceability considerations
- User Eligibility — age requirements (COPPA/GDPR-K considerations), geographic restrictions, entity requirements
- Account Terms — registration requirements, account security obligations, account sharing restrictions
- User Rights and Restrictions — license grant to use the service, scope and limitations
- Prohibited Uses — specific prohibited activities (illegal use, abuse, reverse engineering, scraping, etc.)
- Intellectual Property Ownership — company IP rights, trademarks, copyright notices
- User-Generated Content — if applicable: license grant from users, content moderation rights, DMCA/takedown procedures, content responsibility
- Disclaimers of Warranties — "as is" / "as available" disclaimers, no warranty of uninterrupted service
- Limitation of Liability — liability cap, exclusion of consequential damages, jurisdictional carve-outs where required
- Indemnification — user indemnification obligations, process requirements
- Termination — termination rights (by user, by company, automatic), effect of termination, data retention post-termination
- Governing Law and Dispute Resolution — choice of law, forum selection or arbitration clause, class action waiver (where enforceable)
- Modification Procedure — how changes are communicated, notice period, deemed acceptance mechanism
Tailor to jurisdiction requirements:
- EU: consumer withdrawal rights, unfair terms directive compliance, GDPR cross-references
- California: CCPA cross-references, additional consumer protections
- Other jurisdictions identified in the assessment
Write the artifact — append to .singularskills/legal/<project>/01-draft.md under a ## Terms of Service section. Create the file with a # Draft — <project> heading if it does not exist; if a ## Terms of Service section already exists, replace only that section.
Output
The Terms of Service draft appended to .singularskills/legal/<project>/01-draft.md. Present a summary to the user highlighting:
- Product type and primary jurisdiction identified
- Key sections included and any sections omitted with rationale
- Jurisdiction-specific provisions added
- Areas flagged for attorney review
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}.
This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Draft
workflow: legal
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Terms of Service section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is legal-terms-of-service).
End your section with ### Decisions and ### Open questions (one level under your ## Terms of Service heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>
1---2name: legal-terms-of-service3description: Draft or update Terms of Service for a website, app, marketplace or API — acceptance, eligibility, accounts, prohibited uses, user content, disclaimers, liability, termination and dispute resolution. Use when the user is launching a digital product and needs the public terms users accept at sign-up.4metadata:5 source: https://skillmd.com/skills/bromso/legal-terms-of-service6 argument-hint: "[project] [--skip-checks]"7 workflow: legal8 phase: 19 artifact: 01-draft.md10---1112# Terms of Service1314Draft or update Terms of Service for "$ARGUMENTS". Generate a comprehensive, jurisdiction-aware ToS document tailored to the product type and user base.1516> **Note:** AI-generated legal content does not constitute legal advice. Consult a qualified attorney.1718**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"skipped","artifact":"01-draft.md","note":"<reason or \"none given\">"}`.1920## Prerequisites2122**Part of a workflow.** This skill is phase 1 (Draft) of the Legal Lifecycle workflow (`legal`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `legal` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2324Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"refused","artifact":"01-draft.md","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"started","artifact":"01-draft.md","note":""}`.2526Check that `.singularskills/legal/<project>/00-assess.md` exists. If it does not exist, stop and tell the user:2728> "Run an Assess skill first (e.g. `/legal-risk-assessment <project>`) to generate the prerequisite assessment artifact."2930## Process31321. **Read inputs:**33 - Read `.singularskills/legal/<project>/00-assess.md` for risk and jurisdiction context34 - Read `references/contract-template.md` for standard contract provisions35362. **Identify product context:**37 - Product type (web app, mobile app, marketplace, API, SaaS platform, etc.)38 - Target audience (consumers, businesses, or both)39 - Primary jurisdiction and any additional jurisdictions40 - Key features that require specific terms (payments, user content, subscriptions, etc.)41423. **Draft the following sections:**4344 - **Acceptance Mechanism** — how users accept the terms (clickwrap, browsewrap, sign-in wrap) with enforceability considerations45 - **User Eligibility** — age requirements (COPPA/GDPR-K considerations), geographic restrictions, entity requirements46 - **Account Terms** — registration requirements, account security obligations, account sharing restrictions47 - **User Rights and Restrictions** — license grant to use the service, scope and limitations48 - **Prohibited Uses** — specific prohibited activities (illegal use, abuse, reverse engineering, scraping, etc.)49 - **Intellectual Property Ownership** — company IP rights, trademarks, copyright notices50 - **User-Generated Content** — if applicable: license grant from users, content moderation rights, DMCA/takedown procedures, content responsibility51 - **Disclaimers of Warranties** — "as is" / "as available" disclaimers, no warranty of uninterrupted service52 - **Limitation of Liability** — liability cap, exclusion of consequential damages, jurisdictional carve-outs where required53 - **Indemnification** — user indemnification obligations, process requirements54 - **Termination** — termination rights (by user, by company, automatic), effect of termination, data retention post-termination55 - **Governing Law and Dispute Resolution** — choice of law, forum selection or arbitration clause, class action waiver (where enforceable)56 - **Modification Procedure** — how changes are communicated, notice period, deemed acceptance mechanism57584. **Tailor to jurisdiction requirements:**59 - EU: consumer withdrawal rights, unfair terms directive compliance, GDPR cross-references60 - California: CCPA cross-references, additional consumer protections61 - Other jurisdictions identified in the assessment62635. **Write the artifact** — append to `.singularskills/legal/<project>/01-draft.md` under a `## Terms of Service` section. Create the file with a `# Draft — <project>` heading if it does not exist; if a `## Terms of Service` section already exists, replace only that section.6465## Output6667The Terms of Service draft appended to `.singularskills/legal/<project>/01-draft.md`. Present a summary to the user highlighting:68- Product type and primary jurisdiction identified69- Key sections included and any sections omitted with rationale70- Jurisdiction-specific provisions added71- Areas flagged for attorney review7273**Record the run.** After you have written your section, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"legal-terms-of-service","workflow":"legal","phase":1,"project":"<project>","event":"finished","artifact":"01-draft.md","note":""}`.7475This artifact is shared by every skill of phase 1 (Draft). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (`skill` is the phase title, `started` the time of that first write; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`); if it already exists, leave the block alone except to update `finished` and to set `gate` to the worst value among the sections (`skipped` over `passed`).7677```yaml78---79skill: Draft80workflow: legal81phase: 182project: <project>83started: <ISO timestamp>84finished: <ISO timestamp>85agent: <the agent you run in, or "unknown">86gate: <passed|skipped>87---88```8990Open your `## Terms of Service` section with one italic line, `*<skill name> · <ISO timestamp> · gate: <passed|skipped>*` (your skill name is `legal-terms-of-service`).9192End your section with `### Decisions` and `### Open questions` (one level under your `## Terms of Service` heading, so the section stays one block), in this shape:9394```markdown95### Decisions96- <what was chosen> — <why> — <what was rejected>9798### Open questions99- <what the next phase or a reviewer must settle>100```