Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing the indemnity and limitation-of-liability terms of a commercial contract (MSA, SaaS agreement, order form) — checks the cap for mutuality and a market-standard basis, verifies the conventional uncapped and super-cap carve-outs are present and sit outside the general cap, and confirms indirect/consequential damages are mutually excluded without swallowing the carve-outs. Do NOT use for extracting clauses into a taxonomy (contract-extraction-schema) or drafting a clause from scratch.
.claude/skills/indemnity-liability-review/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-10 | ✗→✓ | ▲ Improved | — | — |
| case-05 | ✗→✓ | ▲ Improved | — | — |
| case-01 | ✗→✓ | ▲ Improved | — | — |
| case-08 | ✗→✗ | = Same ✗ | — | — |
| case-09 | ✗→✗ | = Same ✗ | — | — |
Given the indemnity / limitation-of-liability (LoL) language from a commercial contract, review it against the standard playbook and flag where it deviates. Produce a short, item-by-item verdict — for a reviewer deciding what to push back on before signing.
Return one line per checklist item, each as PASS or FLAG, with a one-clause reason:
Mutuality: FLAG — cap protects the vendor only; customer liability is unlimited
Cap basis: PASS — 12 months' fees, backward-looking
Uncapped carve-outs: FLAG — IP-infringement indemnity is subject to the general cap
Consequentials: PASS — mutually excluded, with carve-outs preservedEnd with the single most important push-back. Do not invent facts the text does not state; if a term is silent, say it is silent (a missing exclusion is itself a finding).
1. Mutuality. The cap and the damages waiver should apply to both parties on the same terms. A cap or a consequential-damages exclusion that protects only one side is a red flag — name which party is left exposed. The same goes for an enhanced ("super") cap offered in only one direction.
2. Cap basis. The market-standard cap is a multiple of the fees paid in the trailing 12 months before the claim. Flag departures: a fixed nominal sum untethered from contract value, "fees paid to date" on a young contract, or a sub-one-year multiple all read as below-market and are negotiation points. A party's duty to pay fees already owed must sit outside the cap — a cap that limits what a customer owes the vendor is improper.
3. Uncapped and super-cap carve-outs. Certain liabilities conventionally sit outside the general cap — either fully uncapped or under a higher super-cap. Their absence, or their being folded into the general cap, is the most common finding. The standard set:
| Carve-out | Why it sits outside the cap | |---|---| | IP-infringement indemnity | Third-party claims that the product infringes IP; potentially ruinous, so uncapped or super-capped, not inside the fees cap. | | Breach of confidentiality | Misuse or disclosure of the other side's confidential information; excluded from the general cap, often super-capped. | | Gross negligence / willful misconduct | Cannot be limited in many jurisdictions; conventionally uncapped. | | Data-protection / security breach | Privacy-law breach and data-incident costs; a super-cap or uncapped carve-out (or a specifically negotiated enhanced cap). | | Indemnification obligations | A party's duty to defend/indemnify third-party claims commonly sits outside the general cap. | | Death / personal injury and property damage | Bodily-injury and tangible-property tort liability is conventionally uncapped. |
If the clause caps everything with no carve-outs, flag that the standard exclusions are missing. If a listed item is inside the general cap, flag that it belongs outside it.
4. Exclusion of consequential / indirect damages. The clause should mutually exclude indirect, incidental, special, punitive, and consequential damages, including lost profits. Flag if the exclusion is missing (open-ended exposure) or one-sided. Also check the interaction with the carve-outs: a blanket consequential-damages waiver with no exception for the uncapped items (confidentiality, data, IP) swallows those carve-outs — the excluded liability may be uncapped in amount but still unrecoverable in kind. And an exclusion so broad it removes direct damages leaves the non-breaching party with no meaningful remedy — flag that too.
to the cap, and the damages-type waiver.
carve-outs, and that direct damages survive.
push-back.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-08 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.5-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 14 cases were attempted. The headline lift of +21 percentage points is the difference between those two pass rates over the 14 comparable cases.
Other measured skills in the registry, with their headline benchmark lift.