Missing-Clauses Detector
When to use this
Use this skill as a first-pass quality gate on any contract:
- After receiving a first draft from a counterparty — to check what they have omitted
- Before signing — to confirm the agreement is complete
- When assessing a historic agreement — to understand its gaps
- After generating a first draft via a drafting skill — to confirm completeness before sending
This skill identifies structural gaps. It is a completeness check, not a risk-in-existing-clauses review — run [[review-risk-flagging]] alongside it for the full picture.
Process
- Identify document type from the subject line, title, recitals, or the user's description (NDA, MSA, lease, employment agreement, SHA, services agreement, etc.)
- Load the standard skeleton for that document type — each document type has a minimum viable clause list (see below)
- Compare clause by clause: scan for each expected provision; note if absent, partially present, or fully present
- Categorize each gap:
- Mandatory: absence may make the contract invalid, unenforceable, or expose to regulatory penalty
- Strongly recommended: absence creates material legal risk or ambiguity
- Optional: standard market practice but not legally required; include if in scope for this deal type
Standard Clause Skeletons by Document Type
NDA (Non-Disclosure Agreement)
| Clause |
Category |
Why it matters |
| Parties and recitals |
Mandatory |
Defines who the obligation runs between |
| Definition of Confidential Information |
Mandatory |
Without it, the NDA protects nothing |
| Standard 4 exclusions (public domain, independent dev, lawful third party, court order) |
Mandatory |
Without exclusions, NDA is overbroad and potentially unenforceable |
| Permitted disclosure (need-to-know employees/advisors) |
Strongly recommended |
Prevents technical breach by normal business use |
| Obligations of the receiving party |
Mandatory |
The core of the NDA |
| Term and duration of obligations |
Strongly recommended |
Perpetual NDAs raise enforceability concerns; 2–5 years typical |
| Return/destruction on termination |
Strongly recommended |
Operational obligation; needed for data protection compliance |
| No license / no IP transfer |
Strongly recommended |
Avoids argument that disclosure implies license |
| Governing law and jurisdiction |
Mandatory |
Without it, forum disputes arise |
| Injunctive relief / remedies |
Strongly recommended |
Monetary damages rarely adequate for breach |
| Signature block and authority |
Mandatory |
No contract without valid execution |
| Entire agreement / no waiver |
Optional |
Good practice; prevents prior discussions being cited |
MSA (Master Services Agreement)
| Clause |
Category |
Why it matters |
| Parties, recitals, and definitions |
Mandatory |
— |
| Scope of services / SOW mechanism |
Mandatory |
Without it, what is the Provider obligated to do? |
| Fees, invoicing, payment terms |
Mandatory |
Core commercial terms |
| Term and termination (for convenience + cause) |
Mandatory |
Without termination rights, parties are locked in indefinitely |
| IP ownership and license |
Strongly recommended |
Work product ownership default varies by jurisdiction |
| Confidentiality |
Strongly recommended |
Overlap with standalone NDA if one exists |
| Liability cap |
Strongly recommended |
Without it, liability is unlimited |
| Indemnification (IP, data breach, breach of warranty) |
Strongly recommended |
Allocates risk for third-party claims |
| Warranties (authority, professional standard, no encumbrances) |
Strongly recommended |
Foundation for claims in breach |
| Data processing / DPA attachment |
Mandatory where personal data is involved |
GDPR/PDPL/UAE PDPL compliance |
| Governing law and dispute resolution |
Mandatory |
— |
| Force majeure |
Strongly recommended |
Especially for multi-year engagements |
| Assignment and change of control |
Strongly recommended |
Prevents counterparty selling the contract without consent |
| Entire agreement and amendment mechanism |
Optional but good practice |
— |
| Signature blocks |
Mandatory |
— |
Commercial Lease
| Clause |
Category |
Why it matters |
| Parties (landlord + tenant) and registered entity details |
Mandatory |
— |
| Premises description with plan |
Mandatory |
Defines the demise |
| Term and commencement date |
Mandatory |
— |
| Rent and payment terms |
Mandatory |
— |
| Permitted use |
Mandatory |
Defines scope of occupation |
| Repair obligations allocation |
Strongly recommended |
Without it, default statutory allocation applies (varies) |
| Service charge |
Strongly recommended for multi-tenanted buildings |
— |
| Insurance obligations |
Strongly recommended |
— |
| Assignment and subletting provisions |
Strongly recommended |
Default varies by jurisdiction |
| Forfeiture / termination rights |
Strongly recommended |
Without it, landlord's remedies are unclear |
| Reinstatement / make-good obligation |
Strongly recommended |
Expensive disputes without it |
| Governing law and dispute resolution |
Mandatory |
— |
| Signature blocks |
Mandatory |
— |
Employment Agreement
| Clause |
Category |
Why it matters |
| Job title and duties |
Mandatory |
Defines the engagement |
| Commencement date and probation period |
Mandatory |
Probation must be specified — defaults vary by jurisdiction |
| Compensation (salary, benefits, bonuses) |
Mandatory |
— |
| Working hours and location |
Mandatory |
Many jurisdictions regulate maximum hours |
| Leave entitlements (annual, sick, parental) |
Mandatory |
Statutory entitlements must be at least met |
| Termination notice periods |
Mandatory |
Statutory minimums apply; contract must be at least equal |
| End-of-service gratuity (MENA) |
Mandatory in KSA, UAE, LB, EG |
Statutory calculation; omission creates liability |
| Confidentiality |
Strongly recommended |
— |
| IP assignment |
Strongly recommended |
Default varies by jurisdiction |
| Non-compete / non-solicitation |
Optional (enforceability depends on jurisdiction) |
— |
| Governing law |
Mandatory |
— |
| Signature block |
Mandatory |
— |
Jurisdictional Mandatory Clauses
Some provisions are not merely "best practice" — they are legally required or have specific local form requirements:
UAE (onshore)
- Governing law: UAE Federal Law No. 33 of 2021 (Labour Law) requires employment contracts in Arabic or bilingual
- Penalty clauses in commercial contracts: UAE Civil Code allows courts to adjust disproportionate penalties regardless of contract terms (Article 390 equivalent); draft as indemnification rather than liquidated damages where possible
- Real estate contracts: must be registered with the relevant Land Department to be effective against third parties
KSA
- Arbitration clauses: must specify (a) the arbitral institution (SCCA or ICC or other recognized body); (b) the seat; (c) the language; (d) the number of arbitrators. A clause saying only "disputes shall be referred to arbitration" is insufficient and courts will assume Saudi General Court jurisdiction
- Employment contracts: must be in Arabic; bilingual is acceptable; Arabic version prevails; must be registered with GOSI
- Commercial Agency agreements: must be registered with the Ministry of Commerce
Lebanon
- Bilateral commercial contracts of value ≥ LBP 1,000,000 (approx.): technically require written form under Article 254 of the Code of Obligations and Contracts (OCC) — though in practice this threshold is very low and most commercial practice is documented in writing regardless
- Real estate transfers: must be registered before the Land Registry; private sale agreements alone are not effective against third parties
- Commercial leases: Commercial Code and Law 160/1992 overlay private terms; some tenant rights cannot be waived
DIFC / ADGM
- Contracts can be governed by DIFC / ADGM law respectively; no requirement for Arabic
- DIFC Data Protection Law and ADGM Data Protection Regulations impose DPA requirements for any processing within those free zones
- For employment: DIFC Employment Law No. 2 of 2019 (amended) and ADGM Employment Regulations require written employment contracts
Output Format
| Missing clause |
Document type |
Category |
Why it matters |
Severity |
| Governing law |
MSA |
Mandatory |
Courts will apply default forum rule; may be adverse |
Critical |
| Data processing agreement |
MSA with personal data |
Mandatory |
GDPR/PDPL compliance obligation |
Critical |
| Liability cap |
Commercial services |
Strongly recommended |
Unlimited liability exposure |
High |
| Force majeure |
Multi-year lease |
Strongly recommended |
No protection against closure events |
Medium |
| Return/destruction |
NDA |
Strongly recommended |
Data protection compliance gap |
Medium |
Severity key: Critical = may make the contract unenforceable or expose to regulatory penalty; High = material legal risk; Medium = increased ambiguity or commercial risk; Low = best practice gap.
Limits
- This skill identifies structural gaps; it does not assess quality of clauses that are present — use [[review-risk-flagging]] for that
- Jurisdiction-specific mandatory provisions require verification against current law — statute amendments can change what is required
- Document type classification must be accurate; if the document type is ambiguous, ask before running the checklist
Related Skills
- [[review-risk-flagging]]
- [[review-msa-deep-review]]
- [[review-nda-quick-check]]
- [[review-unusual-terms-detector]]
- [[draft-contract-skeleton-builder]]
- [[review-indemnification-balance]]
1---2name: review-missing-clauses3description: Use when a contract needs a completeness check against the standard skeleton for its document type. Identifies absent mandatory, strongly recommended, and optional clauses across NDAs, MSAs, leases, employment agreements, and other common commercial instruments. Flags jurisdiction-specific mandatory provisions and links to drafting skills for remediation. Suitable as a first-pass quality gate before any detailed clause-by-clause review.4license: MIT5---67# Missing-Clauses Detector89## When to use this1011Use this skill as a first-pass quality gate on any contract:12- After receiving a first draft from a counterparty — to check what they have omitted13- Before signing — to confirm the agreement is complete14- When assessing a historic agreement — to understand its gaps15- After generating a first draft via a drafting skill — to confirm completeness before sending1617This skill identifies structural gaps. It is a completeness check, not a risk-in-existing-clauses review — run [[review-risk-flagging]] alongside it for the full picture.1819## Process20211. **Identify document type** from the subject line, title, recitals, or the user's description (NDA, MSA, lease, employment agreement, SHA, services agreement, etc.)222. **Load the standard skeleton** for that document type — each document type has a minimum viable clause list (see below)233. **Compare clause by clause**: scan for each expected provision; note if absent, partially present, or fully present244. **Categorize each gap**:25 - **Mandatory**: absence may make the contract invalid, unenforceable, or expose to regulatory penalty26 - **Strongly recommended**: absence creates material legal risk or ambiguity27 - **Optional**: standard market practice but not legally required; include if in scope for this deal type2829## Standard Clause Skeletons by Document Type3031### NDA (Non-Disclosure Agreement)3233| Clause | Category | Why it matters |34|---|---|---|35| Parties and recitals | Mandatory | Defines who the obligation runs between |36| Definition of Confidential Information | Mandatory | Without it, the NDA protects nothing |37| Standard 4 exclusions (public domain, independent dev, lawful third party, court order) | Mandatory | Without exclusions, NDA is overbroad and potentially unenforceable |38| Permitted disclosure (need-to-know employees/advisors) | Strongly recommended | Prevents technical breach by normal business use |39| Obligations of the receiving party | Mandatory | The core of the NDA |40| Term and duration of obligations | Strongly recommended | Perpetual NDAs raise enforceability concerns; 2–5 years typical |41| Return/destruction on termination | Strongly recommended | Operational obligation; needed for data protection compliance |42| No license / no IP transfer | Strongly recommended | Avoids argument that disclosure implies license |43| Governing law and jurisdiction | Mandatory | Without it, forum disputes arise |44| Injunctive relief / remedies | Strongly recommended | Monetary damages rarely adequate for breach |45| Signature block and authority | Mandatory | No contract without valid execution |46| Entire agreement / no waiver | Optional | Good practice; prevents prior discussions being cited |4748### MSA (Master Services Agreement)4950| Clause | Category | Why it matters |51|---|---|---|52| Parties, recitals, and definitions | Mandatory | — |53| Scope of services / SOW mechanism | Mandatory | Without it, what is the Provider obligated to do? |54| Fees, invoicing, payment terms | Mandatory | Core commercial terms |55| Term and termination (for convenience + cause) | Mandatory | Without termination rights, parties are locked in indefinitely |56| IP ownership and license | Strongly recommended | Work product ownership default varies by jurisdiction |57| Confidentiality | Strongly recommended | Overlap with standalone NDA if one exists |58| Liability cap | Strongly recommended | Without it, liability is unlimited |59| Indemnification (IP, data breach, breach of warranty) | Strongly recommended | Allocates risk for third-party claims |60| Warranties (authority, professional standard, no encumbrances) | Strongly recommended | Foundation for claims in breach |61| Data processing / DPA attachment | Mandatory where personal data is involved | GDPR/PDPL/UAE PDPL compliance |62| Governing law and dispute resolution | Mandatory | — |63| Force majeure | Strongly recommended | Especially for multi-year engagements |64| Assignment and change of control | Strongly recommended | Prevents counterparty selling the contract without consent |65| Entire agreement and amendment mechanism | Optional but good practice | — |66| Signature blocks | Mandatory | — |6768### Commercial Lease6970| Clause | Category | Why it matters |71|---|---|---|72| Parties (landlord + tenant) and registered entity details | Mandatory | — |73| Premises description with plan | Mandatory | Defines the demise |74| Term and commencement date | Mandatory | — |75| Rent and payment terms | Mandatory | — |76| Permitted use | Mandatory | Defines scope of occupation |77| Repair obligations allocation | Strongly recommended | Without it, default statutory allocation applies (varies) |78| Service charge | Strongly recommended for multi-tenanted buildings | — |79| Insurance obligations | Strongly recommended | — |80| Assignment and subletting provisions | Strongly recommended | Default varies by jurisdiction |81| Forfeiture / termination rights | Strongly recommended | Without it, landlord's remedies are unclear |82| Reinstatement / make-good obligation | Strongly recommended | Expensive disputes without it |83| Governing law and dispute resolution | Mandatory | — |84| Signature blocks | Mandatory | — |8586### Employment Agreement8788| Clause | Category | Why it matters |89|---|---|---|90| Job title and duties | Mandatory | Defines the engagement |91| Commencement date and probation period | Mandatory | Probation must be specified — defaults vary by jurisdiction |92| Compensation (salary, benefits, bonuses) | Mandatory | — |93| Working hours and location | Mandatory | Many jurisdictions regulate maximum hours |94| Leave entitlements (annual, sick, parental) | Mandatory | Statutory entitlements must be at least met |95| Termination notice periods | Mandatory | Statutory minimums apply; contract must be at least equal |96| End-of-service gratuity (MENA) | Mandatory in KSA, UAE, LB, EG | Statutory calculation; omission creates liability |97| Confidentiality | Strongly recommended | — |98| IP assignment | Strongly recommended | Default varies by jurisdiction |99| Non-compete / non-solicitation | Optional (enforceability depends on jurisdiction) | — |100| Governing law | Mandatory | — |101| Signature block | Mandatory | — |102103## Jurisdictional Mandatory Clauses104105Some provisions are not merely "best practice" — they are legally required or have specific local form requirements:106107### UAE (onshore)108109- **Governing law**: UAE Federal Law No. 33 of 2021 (Labour Law) requires employment contracts in Arabic or bilingual110- **Penalty clauses** in commercial contracts: UAE Civil Code allows courts to adjust disproportionate penalties regardless of contract terms (Article 390 equivalent); draft as indemnification rather than liquidated damages where possible111- **Real estate contracts**: must be registered with the relevant Land Department to be effective against third parties112113### KSA114115- **Arbitration clauses**: must specify (a) the arbitral institution (SCCA or ICC or other recognized body); (b) the seat; (c) the language; (d) the number of arbitrators. A clause saying only "disputes shall be referred to arbitration" is insufficient and courts will assume Saudi General Court jurisdiction116- **Employment contracts**: must be in Arabic; bilingual is acceptable; Arabic version prevails; must be registered with GOSI117- **Commercial Agency agreements**: must be registered with the Ministry of Commerce118119### Lebanon120121- **Bilateral commercial contracts of value ≥ LBP 1,000,000 (approx.)**: technically require written form under Article 254 of the Code of Obligations and Contracts (OCC) — though in practice this threshold is very low and most commercial practice is documented in writing regardless122- **Real estate transfers**: must be registered before the Land Registry; private sale agreements alone are not effective against third parties123- **Commercial leases**: Commercial Code and Law 160/1992 overlay private terms; some tenant rights cannot be waived124125### DIFC / ADGM126127- Contracts can be governed by DIFC / ADGM law respectively; no requirement for Arabic128- DIFC Data Protection Law and ADGM Data Protection Regulations impose DPA requirements for any processing within those free zones129- For employment: DIFC Employment Law No. 2 of 2019 (amended) and ADGM Employment Regulations require written employment contracts130131## Output Format132133| Missing clause | Document type | Category | Why it matters | Severity |134|---|---|---|---|---|135| Governing law | MSA | Mandatory | Courts will apply default forum rule; may be adverse | Critical |136| Data processing agreement | MSA with personal data | Mandatory | GDPR/PDPL compliance obligation | Critical |137| Liability cap | Commercial services | Strongly recommended | Unlimited liability exposure | High |138| Force majeure | Multi-year lease | Strongly recommended | No protection against closure events | Medium |139| Return/destruction | NDA | Strongly recommended | Data protection compliance gap | Medium |140141Severity key: Critical = may make the contract unenforceable or expose to regulatory penalty; High = material legal risk; Medium = increased ambiguity or commercial risk; Low = best practice gap.142143## Limits144145- This skill identifies structural gaps; it does not assess quality of clauses that are present — use [[review-risk-flagging]] for that146- Jurisdiction-specific mandatory provisions require verification against current law — statute amendments can change what is required147- Document type classification must be accurate; if the document type is ambiguous, ask before running the checklist148149## Related Skills150151- [[review-risk-flagging]]152- [[review-msa-deep-review]]153- [[review-nda-quick-check]]154- [[review-unusual-terms-detector]]155- [[draft-contract-skeleton-builder]]156- [[review-indemnification-balance]]
sboghossian