Agent skill · Data & Analytics

yc-saas-drafter

Drafts a customized Customer Agreement starting from the Y Combinator standard form SaaS template. Tailors the agreement through structured intake questions covering fee structure, data handling, ML rights, implementation services, and more. Applies 18 always-on defaults that transform the raw YC form into a professional starting point (renamed to "Customer Agreement", data privacy section added, warranty restructured, consolidated SLA/support exhibit, etc.). Produces a clean .docx and a lawyer-facing memo explaining every change from the YC standard. Use when user says "draft a SaaS agreement

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill yc-saas-drafter-victor-wang --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 9 KB
Bundled scripts: none
Version: 2026-05-12
Declared author: Victor Wang
Path: skills/yc-saas-drafter-victor-wang/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

## Output Requirements The final .docx must read like a lawyer drafted it. The output must contain: - **Zero** YC drafting annotations (`*[Note:...]*`, `*[OPTIONAL:...]*`) - **Zero** placeholder scaffolding (`[OPTIONAL]` markers, option guides) - **Zero** unfilled template brackets — except deliberate `[TBD — description]` markers for values the user couldn't provide, documented in the memo The agreement title is "Customer Agreement" — NOT "SaaS Services Agreement". If any annotation, note, or non-TBD bracket appears in the output, the draft is not ready. Fix it before delivering. --- ## Workflow ### Step 1: Load References Before asking any questions, read all three reference files: - `references/intake-questions.md` — 15 question groups with branching and defaults - `references/decision-matrix.md` — maps answers to YC template actions (18 always-apply defaults, 12 conditional decisions, variable substitutions, raise-with-lawyer flags) - `references/supplementary-language.md` — pre-written clause text anchored by ID (always-apply blocks and conditional blocks) The decision matrix tells you WHAT to change. The supplementary language gives you the EXACT TEXT to insert. Do not improv

What's inside
Steps it walks through
  1. Output Requirements
  2. Workflow
  3. Step 1: Load References
  4. Step 2: Run Intake
  5. Step 3: Produce the Agreement
  6. Step 4: Produce the Lawyer Memo
  7. Step 5: Deliver
  8. Decision Points Quick Reference
  9. Supplementary Language Reference
  10. What This Skill Does NOT Do
Ships with 6 files
  • LICENSE
  • README.md
  • assets/YC_Form_SaaS_Agreement.docx
  • references/decision-matrix.md
  • references/intake-questions.md
  • references/supplementary-language.md
More from awesome-legal-skills
All skills →
About this skill
What does the yc-saas-drafter skill do?

Drafts a customized Customer Agreement starting from the Y Combinator standard form SaaS template. Tailors the agreement through structured intake questions covering fee structure, data handling, ML rights, implementation services, and more. Applies 18 always-on defaults that transform the raw YC form into a professional starting point (renamed to "Customer Agreement", data privacy section added, warranty restructured, consolidated SLA/support exhibit, etc.). Produces a clean .docx and a lawyer-facing memo explaining every change from the YC standard. Use when user says "draft a SaaS agreement

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill yc-saas-drafter-victor-wang --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going