BD 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", "YC SaaS", "startup SaaS contract", "customer agreement", "SaaS subscription agreement", or "I need a SaaS agreement starting from the YC form". Also trigger when the user is a startup founder discussing SaaS contracting, even if they don't mention YC specifically.
Drafts a customized Customer Agreement starting from the Y Combinator standard form SaaS template.
As a process D 42/100 · Unfinished process — References files that are not bundled: assets/YC_Form_SaaS_Agreement.docx
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/YC_Form_SaaS_Agreement.docx
Process rating: all ten parameters 42/100
- 0Tools and files. 1 referenced file(s) missing: assets/YC_Form_SaaS_Agreement.docx
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (yc-saas-drafter) differs from the folder (yc-saas-drafter-victor-wang)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 52 steps
- 100Execution cost. Instruction body is 2112 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 868: 120–800 characters recommended
- +4No input/output examples
- -5TODO / placeholder text left in the skill
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 10 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (3 of 3)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.