/legal-contract-negotiation-review
Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions.
$ npx -y skills add CoWork-OS/CoWork-OS --skill legal-contract-negotiation-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/legal-contract-negotiation-review
Context preview
The summary Claude sees to decide when to auto-load this skill.
Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions.
SKILL.md
legal-contract-negotiation-review.SKILL.mdname: legal-contract-negotiation-review
description: "Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions."
Legal Contract Negotiation Review
Purpose
Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions.
Routing
- Use when: Use for contract markups, last-minute deal term demands, or clause-by-clause negotiation defense work.
- Do not use when: Do not use for pure legal research questions that do not require document comparison.
- Outputs: Clause matrix, severity-ranked recommendations, counter-language, and a written negotiation brief.
- Success criteria: Finds cross-document conflicts, produces actionable counterpositions, and writes the report artifact.
Trigger Examples
Positive
- Use the legal-contract-negotiation-review skill for this request.
- Help me with legal contract negotiation review.
- Use for contract markups, last-minute deal term demands, or clause-by-clause negotiation defense work.
- Legal Contract Negotiation Review: provide an actionable result.
Negative
- Do not use for pure legal research questions that do not require document comparison.
- Do not use legal-contract-negotiation-review for unrelated requests.
- This request is outside legal contract negotiation review scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | agreement_path | string | No | Optional explicit path to the main agreement (DOCX/PDF/TXT) | | disclosure_schedules_path | string | No | Optional explicit path to disclosure schedules or side letter | | counterparty_changes_path | string | No | Optional explicit path to counterparty redline or demand letter | | client_side | select | No | Which side you represent | | output_report_path | string | No | Where to write the negotiation analysis markdown | | output_docx_path | string | No | Optional path for a clean revised DOCX draft |
Runtime Prompt
- Current runtime prompt length: 2482 characters.
- Runtime prompt is defined directly in `../legal-contract-negotiation-review.json`.
Read more
name: legal-contract-negotiation-review description: "Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions."
Legal Contract Negotiation Review
Purpose
Analyze counterparty contract changes against agreement/schedules, flag conflicts, and produce severity-rated counterpositions.
Routing
- Use when: Use for contract markups, last-minute deal term demands, or clause-by-clause negotiation defense work.
- Do not use when: Do not use for pure legal research questions that do not require document comparison.
- Outputs: Clause matrix, severity-ranked recommendations, counter-language, and a written negotiation brief.
- Success criteria: Finds cross-document conflicts, produces actionable counterpositions, and writes the report artifact.
Trigger Examples
Positive
- Use the legal-contract-negotiation-review skill for this request.
- Help me with legal contract negotiation review.
- Use for contract markups, last-minute deal term demands, or clause-by-clause negotiation defense work.
- Legal Contract Negotiation Review: provide an actionable result.
Negative
- Do not use for pure legal research questions that do not require document comparison.
- Do not use legal-contract-negotiation-review for unrelated requests.
- This request is outside legal contract negotiation review scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description | |---|---|---|---| | agreement_path | string | No | Optional explicit path to the main agreement (DOCX/PDF/TXT) | | disclosure_schedules_path | string | No | Optional explicit path to disclosure schedules or side letter | | counterparty_changes_path | string | No | Optional explicit path to counterparty redline or demand letter | | client_side | select | No | Which side you represent | | output_report_path | string | No | Where to write the negotiation analysis markdown | | output_docx_path | string | No | Optional path for a clean revised DOCX draft |
Runtime Prompt
- Current runtime prompt length: 2482 characters.
- Runtime prompt is defined directly in `../legal-contract-negotiation-review.json`.
Local-first personal agentic OS and everything app for coding, knowledge work, web design, automations, and artifacts.
Repo: CoWork-OS/CoWork-OS
Other skills on cowork-os.
- /attack-path-analysis
Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a security finding from source to sink and calibrate severity. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /deep-security-scan
Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan. Run repeated independent repository-wide discovery passes with worker-specific threat models, semantically merge candidates, synthesize one canonical validation
Open skill - /finding-discovery
Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover candidate security findings in a repository or code change. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /fix-finding
Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
Open skill - /security-diff-scan
Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other Git-backed change set.
Open skill - /security-scan
Use when the user asks for a repository-wide or scoped-path security scan.
Open skill