scholarly360/contract-intelligence · Archived

amendment-general

Requires that all changes to the contract be made in writing and signed by authorized representatives of both parties. Prevents informal or unauthorized alterations from undermining the agreed terms.

First seen Feb 21, 2026

Installation

$ npx skills add scholarly360/contract-intelligence --skill amendment-general

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from scholarly360/contract-intelligence · top by installs.

npx skills add scholarly360/contract-intelligence

Browse all from scholarly360/contract-intelligence

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,318 B
  • docs SUMMARY.md 224 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

Amendment Clause -- General

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


When to Activate

Activate this skill when the user:

  • Uploads or pastes a contract containing a Amendment clause
  • Asks to draft, redline, or improve a Amendment clause
  • Asks for a risk assessment of an existing Amendment provision
  • Mentions keywords: amendment clause, modification, contract change

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:

## Amendment 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

Amendment 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.