The 3 Claude Skills That Protect Your Business Legally
Most small businesses operate with more legal exposure than they realize. Not because they're doing anything wrong — because the documents that protect them either don't exist or were copy-pasted from somewhere and never properly tailored to the situation.
The Legal pack has 4 skills. None of them replace a lawyer for complex situations. All of them handle the day-to-day legal writing that eats time and creates gaps when you skip it.
/nda-draft
NDAs are one of those things where the stakes feel low until they aren't. You share something sensitive with a contractor or a potential partner without one, and most of the time nothing happens. The one time it does, you have no recourse.
/nda-draft generates a complete NDA from a quick brief — mutual or one-way, depending on the situation. All standard clauses are included: confidentiality obligations, exclusions, term, termination, and what happens to information after the relationship ends.
--contractor adjusts the language for a freelance or contractor engagement where the relationship and risk profile are different from a business partnership. --simple strips it down to a shorter, cleaner document for situations where a 10-page agreement would feel disproportionate.
Sending an NDA before a sensitive conversation is a habit worth building. This makes it take 2 minutes instead of a reason to delay.
/contract-review
Most people sign contracts they haven't fully read. Not because they're careless — because contracts are dense, the language is unfamiliar, and it feels easier to trust that the other party is acting in good faith. Sometimes that's fine. Sometimes you sign something that limits your rights in ways you don't notice until they matter.
/contract-review reads any pasted contract and flags red flags (clauses that actively disadvantage you), yellow flags (clauses worth negotiating), and missing clauses (protections that should be there but aren't). It tells you what each flag means in plain English and what you should push back on.
You still make the final call. But you're making it with a clear picture of what you're agreeing to, not a blind signature.
/privacy-policy
If you have a web app or SaaS product that collects any user data, you need a privacy policy. Not a boilerplate one copied from another company's site — one that accurately describes what you collect, how you use it, and what rights your users have. GDPR and CCPA both have teeth, and a policy that doesn't match your actual practices is worse than a vague one.
/privacy-policy drafts a GDPR and CCPA-aware privacy policy for any web app or SaaS. It's built around what you actually do, not generic template language that describes a company nothing like yours.
--no-cookies removes cookie and tracking language for products that don't use them. --b2b adjusts the framing for B2B products where the data relationship is between businesses rather than individuals.
Your privacy policy is a legal document and a trust signal. It should say something accurate.
All four skills in the Legal pack — including /terms-explainer for understanding any clause in plain English — are available to Skills Pack members. They ship as SKILL.md files — drop them into ~/.claude/skills/ and invoke with the slash command in Claude Code, Cursor, or Codex.
Next up: the Fundraising pack — pitch narrative, data room checklist, investor outreach, and term sheet explainer.