Terms of Service Writer

What it does

Audits what the site actually does (sells products, accepts user-generated content, offers subscriptions, allows user accounts) and drafts terms sections only for features that genuinely exist, flagging sections like payment terms and liability limits where a lawyer should review before publishing.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/terms-of-service-writer/ (or ~/.claude/skills/terms-of-service-writer/ for all projects)

GitHub Copilot (VS Code)

.github/skills/terms-of-service-writer/

OpenAI Codex

.codex/skills/terms-of-service-writer/

Cursor

.cursor/skills/terms-of-service-writer/ (or ~/.cursor/skills/terms-of-service-writer/ globally)

Compatibility

Any WordPress site; works from a list of active plugins and business details the site owner provides.

The complete SKILL.md for this skill:

---
name: terms-of-service-writer
description: Use when a user needs a terms of service page drafted or updated to reflect new site features like a store, subscriptions, or user accounts.
---

# Terms of Service Writer

## When to use
The site needs a terms of service page, either from scratch or updated after adding a feature (store, subscriptions, comments, user accounts) that the current terms don't cover.

## Procedure
1. Audit active plugins and site features to determine what actually applies: ecommerce/checkout, subscriptions, user-generated content, account registration, third-party integrations.
2. Draft sections only for features that exist on the site, skip boilerplate about features (like a marketplace or app store) that aren't present.
3. For a store or subscription feature, draft payment, refund, and cancellation terms based on the actual policies the user provides, not assumed defaults.
4. For user-generated content (comments, forums, reviews), draft an acceptable use and content ownership section reflecting how the site actually moderates content.
5. Include a liability limitation and dispute resolution section at a general level, flagged explicitly as needing legal review before publishing.
6. Present the draft with a note on which sections were based on confirmed site features versus information still needed from the user.

## Guardrails
- Never present the draft as final, legally binding text, it is a starting draft that should be reviewed by a lawyer before publishing, especially the liability and payment sections.
- Do not invent policies (refund windows, cancellation terms) that weren't provided by the user, mark them clearly as placeholders needing real input instead of guessing.