Legal document library
Start from the exact source template routed below. Preserve its clauses and customization fields until matter facts justify a change. The source is a drafting baseline, not proof of current law or approval to sign or publish.
Resolve every path relative to this SKILL.md. Load only the requested template and its companion README.md when one exists.
Template routes
| Request |
Source template |
| Advisor agreement |
assets/general-legal/templates/advisor-agreement/template.md |
| HIPAA business associate agreement / BAA |
assets/general-legal/templates/business-associate-agreement/template.md |
| Cookie notice |
assets/general-legal/templates/cookie-notice/template.md |
| Global / GDPR data processing addendum |
assets/general-legal/templates/dpa-global/template.md |
| U.S.-only data processing addendum |
assets/general-legal/templates/dpa-us/template.md |
| California exempt employee offer letter |
assets/general-legal/templates/employee-offer-letter/template.md |
| Technology master services agreement / MSA |
assets/general-legal/templates/master-services-agreement/template.md |
| Mutual NDA |
assets/general-legal/templates/mutual-nda/template.md |
| One-way NDA |
assets/general-legal/templates/one-way-nda/template.md |
| GDPR-enhanced privacy policy |
assets/general-legal/templates/privacy-policy-gdpr/template.md |
| U.S.-only privacy policy |
assets/general-legal/templates/privacy-policy-us/template.md |
| Website terms of use |
assets/general-legal/templates/terms-of-use/template.md |
Drafting flow
steps:
- id: select_source
action: Select the exact template for each requested document.
instruction: |
Set skill_dir to the directory containing this SKILL.md and slug to the routed template directory.
Keep different document types separate; a DPA is not a privacy policy, and an industry MSA is not a technology MSA.
validation: 'test -f "$skill_dir/assets/general-legal/templates/$slug/template.md"'
on_failure: "Stop and report the missing route. Do not substitute a nearby legal skill."
next: verify_provenance
- id: verify_provenance
action: Read the source manifest and selected template.
instruction: |
Read references/source.yaml, then read the selected template and its README.md when present.
Read references/errata.yaml and apply every entry matching the selected template as a listed deviation; keep the vendored source asset unchanged.
Record the repository commit and template path in the drafting ledger.
validation: 'rg -n "^ commit: [0-9a-f]{40}$" "$skill_dir/references/source.yaml" && test -f "$skill_dir/references/errata.yaml"'
on_failure: "Stop and label the source unpinned."
next: compile_matter
- id: compile_matter
action: Map matter facts to every customization field.
instruction: |
Collect parties, roles, jurisdiction, commercial terms, data flows, security facts, notice details, and execution choices required by the selected template.
Map each <mark> field to a supplied fact or an explicit [OPEN: description] item. Keep source language when no matter-specific reason supports a change.
validation: "Every source customization field maps to a supplied fact or an [OPEN] item; no fact is invented."
on_failure: "Return the unresolved-input list before producing an execution candidate."
next: verify_law
- id: verify_law
action: Separate source drafting from current-law verification.
instruction: |
For a document intended for signature or publication, verify jurisdiction-specific requirements against current primary authorities and cite them.
For an exploratory draft, mark current-law status unverified and retain the counsel-review gate.
validation: "The draft records current-law status as verified with primary citations or unverified with a visible blocker."
on_failure: "Downgrade the output to a counsel-review draft."
next: produce_draft
- id: produce_draft
action: Tailor the selected source without losing provenance.
instruction: |
Replace resolved fields, retain [OPEN] items, preserve defined-term and cross-reference consistency, and list material deviations from the source.
Apply matching errata before presenting any signature or publication candidate.
Write to disk only when the user explicitly names or authorizes a destination; otherwise return the draft in chat.
validation: "All source sections are accounted for, all deviations are listed, and no disk write occurred without destination authorization."
on_failure: "Repair omissions or return the blocker instead of claiming completion."
| Field |
Required value |
| compiled_intent |
Document type, parties, jurisdiction, and intended use |
| disk_state |
Chat-only, proposed path, or user-authorized written path |
| artifact_ref |
Output path or chat draft identifier |
| source_ref |
Repository commit and selected template path |
| route |
Selected template slug |
| blocker |
Open inputs, current-law verification, or counsel review |
| confidence |
Source fidelity and legal-currentness stated separately |
Baseline counters
| Baseline rationale |
Required correction |
| "The requested legal-document-library skill is absent; I will not invent it." |
Load this library and select the exact asset. |
| "The closest local drafting asset is GDPR-only, so I will reuse its structure." |
Route U.S. and global DPAs separately. |
| "The 20-minute shortcut is one generic U.S. core plus a California role-and-use restriction overlay." |
Start from the pinned U.S. DPA and mark unresolved states. |
"I would not treat oilfield-msa as 'close enough.'" |
Use the technology MSA asset. |
| "The DPA skill is not close enough." |
Use the GDPR privacy-policy asset for transparency notices. |
| "The compliance-summary skill can supply the disclosure checklist, but it cannot supply verified attorney-authored clauses." |
Use compliance skills for review after the source draft, not instead of it. |
If you catch yourself thinking:
- "We already spent six hours, so rerouting now wastes the work."
- "A DPA discusses privacy, so it is close enough to publish as the privacy policy."
- "Changing attorney-drafted language creates risk, so using the MSA unchanged is safest."
- "The missing fields are clerical; normal defaults cannot materially change the deal."
- "Attorney-drafted means legally current, and tonight's deadline makes another review redundant."
All five mean: stop, preserve useful prior work as input, and return to select_source, compile_matter, or verify_law before producing a signature or publication candidate.
1---2name: legal-document-library3description: Use when drafting from attorney-authored startup and technology templates for an advisor agreement, business associate agreement, cookie notice, U.S. or global data processing addendum, California offer letter, technology master services agreement, mutual or one-way NDA, U.S. or GDPR privacy policy, or terms of use.4---56# Legal document library78Start from the exact source template routed below. Preserve its clauses and customization fields until matter facts justify a change. The source is a drafting baseline, not proof of current law or approval to sign or publish.910Resolve every path relative to this `SKILL.md`. Load only the requested template and its companion `README.md` when one exists.1112## Template routes1314| Request | Source template |15|---|---|16| Advisor agreement | `assets/general-legal/templates/advisor-agreement/template.md` |17| HIPAA business associate agreement / BAA | `assets/general-legal/templates/business-associate-agreement/template.md` |18| Cookie notice | `assets/general-legal/templates/cookie-notice/template.md` |19| Global / GDPR data processing addendum | `assets/general-legal/templates/dpa-global/template.md` |20| U.S.-only data processing addendum | `assets/general-legal/templates/dpa-us/template.md` |21| California exempt employee offer letter | `assets/general-legal/templates/employee-offer-letter/template.md` |22| Technology master services agreement / MSA | `assets/general-legal/templates/master-services-agreement/template.md` |23| Mutual NDA | `assets/general-legal/templates/mutual-nda/template.md` |24| One-way NDA | `assets/general-legal/templates/one-way-nda/template.md` |25| GDPR-enhanced privacy policy | `assets/general-legal/templates/privacy-policy-gdpr/template.md` |26| U.S.-only privacy policy | `assets/general-legal/templates/privacy-policy-us/template.md` |27| Website terms of use | `assets/general-legal/templates/terms-of-use/template.md` |2829## Drafting flow3031```yaml32steps:33 - id: select_source34 action: Select the exact template for each requested document.35 instruction: |36 Set skill_dir to the directory containing this SKILL.md and slug to the routed template directory.37 Keep different document types separate; a DPA is not a privacy policy, and an industry MSA is not a technology MSA.38 validation: 'test -f "$skill_dir/assets/general-legal/templates/$slug/template.md"'39 on_failure: "Stop and report the missing route. Do not substitute a nearby legal skill."40 next: verify_provenance4142 - id: verify_provenance43 action: Read the source manifest and selected template.44 instruction: |45 Read references/source.yaml, then read the selected template and its README.md when present.46 Read references/errata.yaml and apply every entry matching the selected template as a listed deviation; keep the vendored source asset unchanged.47 Record the repository commit and template path in the drafting ledger.48 validation: 'rg -n "^ commit: [0-9a-f]{40}$" "$skill_dir/references/source.yaml" && test -f "$skill_dir/references/errata.yaml"'49 on_failure: "Stop and label the source unpinned."50 next: compile_matter5152 - id: compile_matter53 action: Map matter facts to every customization field.54 instruction: |55 Collect parties, roles, jurisdiction, commercial terms, data flows, security facts, notice details, and execution choices required by the selected template.56 Map each <mark> field to a supplied fact or an explicit [OPEN: description] item. Keep source language when no matter-specific reason supports a change.57 validation: "Every source customization field maps to a supplied fact or an [OPEN] item; no fact is invented."58 on_failure: "Return the unresolved-input list before producing an execution candidate."59 next: verify_law6061 - id: verify_law62 action: Separate source drafting from current-law verification.63 instruction: |64 For a document intended for signature or publication, verify jurisdiction-specific requirements against current primary authorities and cite them.65 For an exploratory draft, mark current-law status unverified and retain the counsel-review gate.66 validation: "The draft records current-law status as verified with primary citations or unverified with a visible blocker."67 on_failure: "Downgrade the output to a counsel-review draft."68 next: produce_draft6970 - id: produce_draft71 action: Tailor the selected source without losing provenance.72 instruction: |73 Replace resolved fields, retain [OPEN] items, preserve defined-term and cross-reference consistency, and list material deviations from the source.74 Apply matching errata before presenting any signature or publication candidate.75 Write to disk only when the user explicitly names or authorizes a destination; otherwise return the draft in chat.76 validation: "All source sections are accounted for, all deviations are listed, and no disk write occurred without destination authorization."77 on_failure: "Repair omissions or return the blocker instead of claiming completion."78```7980<drafting-ledger>8182| Field | Required value |83|---|---|84| compiled_intent | Document type, parties, jurisdiction, and intended use |85| disk_state | Chat-only, proposed path, or user-authorized written path |86| artifact_ref | Output path or chat draft identifier |87| source_ref | Repository commit and selected template path |88| route | Selected template slug |89| blocker | Open inputs, current-law verification, or counsel review |90| confidence | Source fidelity and legal-currentness stated separately |9192</drafting-ledger>9394## Baseline counters9596| Baseline rationale | Required correction |97|---|---|98| "The requested legal-document-library skill is absent; I will not invent it." | Load this library and select the exact asset. |99| "The closest local drafting asset is GDPR-only, so I will reuse its structure." | Route U.S. and global DPAs separately. |100| "The 20-minute shortcut is one generic U.S. core plus a California role-and-use restriction overlay." | Start from the pinned U.S. DPA and mark unresolved states. |101| "I would not treat `oilfield-msa` as 'close enough.'" | Use the technology MSA asset. |102| "The DPA skill is not close enough." | Use the GDPR privacy-policy asset for transparency notices. |103| "The compliance-summary skill can supply the disclosure checklist, but it cannot supply verified attorney-authored clauses." | Use compliance skills for review after the source draft, not instead of it. |104105If you catch yourself thinking:106107- "We already spent six hours, so rerouting now wastes the work."108- "A DPA discusses privacy, so it is close enough to publish as the privacy policy."109- "Changing attorney-drafted language creates risk, so using the MSA unchanged is safest."110- "The missing fields are clerical; normal defaults cannot materially change the deal."111- "Attorney-drafted means legally current, and tonight's deadline makes another review redundant."112113All five mean: stop, preserve useful prior work as input, and return to `select_source`, `compile_matter`, or `verify_law` before producing a signature or publication candidate.