review contract

Engineering Community

Skill notes

Invocation

Review the contract: @$1

Step 1: Accept the Contract

Accept the contract in any of these formats: File upload: PDF, DOCX, or other document format URL: Link to a contract in your CLM, cloud storage (e.g., Box, Egnyte, SharePoint), or other document system Pasted text: Contract text pasted directly into the conversation If no contract is provided, prompt the user to supply one.

Step 2: Gather Context

Ask the user for context before beginning the review: Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner -- or other) Deadline: When does this need to be finalized? (Affects prioritization of issues) Focus areas: Any specific concerns? (e.g., "data protection is critical", "we need flexibility on term", "IP ownership is the key issue") Deal context: Any relevant business context? (e.g., deal size, strategic importance, existing relationship)

Step 3: Load the Playbook

Look for the organization's contract review playbook in local settings (e.g., legal.local.md or similar configuration files). The playbook should define: Standard positions: The organization's preferred terms for each major clause type Acceptable ranges: Terms that can be agreed to without escalation Escalation triggers: Terms that require senior counsel review or outside counsel involvement

Step 4: Clause-by-Clause Analysis

Apply the following review process: Identify the contract type: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material. Determine the user's side: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties). Read the entire contract before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability).

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@anthropics · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Accept the Contract

Accept the contract in any of these formats: File upload: PDF, DOCX, or other document format URL: Link to a contract in your CLM, cloud storage (e.g., Box, Egnyte, SharePoint), or other document system Pasted text: Contract text pasted directly into the conversation If no contract is provided, prompt the user to supply one.

02
Step 2: Gather Context

Ask the user for context before beginning the review: Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner -- or other) Deadline: When does this need to be finalized? (Affects prioritization of issues) Focus areas: Any specific concerns? (e.g., "data protection is critical", "we need flexibility on term", "IP ownership is the key issue") Deal context: Any relevant business context? (e.g., deal size, strategic importance, existing relationship)

03
Step 3: Load the Playbook

Look for the organization's contract review playbook in local settings (e.g., `legal.local.md` or similar configuration files). The playbook should define: Standard positions: The organization's preferred terms for each major clause type Acceptable ranges: Terms that can be agreed to without escalation Escalation triggers: Terms that require senior counsel review or outside counsel involvement

04
Step 4: Clause-by-Clause Analysis

Apply the following review process: Identify the contract type: SaaS agreement, professional services, license, partnership, procurement, etc. The contract type affects which clauses are most material. Determine the user's side: Vendor, customer, licensor, licensee, partner. This fundamentally changes the analysis (e.g., limitation of liability protections favor different parties). Read the entire contract before flagging issues. Clauses interact with each other (e.g., an uncapped indemnity may be partially mitigated by a broad limitation of liability).

05
Step 5: Flag Deviations

Classify each deviation from the playbook using a three-tier system: GREEN -- Acceptable The clause aligns with or is better than the organization's standard position. Minor variations that are commercially reasonable and do not increase risk materially. Examples: Liability cap at 18 months of fees when standard is 12 months (better for the customer)

06
Step 6: Generate Redline Suggestions

For each YELLOW and RED deviation, provide: Current language: Quote the relevant contract text Suggested redline: Specific alternative language Rationale: Brief explanation suitable for sharing with the counterparty Priority: Whether this is a must-have or nice-to-have in negotiation

07
Step 7: Business Impact Summary

Provide a summary section covering: Overall risk assessment: High-level view of the contract's risk profile Top 3 issues: The most important items to address Negotiation strategy: Recommended approach (which issues to lead with, what to concede) Timeline considerations: Any urgency factors affecting the negotiation approach

08
Step 8: CLM Routing (If Connected)

If a Contract Lifecycle Management system is connected via MCP: Recommend the appropriate approval workflow based on contract type and risk level Suggest the correct routing path (e.g., standard approval, senior counsel, outside counsel) Note any required approvals based on contract value or risk flags If no CLM is connected, skip this step.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.