Clause Library
Build or extend a library of approved contract clauses for "$ARGUMENTS". Provide multiple versions of each clause type with jurisdiction considerations and usage guidance.
Note: AI-generated legal content does not constitute legal advice. All clauses should be reviewed by a qualified attorney before use in binding agreements.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"legal-clause-library","workflow":"legal","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}.
Prerequisites
None — this is a utility skill.
Process
Determine scope:
- Parse "" to identify which clause types or contract context to focus on
- If a clause library already exists at
.singularskills/legal/<project>/clause-library.md, read it and extend rather than replace
Organize clauses by type:
- Indemnification — allocation of liability for third-party claims
- Limitation of Liability — caps on damages and liability exposure
- Confidentiality — scope, duration, and exceptions for confidential information
- Termination — rights, notice periods, cure periods, and post-termination obligations
- IP Assignment — ownership and assignment of intellectual property created under the agreement
- Data Protection — data processing obligations, security requirements, and breach notification
- Force Majeure — excused performance due to extraordinary events beyond control
- Governing Law — choice of law and venue selection
- Dispute Resolution — arbitration, mediation, litigation, and escalation procedures
- Non-Compete — restrictions on competitive activity post-termination
- Non-Solicitation — restrictions on soliciting employees or customers
- Warranty — representations, warranties, and disclaimers
For each clause type, provide 3 versions:
- Standard — balanced language protecting both parties fairly; suitable for most negotiations
- Protective — language that favors our side; use when negotiating from a position of strength or when risk exposure is high
- Minimum Acceptable — the bottom-line position; the least favorable terms we would accept before walking away
Note jurisdiction considerations per clause:
- Enforceability limitations in specific jurisdictions (e.g., non-compete restrictions vary widely by state)
- Mandatory legal requirements that override contractual terms
- Jurisdictions where certain clause types require specific language or formalities
Include usage guidance:
- When to use each version (standard vs. protective vs. minimum)
- Common negotiation patterns and fallback positions
- Red flags that indicate the other party's clause is unacceptable
Mark clauses requiring legal review:
- Flag any clause that involves regulatory compliance obligations
- Flag clauses with jurisdiction-specific enforceability concerns
- Flag clauses dealing with liability caps above or below industry norms
Write the artifact to .singularskills/legal/<project>/clause-library.md, starting with # Clause Library — <project>.
Include for each clause type:
- Clause Name and Purpose — what the clause does and why it matters
- Standard Version — balanced clause text
- Protective Version — clause text favoring our position
- Minimum Acceptable Version — bottom-line clause text
- Jurisdiction Notes — enforceability considerations by jurisdiction
- Usage Guidance — when to use which version
- Legal Review Required — yes/no with explanation
Output
The clause library written to .singularskills/legal/<project>/clause-library.md. Present a summary to the user highlighting:
- Total clause types covered
- Clauses flagged as requiring legal review before use
- Key jurisdiction-specific enforceability concerns
- Recommended starting position for each clause type
1---2name: legal-clause-library3description: Build or extend a library of approved contract clauses, each in standard, protective and minimum-acceptable versions with jurisdiction notes and usage guidance. Use when the user wants reusable fallback language their team can pull into any contract. Not for positions on one specific deal; see /legal-negotiation-prep.4metadata:5 source: https://skillmd.com/skills/bromso/legal-clause-library6 argument-hint: "[project] [--skip-checks]"7---89# Clause Library1011Build or extend a library of approved contract clauses for "$ARGUMENTS". Provide multiple versions of each clause type with jurisdiction considerations and usage guidance.1213> **Note:** AI-generated legal content does not constitute legal advice. All clauses should be reviewed by a qualified attorney before use in binding agreements.1415**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"legal-clause-library","workflow":"legal","phase":null,"project":"<project>","event":"skipped","artifact":"<artifact file>","note":"<reason or \"none given\">"}`.1617## Prerequisites1819None — this is a utility skill.2021## Process22231. **Determine scope:**24 - Parse "<project>" to identify which clause types or contract context to focus on25 - If a clause library already exists at `.singularskills/legal/<project>/clause-library.md`, read it and extend rather than replace26272. **Organize clauses by type:**28 - **Indemnification** — allocation of liability for third-party claims29 - **Limitation of Liability** — caps on damages and liability exposure30 - **Confidentiality** — scope, duration, and exceptions for confidential information31 - **Termination** — rights, notice periods, cure periods, and post-termination obligations32 - **IP Assignment** — ownership and assignment of intellectual property created under the agreement33 - **Data Protection** — data processing obligations, security requirements, and breach notification34 - **Force Majeure** — excused performance due to extraordinary events beyond control35 - **Governing Law** — choice of law and venue selection36 - **Dispute Resolution** — arbitration, mediation, litigation, and escalation procedures37 - **Non-Compete** — restrictions on competitive activity post-termination38 - **Non-Solicitation** — restrictions on soliciting employees or customers39 - **Warranty** — representations, warranties, and disclaimers40413. **For each clause type, provide 3 versions:**42 - **Standard** — balanced language protecting both parties fairly; suitable for most negotiations43 - **Protective** — language that favors our side; use when negotiating from a position of strength or when risk exposure is high44 - **Minimum Acceptable** — the bottom-line position; the least favorable terms we would accept before walking away45464. **Note jurisdiction considerations per clause:**47 - Enforceability limitations in specific jurisdictions (e.g., non-compete restrictions vary widely by state)48 - Mandatory legal requirements that override contractual terms49 - Jurisdictions where certain clause types require specific language or formalities50515. **Include usage guidance:**52 - When to use each version (standard vs. protective vs. minimum)53 - Common negotiation patterns and fallback positions54 - Red flags that indicate the other party's clause is unacceptable55566. **Mark clauses requiring legal review:**57 - Flag any clause that involves regulatory compliance obligations58 - Flag clauses with jurisdiction-specific enforceability concerns59 - Flag clauses dealing with liability caps above or below industry norms60617. **Write the artifact** to `.singularskills/legal/<project>/clause-library.md`, starting with `# Clause Library — <project>`.6263 Include for each clause type:64 - **Clause Name and Purpose** — what the clause does and why it matters65 - **Standard Version** — balanced clause text66 - **Protective Version** — clause text favoring our position67 - **Minimum Acceptable Version** — bottom-line clause text68 - **Jurisdiction Notes** — enforceability considerations by jurisdiction69 - **Usage Guidance** — when to use which version70 - **Legal Review Required** — yes/no with explanation7172## Output7374The clause library written to `.singularskills/legal/<project>/clause-library.md`. Present a summary to the user highlighting:75- Total clause types covered76- Clauses flagged as requiring legal review before use77- Key jurisdiction-specific enforceability concerns78- Recommended starting position for each clause type