missing-protections
Audits a contract against type-specific protection checklists to find gaps, then provides ready-to-insert clause language for each missing protection. Use when a user wants to know what protections are absent from their contract. Trigger with "/missing-protections" or "what protections is this contract missing".
What this skill does
# Missing Protections — Contract Gap Finder
Audits a contract against a comprehensive checklist of protections that should
be present based on the contract type, flags every gap, rates its urgency, and
provides ready-to-insert clause language drawn from industry-standard templates.
## Overview
What a contract does not say is often more dangerous than what it does. Silence
on key protections means the default rules of the governing jurisdiction apply
— and those defaults rarely favor the weaker party.
This skill checks the contract against 15 universal protections that every
agreement should contain, plus type-specific protections tailored to the
contract category. For each missing protection, it explains the risk of
omission and provides suggested clause language based on CommonPaper open-source
templates (CC BY 4.0) and widely accepted market standards.
## Prerequisites
- A contract must be provided as a file path or pasted text.
- The user should specify which party they represent. If not specified, the
analysis defaults to the party that did not draft the contract.
## Instructions
1. **Read the full contract.** Use the Read tool if a file path is provided.
2. **Classify the contract type** to select the appropriate checklist:
- Employment Agreement
- Independent Contractor / Freelance Agreement
- Non-Disclosure Agreement (NDA)
- Master Services Agreement (MSA)
- Software License / SaaS Agreement
- Terms of Service / Terms of Use
- Partnership / Joint Venture Agreement
- Other (apply universal checklist only)
3. **Check the 15 universal protections.** Every contract should address:
| # | Protection | What to Look For |
|---|-----------|-----------------|
| 1 | **Limitation of Liability** | Cap on total damages (ideally mutual) |
| 2 | **Indemnification Scope** | Clear boundaries on who indemnifies whom and for what |
| 3 | **Termination for Convenience** | Either party can exit with reasonable notice |
| 4 | **Termination for Cause** | Right to terminate if the other party breaches, with cure period |
| 5 | **Cure Period** | Time to fix a breach before termination triggers |
| 6 | **Notice Requirements** | How and where notices must be delivered |
| 7 | **Force Majeure** | Excuse for non-performance due to extraordinary events |
| 8 | **Dispute Resolution** | Defined process (mediation, arbitration, or litigation) |
| 9 | **Governing Law** | Which jurisdiction's law applies |
| 10 | **Assignment Restrictions** | Cannot assign without consent |
| 11 | **Amendment Requirements** | Changes require written mutual agreement |
| 12 | **Severability** | Invalid clauses do not void the entire contract |
| 13 | **Entire Agreement** | Contract supersedes prior discussions |
| 14 | **Confidentiality** | Protection for sensitive information exchanged |
| 15 | **Data Protection** | Compliance with applicable privacy laws (GDPR, CCPA) |
4. **Check type-specific protections.** Apply the additional checklist for the
classified contract type:
**Employment Agreements:** Background IP carve-out, overtime/exempt
classification, benefits vesting schedule, post-termination obligations
clarity, whistleblower protections, non-compete geographic/temporal limits.
**Freelance/Contractor Agreements:** Payment timeline (net-30 or less),
kill fee / cancellation fee, scope change process, deliverable acceptance
criteria, independent contractor status affirmation, equipment/expense
reimbursement.
**NDAs:** Mutual vs. unilateral clarity, residual knowledge carve-out,
compelled disclosure exception, return/destruction of materials, reasonable
duration (2-3 years standard), carve-out for publicly available information.
**SaaS/Software Agreements:** SLA with uptime commitment, data portability
on termination, data breach notification timeline, sub-processor disclosure,
price change notice period, API deprecation notice.
**MSAs:** SOW incorporation mechanism, change order process, acceptance
testing period, warranty period, insurance requirements.
5. **Rate each missing protection by urgency:**
| Rating | Criteria |
|--------|----------|
| **CRITICAL** | Absence creates immediate, significant financial or legal risk. Must be added before signing. |
| **IMPORTANT** | Absence creates meaningful risk that should be addressed. Negotiate to include. |
| **RECOMMENDED** | Best practice that strengthens position. Include if possible. |
6. **Provide suggested clause language.** For each missing protection rated
CRITICAL or IMPORTANT, provide:
- A ready-to-insert clause written in standard contract language
- A note on where it should be placed in the contract
- The source or pattern it follows (e.g., "Based on CommonPaper MSA v4,
Section 8.3")
7. **Summarize the protection coverage score:**
```
Universal protections present: X / 15
Type-specific protections present: Y / Z
Overall coverage: [percentage]%
```
## Output
**Filename:** `MISSING-PROTECTIONS-{contract-name-or-type}.md`
```
# Missing Protections Report
## Contract Summary
## Protection Coverage Score
| Category | Present | Missing | Coverage |
## Critical Missing Protections
### 1. [Protection Name]
**Risk of Omission:** [explanation]
**Suggested Clause:**
> [ready-to-insert language]
**Placement:** [where in contract]
**Source:** [reference]
## Important Missing Protections
### ...
## Recommended Missing Protections
### ...
## Complete Checklist
| # | Protection | Status | Urgency |
## Disclaimer
```
## Error Handling
| Failure Mode | Cause | Resolution |
|--------------|-------|------------|
| Unclassifiable contract | Contract type does not match standard categories | Apply universal checklist only; note limitation |
| Partial coverage | Protection is addressed but incompletely | Mark as "Partial" rather than present or missing; explain the gap |
| Jurisdiction-specific protections | Some protections are required by local law | Note when a protection is legally required vs. best practice |
| Referenced exhibits missing | Contract references schedules with additional terms | Note that coverage assessment is based on available text only |
| Conflicting clauses | Two sections address the same protection differently | Flag the conflict as a separate finding |
## Examples
**Example 1 — Freelance agreement missing critical protections:**
> User: What protections is this freelance contract missing? I am the freelancer.
```
Protection Coverage: 8/15 universal, 2/6 type-specific (48%)
CRITICAL Missing Protections:
1. Kill Fee / Cancellation Clause
Risk: Client can cancel the project at any time with no compensation
for work already completed or opportunity cost.
Suggested Clause:
> "If Client terminates this Agreement for convenience prior to
> completion of the Services, Client shall pay Contractor for all
> work completed through the termination date plus a cancellation
> fee equal to 25% of the remaining contract value."
Placement: Section 5 (Payment Terms)
Source: Based on Freelancers Union standard contract, Section 4.2
2. Payment Timeline
Risk: No payment deadline specified. Default rules vary by jurisdiction
and may allow payment delays of 60-90 days or more.
Suggested Clause:
> "Client shall pay all invoices within thirty (30) calendar days of
> receipt. Invoices unpaid after 30 days shall accrue interest at the
> rate of 1.5% per month or the maximum rate permitted by law."
Placement: Section 5 (Payment Terms)
Source: Based on CommonPaper Contractor Agreement v3, Section 5.1
```
**Example 2 — SaaS agreement with partial protections:**
> User: Check ~/contracts/vendor-saas-agreement.pdf for missing protections.
```
CRITICAL: No data breach notification timeline.
The contract mentions "reasonable" notification but sets no deadline.
Under GDPR Article 33, processors must notifRelated in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.