How to use the Terms of Service Drafter agent skill

What the skill makes the agent do

Once the skill is installed, the agent interviews you about your product. The product can be an app, website, SaaS product, mini-program or open-source tool. The agent lists the feature modules it identifies, such as accounts, user posts, payments, subscriptions, virtual goods, third-party login, API access, community interaction or use by minors, and asks you to confirm or add to that list.

The agent then drafts the terms as a Word document. The document follows a fixed skeleton covering acceptance and updates, definitions, account registration and security, service content and changes, user conduct, intellectual property, disclaimers and limitation of liability, termination, governing law and dispute resolution, and contact. Each feature you have gets its own chapter that covers only rules for that feature. A companion privacy notice can be produced as part of the same document, or as a separate Word document if you ask for one.

• Feature chapters: for example, a user-content chapter covers content licence, moderation, removal and appeals, and a payments chapter covers price display, payment, invoicing, refunds and how to cancel auto-renewal.
• Privacy notice: maps each category of information collected to the feature that triggers its collection.
• Placeholders: entity name, address, contact details and effective date are left as placeholders, and governing law and competent court are left blank for you to fill in.

Install the skill on Claude, in your project or in the Claude apps

There are three ways to add the skill. Download the ZIP from the skill page on this site first. The skill is a folder whose main file is SKILL.md, so the ZIP needs to be unzipped to a location where the agent can find it.

For a personal setup, unzip the download into your skills folder at ~/.claude/skills/. To make the skill available only inside one project, unzip it into that project's .claude/skills/ folder. If you use the Claude apps instead, open Settings, go to Capabilities, then Skills, and upload the skill there.

• Personal install: unzip into ~/.claude/skills/
• Project install: unzip into the project's .claude/skills/ folder
• Claude apps: Settings → Capabilities → Skills, then upload

How to trigger the skill with a natural request

You do not need a special command. Describe what you want in ordinary language and mention your product's form and main features. The skill is listed under the scenarios terms of service, user agreements and platform rules, so requests on those topics are the right ones to make.

Be specific about features. The agent builds one chapter per feature, so a request that names payments, auto-renewal or user posts will produce matching rules. If you leave features out, the agent will not write rules for them, and a missed feature means a missing block of rules.

• Write terms of service for our SaaS product
• My community app has user-generated content and a paid membership, draft the user agreement
• Draft a terms of service and privacy notice for our mini-program that sells virtual goods and uses third-party login

What the agent will ask you and what the output looks like

The agent collects the essentials in one go. Expect questions about the operating entity, the user base (individuals or businesses, and whether minors are included), the pricing model and refund rules, whether users can post content, whether third-party services are integrated, and the regions where the service operates.

The Word document opens with the agreement name as the top heading. Chapters are numbered with Roman numerals and clauses are numbered as Articles. Each chapter opens with one sentence naming the feature it covers. Every rule is written as what the user may or may not do, with the consequence. User obligations and platform rights are kept in separate clauses, and the limitation-of-liability chapter marks the cap amount placeholder in bold. Directly under the title is an italic line stating that the document is a reference draft, not legal advice, and should be reviewed by a licensed lawyer before signing.

Safety notes: scripts, network and what the output is not

The skill runs no scripts and uses no network connection, according to its listing. It needs a runtime that can create Word (.docx) documents through document tools. Nothing in the skill is designed to publish the terms for you.

The output is a reference draft. The skill avoids citing statute numbers and only refers to 'under applicable law', so local legal requirements must be checked separately. It is not suitable for regulated or high-stakes businesses such as finance, healthcare or children's services, where a licensed lawyer must write or review the terms.

• Runs scripts: no
• Uses network: no
• Do not copy the output into a live product without review, since governing law, the court and cap amounts are left for you to fill in.

Tips for a better first draft

The quality of the draft depends mostly on the facts you give. Decide your refund rules, your moderation turnaround and your cancellation path before you start, because those answers become specific rules in the document. Answer the feature list carefully, adding anything the agent missed.

Treat the draft as the structure you hand to a lawyer rather than the final text. Developers can use it to show what the product needs covered, and product managers can use the feature chapters to check that each feature has matching rules.

• Confirm the refund window and the pre-charge reminder timing before generating payment clauses.
• Confirm how quickly user content is moderated, since the content chapter depends on it.
• Ask for the privacy notice as a separate document if your lawyer prefers two files.