Use this skill when drafting NDAs, MSAs, SaaS agreements, licensing terms, or redlining contracts. Triggers on contract drafting, NDA, MSA, SaaS agreement, licensing, redlining, terms of service, data processing agreements, and any task requiring commercial contract creation or review.
When this skill is activated, always start your first response with the 🧢 emoji.
Disclaimer: This skill provides general guidance on commercial contract structure and drafting best practices. It is NOT legal advice. Always have qualified legal counsel review contracts before signing or sending them to counterparties.
Commercial contracts are the binding agreements that govern business relationships. Good contracts prevent disputes by making expectations, obligations, and risk allocation explicit. This skill covers the structure, key clauses, and drafting process for the most common commercial agreements - NDAs, MSAs, SaaS subscriptions, licensing agreements, and data processing addendums - and the process of reviewing and redlining contracts received from counterparties.
Trigger this skill when the user:
Do NOT trigger this skill for:
Clarity over legalese - Plain language reduces disputes. Every obligation, right, and restriction should be understandable on first reading. If a clause requires a lawyer to decode, rewrite it. Legalese that obscures meaning creates ambiguity that parties exploit in disputes.
Define all terms - Every capitalized term must appear in a Definitions section or be defined on first use. Undefined terms invite competing interpretations. "Confidential Information," "Intellectual Property," "Affiliate," and "Services" are the most commonly contested undefined terms.
Risk allocation must be explicit - Contracts exist to allocate risk. Who bears the cost of a data breach? Who indemnifies whom for IP infringement claims? What is the liability cap? If risk allocation is implicit or absent, courts default to interpretations that may not match what either party intended.
Standard terms reduce negotiation - Using market-standard positions (e.g., mutual NDA, uncapped IP indemnity, 12-month liability cap for SaaS) speeds up deals. Know which clauses are standard so you can focus negotiation energy on the genuinely non-standard asks.
Version control everything - Every draft should be dated and versioned. Track changes between drafts. Maintain a redline history. In a dispute, the negotiation history can be used to interpret ambiguous terms (the "course of dealing" doctrine).
Every commercial contract shares a common skeleton:
Indemnification - Party A agrees to defend and pay costs if Party B is sued by a third party because of Party A's breach or IP. Usually mutual for IP, one-sided for gross negligence.
Limitation of liability - Caps total recovery at a multiple of fees paid (12 months is standard for SaaS). Always carve out: death/personal injury, willful misconduct, confidentiality breaches, and IP indemnity from the cap.
Representations and warranties - "We represent that our software does not infringe third-party IP." Breach of a warranty triggers indemnification or termination rights.
Governing law and jurisdiction - Which state/country's law applies and where disputes are resolved. Avoid agreeing to the other party's home jurisdiction.
Assignment - Whether either party can transfer the contract to a third party (e.g., in a merger or acquisition). Standard position: neither party may assign without consent, except to an acquirer of all or substantially all assets.
| Risk | Typical allocation |
|---|---|
| IP infringement by vendor's product | Vendor indemnifies customer |
| Customer's misuse of the product | Customer indemnifies vendor |
| Data breach caused by vendor | Vendor liable, often uncapped |
| Force majeure (pandemic, natural disaster) | Neither party liable |
| Consequential damages | Mutually excluded (carve out fraud) |
| Death / personal injury | Neither party may cap |
All changes to a signed contract must be in writing, signed by both parties, and reference the original agreement. Verbal amendments are unenforceable in most jurisdictions. Use a formal Amendment or Change Order template with a sequential number (Amendment No. 1, Amendment No. 2) to maintain a clear audit trail.
A mutual NDA protects confidential information exchanged in both directions. Key sections and what belongs in each:
1. Definition of Confidential Information
- Broad enough to cover all sensitive info
- Exclude: public domain, independently developed, received from third party,
required to be disclosed by law (with notice obligation)
2. Obligations of receiving party
- Use only for the Permitted Purpose
- Protect with at least the same care as own confidential info (not less than
reasonable care)
- Share only with employees/contractors on need-to-know basis
- Ensure recipients are bound by equivalent obligations
3. Term
- Duration of disclosure period (e.g., 2 years)
- Survival of confidentiality obligations (typically 3-5 years after expiry)
4. Return / destruction
- Upon request or expiry, return or certify destruction of materials
5. Remedies
- Acknowledge that breach causes irreparable harm - injunctive relief available
without bond requirement
Mutual NDA checklist:
A Master Services Agreement governs the overall relationship; Statements of Work (SOWs) or Order Forms attach to it for specific engagements.
MSA core sections:
IP ownership decision tree:
SaaS agreements govern access to hosted software. Key distinctions from on-premise