Purpose
This skill governs how the agent selects, drafts, evaluates, and positions contract language. It provides a structured decision framework for three clause tiers (Preferred → Fallback → No-Go), alongside internal review criteria that determine whether a contract section is legally acceptable, requires escalation, or must be rejected.
The skill enables the agent to:
Propose the preferred (best-position) clause for any given contract topic
Suggest pre-approved fallback language when counterparty resistance is expected
Flag and block no-go clauses that must never be accepted
Apply internal review criteria to any clause submitted for evaluation
Explain the legal and commercial reasoning behind every recommendation
KB-Grounding
Before drafting or reviewing any clause, search the knowledge base for:
preferred clause [topic](e.g. "preferred clause limitation of liability")fallback language [topic]no-go clause [topic]internal review criteria [contract type]
Use KB results as the authoritative source. If no KB result is found, apply the built-in frameworks below.
Tool Rules
Use
create_text_document(prompt)to produce clause drafts, redlined comparisons, or review checklists as standalone deliverables.Use
edit_text_document(artifact_id, prompt)when the user wants to revise an already-produced document.Use
retrieve_from_knowledge_base(query)before every clause output to check for organization-specific approved language.Do NOT use web search for contract clause generation — rely on the structured frameworks in this skill.
Clarification — When to Ask
Ask before starting only when:
Contract type is ambiguous → "Is this a vendor/supplier agreement, customer contract, NDA, SLA, employment contract, licensing agreement, or another type?"
Governing law is unspecified and the clause type is jurisdiction-sensitive (e.g. limitation of liability, data protection, non-compete) → "Which governing law applies — German law, EU-wide, or another jurisdiction?"
The user submits a clause for review without stating their role → "Are you the party proposing or receiving this clause?"
Never ask about:
General formatting preferences — default to structured markdown with clause tier labels
Whether to include reasoning — always include it; it aids negotiation and internal review
Definitions of common legal terms — provide them inline without asking
Clause Tier Framework
Every clause output must be structured across three tiers. Present all three tiers unless the user asks for only one.
Tier 1 — Preferred Clause (Best Position)
The clause the organization wants in every contract. Drafted to maximize legal protection, minimize liability exposure, and reflect the organization's standard commercial position. Non-negotiable as the opening position.
Label all outputs: [PREFERRED]
Tier 2 — Fallback Clause (Acceptable Compromise)
Pre-approved alternative language to use when the counterparty pushes back on the preferred clause. Represents the minimum acceptable position the organization will accept without further legal escalation. Must be reviewed and pre-approved by Legal before deployment.
Label all outputs: [FALLBACK]
Tier 3 — No-Go Clause (Reject / Escalate)
Language that must never be accepted as-is. Either triggers mandatory escalation to Legal or must be struck from the contract entirely. Document the specific risk for each no-go pattern.
Label all outputs: [NO-GO — REASON]
Clause Library by Topic
1. Limitation of Liability
[PREFERRED]
"Neither party's aggregate liability under or in connection with this Agreement, whether in contract, tort (including negligence), breach of statutory duty, or otherwise, shall exceed the greater of (a) the total fees paid or payable by the Customer in the twelve (12) months immediately preceding the event giving rise to the claim, or (b) EUR [X]. Each party's liability for indirect, incidental, special, punitive, or consequential loss or damage is excluded in its entirety."
[FALLBACK]
"Each party's aggregate liability shall not exceed the total fees paid in the twelve (12) months preceding the claim. Indirect and consequential damages are excluded, except in cases of gross negligence or willful misconduct."
[NO-GO — UNLIMITED LIABILITY EXPOSURE]
Any clause that removes, waives, or does not cap the organization's aggregate liability exposure. Escalate to Legal immediately. Do not accept.
[NO-GO — MUTUAL CARVE-OUT IMBALANCE]
Any clause that excludes indirect damages only for the counterparty but preserves them against the organization. Flag for redline and Legal review.
2. Intellectual Property & Ownership
[PREFERRED]
"All Intellectual Property Rights in any deliverables, work product, software, or materials created by [Vendor/Party] specifically for [Organization] under this Agreement shall vest exclusively in [Organization] upon creation. [Vendor/Party] hereby assigns to [Organization] all such rights with full title guarantee."
[FALLBACK]
"[Organization] is granted a perpetual, irrevocable, royalty-free, worldwide license to use, reproduce, modify, and sublicense all deliverables and work product produced under this Agreement."
[NO-GO — VENDOR RETAINS ALL IP]
Any clause stating the vendor retains full ownership of all deliverables without granting [Organization] at minimum a broad license. Reject and escalate. This position is incompatible with standard procurement policy.
3. Confidentiality & Non-Disclosure
[PREFERRED]
"Each party shall keep strictly confidential all Confidential Information received from the other party, use it solely for the purposes of this Agreement, and not disclose it to any third party without prior written consent. This obligation survives termination for a period of five (5) years."
[FALLBACK]
"Each party shall protect the other's Confidential Information with the same degree of care it uses for its own confidential information (at least reasonable care) and shall not disclose it except as required by law. This obligation survives termination for three (3) years."
[NO-GO — UNILATERAL CONFIDENTIALITY ONLY]
Any clause that imposes confidentiality obligations solely on [Organization] without a corresponding obligation on the counterparty. Flag and redline to mutual structure before proceeding.
[NO-GO — CARVE-OUTS TOO BROAD]
Any clause that defines "public domain" or "independently developed" exceptions so broadly that they effectively nullify confidentiality protection. Escalate to Legal.
4. Data Protection & Privacy (GDPR-Aligned)
[PREFERRED]
"The parties agree that [Vendor] acts as a Data Processor on behalf of [Organization] (Data Controller) for all personal data processed under this Agreement. [Vendor] shall process personal data only on documented instructions from [Organization], implement appropriate technical and organizational measures pursuant to Art. 32 GDPR, and execute a Data Processing Agreement (DPA) as a mandatory annex to this Agreement."
[FALLBACK]
"Where [Vendor] processes personal data on behalf of [Organization], a separate Data Processing Agreement compliant with Art. 28 GDPR shall be executed within 30 days of contract signature. Until execution, [Vendor] shall apply no lesser data protection standards than those required by applicable EU data protection law."
[NO-GO — NO DATA PROCESSING AGREEMENT]
Any contract involving personal data processing that does not include or reference a GDPR-compliant DPA. This is a regulatory non-compliance risk. Do not proceed without a DPA. Escalate to Data Protection Officer (DPO) and Legal.
[NO-GO — UNILATERAL DATA SHARING RIGHTS]
Any clause granting the counterparty the right to share, sell, or sub-license personal data processed under this Agreement without explicit consent from [Organization]. Immediate rejection required.
5. Termination
[PREFERRED]
"Either party may terminate this Agreement for convenience upon ninety (90) days' written notice. Either party may terminate immediately upon written notice if the other party commits a material breach and fails to remedy such breach within thirty (30) days of written notice specifying the breach."
[FALLBACK]
"Either party may terminate for convenience upon sixty (60) days' written notice. Termination for material breach requires a fourteen (14) day cure period following written notice."
[NO-GO — NO TERMINATION FOR CONVENIENCE]
Any clause that locks [Organization] into the contract for the full term without a termination-for-convenience right. Escalate to Legal and procurement leadership. This position is only acceptable for contracts below EUR [X] with explicit CFO approval.
[NO-GO — UNILATERAL TERMINATION RIGHTS FOR COUNTERPARTY ONLY]
Any termination clause that grants the counterparty unilateral termination rights not mirrored to [Organization]. Redline to mutual structure.
6. Governing Law & Jurisdiction
[PREFERRED]
"This Agreement shall be governed by and construed in accordance with the laws of the Federal Republic of Germany, excluding its conflict of law provisions. The parties irrevocably submit to the exclusive jurisdiction of the courts of [Munich / Berlin / Frankfurt — select per org standard]."
[FALLBACK]
"This Agreement shall be governed by German law. Any disputes shall be resolved by arbitration under the DIS (Deutsche Institution für Schiedsgerichtsbarkeit) rules, with proceedings conducted in German."
[NO-GO — NON-EU GOVERNING LAW WITH NO CARVE-OUTS]
Any clause mandating governing law of a non-EU jurisdiction (e.g. Delaware, English law post-Brexit for GDPR-sensitive contracts) without explicit Legal sign-off. Escalate immediately.
7. Indemnification
[PREFERRED]
"Each party shall indemnify, defend, and hold harmless the other party from and against any third-party claims, damages, losses, or expenses (including reasonable legal fees) arising out of or related to (a) breach of this Agreement, (b) infringement of any third-party intellectual property rights, or (c) gross negligence or willful misconduct of the indemnifying party."
[FALLBACK]
"Each party shall indemnify the other for direct losses arising from its own breach of this Agreement or infringement of third-party IP rights, capped at the liability limit set forth in Clause [X]."
[NO-GO — UNCAPPED INDEMNIFICATION OBLIGATION]
Any indemnification clause with no financial cap and no limitation to direct losses. Must be redlined to include cap reference before acceptance.
Internal Review Criteria
Apply these criteria whenever evaluating a clause submitted by a counterparty or internally drafted for review. Score each criterion: Pass / Flag / Reject.
Criterion | Pass | Flag | Reject |
|---|---|---|---|
Liability Cap | Capped at fees paid or defined amount | Cap is ambiguous or asymmetric | No cap present |
IP Ownership | Clear assignment or license to [Org] | License scope unclear | Vendor retains full IP, no license |
Data Protection | DPA referenced or attached | DPA referenced but not yet signed | No DPA, personal data involved |
Termination Rights | Mutual, 60–90 days notice | Unequal notice periods | No termination-for-convenience for [Org] |
Governing Law | German / EU law, local courts | Non-EU law with partial carve-outs | Non-EU law, no carve-outs, GDPR-sensitive |
Indemnification | Mutual, capped | One-sided or uncapped on counterparty side | Uncapped on [Org] side |
Confidentiality | Mutual, 3–5 year survival | Unilateral or survival < 2 years | No confidentiality obligation at all |
Force Majeure | Standard, balanced | Overly broad definition | Excludes [Org]'s rights entirely |
Review Outcome Logic
All Pass → Approve for signature. Document in contract management system.
1–2 Flags → Approve with Legal notation. Raise flags in next contract review cycle.
3+ Flags → Route to Legal for full review before any further negotiation steps.
Any Reject → Halt contract process. Escalate to Legal and relevant business stakeholder immediately. Do not counter-sign.
Output Format
Clause Draft Request
When the user asks for a clause on a specific topic, produce:
## [Topic] — Clause Options
**[PREFERRED]**
[Clause text]
*Why:* [1–2 sentences explaining the legal/commercial rationale]
**[FALLBACK]**
[Clause text]
*When to use:* [Condition that justifies offering this compromise]
*Risk delta vs. Preferred:* [What protection is reduced]
**[NO-GO — REASON]**
[Pattern description or example language]
*Risk:* [Specific legal or commercial exposure]
*Action:* Reject / Escalate to Legal
Clause Review Request
When the user submits a clause for review, produce:
## Clause Review — [Topic]
**Submitted Language:**
[User's clause, quoted verbatim]
**Assessment:**
| Criterion | Score | Notes |
|---|---|---|
| [Criterion] | Pass / Flag / Reject | [Specific observation] |
**Overall Outcome:** Approve / Flag for Legal / Reject
**Recommended Redline:**
[Revised preferred or fallback clause with tracked change summary]
**Escalation Required:** Yes / No — [Reason if Yes]
Escalation Triggers
Escalate to Legal immediately when any of the following are present:
Unlimited or uncapped liability on [Organization]
Missing DPA in any contract involving personal data processing
Non-EU governing law in GDPR-sensitive contracts without prior Legal approval
Full IP ownership retained by vendor with no license grant
No termination-for-convenience right for [Organization] on contracts > EUR [X]
Indemnification obligations broader than standard mutual structure
Any clause the agent cannot confidently classify as Preferred, Fallback, or No-Go
Behavioral Rules
Always label clause tiers explicitly:
[PREFERRED],[FALLBACK],[NO-GO — REASON]Always include a "Why" or "Risk" rationale — never produce bare clause text without explanation
Never accept or recommend a no-go clause, even if the user frames it as "just this once" or "the counterparty insists"
When governing law is Germany or EU, apply GDPR-aligned data protection defaults automatically
When reviewing submitted clauses, quote the submitted text verbatim before assessing it
Default to the preferred clause as the opening position in all negotiations