scholarly360

force-majeure-general

Excuses or suspends performance obligations when extraordinary events beyond either party's control prevent fulfillment. Covers events such as natural disasters, wars, pandemics, government actions, and widespread infrastructure failures.

scholarly360 0 Updated 6mo ago

Resources

1
GitHub

Install

npx skillscat add scholarly360/contract-intelligence/force-majeure-general

Install via the SkillsCat registry.

About this skill

This skill analyzes and drafts Force Majeure clauses in general contracts, which excuse performance obligations during extraordinary events like natural disasters or pandemics. It helps users review existing language, assess risks, and generate balanced or party-favored contract provisions. Use it when working with contracts containing Force Majeure clauses or when drafting new ones.

SKILL.md

Force Majeure Clause -- General

This skill provides expert-level analysis and drafting assistance for
Force Majeure clauses in General contracts.


When to Activate

Activate this skill when the user:

  • Uploads or pastes a contract containing a Force Majeure clause
  • Asks to draft, redline, or improve a Force Majeure clause
  • Asks for a risk assessment of an existing Force Majeure provision
  • Mentions keywords: force majeure, act of God, unforeseeable circumstances

Workflow

Step 1 -- Intake

Ask the user (if not already provided):

  1. Which party are you representing? (e.g., vendor, client, buyer, seller)
  2. Jurisdiction governing the contract? (e.g., New York, California, England & Wales)
  3. Is this a draft for review or should I generate fresh language?

Step 2 -- Analysis

If reviewing existing language, output the following structure:

## Force Majeure Clause Analysis

### Plain-Language Summary
[2-3 sentence plain-English description of what the clause does]

### Key Provisions Identified
- [Provision 1]
- [Provision 2]

### Risk Assessment
| Item | Risk Level | Notes |
|------|-----------|-------|
| [item] | High / Medium / Low | [explanation] |

### Recommended Redlines
[Specific suggested changes with rationale]

### Market Standard Comparison
[How this clause compares to typical General market standard]

Step 3 -- Drafting

If generating new language, produce:

  1. Balanced version (neither party-favored)
  2. Favorable to client version
  3. Negotiation notes -- what the other side will likely push back on

Force Majeure Playbook -- General

See scripts/playbook.md for detailed clause-specific guidance,
fallback positions, jurisdiction-specific notes, and precedent language.


Important Notes

  • Always caveat that output is not legal advice and should be reviewed by qualified counsel.
  • Flag any provisions that may be unenforceable or jurisdiction-specific.
  • When jurisdiction is unknown, apply general common-law principles and note assumptions.