review-contract

Name: review-contract
Author: getnao

168stars52forks

How to install review-contract?

getnao/sylph/review-contract

$npx -y skills add getnao/sylph --skill review-contract

Installs into the current project.

Summary

Review a contract against standard negotiation positions - flag deviations, generate redlines, provide business impact analysis. Use when reviewing vendor or customer agreements, when you need clause-by-clause analysis, or when preparing a negotiation strategy.

Files · 1

View on GitHub

SKILL.md

1	# /review-contract - Contract Review
2
3	## MCP connectors
4
5	None required. This skill operates on local repo files only.
6
7	Review a contract against standard positions. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.
8
9	Important: This assists with legal workflows but does not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
10
11	## Invocation
12
13	```
14	/review-contract <contract file or URL>
15	```
16
17	## Workflow
18
19	### Step 1: Accept the Contract
20
21	Accept in any format: PDF, DOCX, pasted text, or file path.
22	If no contract is provided, prompt the user.
23
24	### Step 2: Gather Context
25
26	Ask:
27	1. Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner)
28	2. Deadline: When does this need to be finalized?
29	3. Focus areas: Any specific concerns?
30	4. Deal context: Deal size, strategic importance, existing relationship?
31
32	Proceed with partial context if needed, noting assumptions.
33
34	### Step 3: Load Standard Positions
35
36	Load standard contract positions from `legal/templates/enterprise-service-agreement.md`.
37
38	If no template exists, proceed with generic review using widely-accepted SaaS commercial standards as baseline. Note clearly.
39
40	### Step 4: Clause-by-Clause Analysis
41
42	1. Identify the contract type (SaaS, services, license, partnership, procurement)
43	2. Determine the user's side
44	3. Read the entire contract before flagging issues - clauses interact
45	4. Analyze each material clause against standard positions
46	5. Consider the contract holistically
47
48	Cover at minimum:
49
50	\| Clause Category \| Key Review Points \|
51	\|----------------\|-------------------\|
52	\| Limitation of Liability \| Cap amount, carveouts, mutual vs. unilateral, consequential damages \|
53	\| Indemnification \| Scope, mutual vs. unilateral, cap, IP infringement, data breach \|
54	\| IP Ownership \| Pre-existing IP, developed IP, open source, license grants \|
55	\| Data Protection \| DPA, processing terms, self-hosted vs. cloud, sub-processors, breach notification \|
56	\| Confidentiality \| Scope, term, carveouts, return/destruction \|
57	\| Warranties \| Scope, disclaimers, survival period \|
58	\| Term & Termination \| Duration, renewal, termination for convenience/cause, wind-down \|
59	\| Governing Law \| Jurisdiction, venue, arbitration vs. litigation \|
60	\| Payment Terms \| Net terms, late fees, taxes, price escalation \|
61	\| SLA & Support \| Uptime, response times, support channels \|
62
63	### Step 5: Flag Deviations
64
65	#### GREEN - Acceptable
66	Aligns with or better than standard position. No action needed.
67
68	#### YELLOW - Negotiate
69	Outside standard position but within negotiable range. Generate redlines.
70
71	#### RED - Escalate
72	Outside acceptable range, poses material risk. Requires escalation.
73
74	### Step 6: Generate Redlines
75
76	For each YELLOW and RED deviation:
77
78	```
79	Clause: [Section reference]
80	Current language: "[quote]"
81	Proposed redline: "[alternative language]"
82	Rationale: [1-2 sentences, suitable for external sharing]
83	Priority: [Must-have / Should-have / Nice-to-have]
84	Fallback: [Alternative position if rejected]
85	```
86
87	### Step 7: Business Impact Summary
88
89	- Overall risk assessment: High-level view
90	- Top 3 issues: Most important items to address
91	- Negotiation strategy: Which issues to lead with, what to concede
92	- Timeline considerations: Urgency factors
93
94	## Notes
95
96	- For non-English contracts, ask if the user wants translation or review in the original language
97	- For long contracts (50+ pages), focus on material sections first
98	- Always remind that analysis should be reviewed by qualified legal counsel
99
100	## Self-improvement
101
102	After the CAO (or legal counsel) reviews the contract analysis:
103
104	1. If they override a risk assessment (e.g. marked something RED that should have been YELLOW, or vice versa), update the risk calibration in this skill
105	2. If they flag a clause type or risk pattern not covered in the Clause-by-Clause table, add it
106	3. Update `legal/_insights.md` with the correction and the reasoning
107	4. If new standard positions emerge from negotiations (e.g. "we now accept mutual liability caps at 2x annual fees"), update `legal/templates/enterprise-service-agreement.md`
108	5. If a review format or negotiation strategy worked well, save it to `legal/_examples/` as a reference

People who liked this also viewed

6 picks

Type

review-contract

168stars52forks

View on GitHub

How to install review-contract?

getnao/sylph/review-contract

$npx -y skills add getnao/sylph --skill review-contract

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# /review-contract - Contract Review
2
3	## MCP connectors
4
5	None required. This skill operates on local repo files only.
6
7	Review a contract against standard positions. Analyze each clause, flag deviations, generate redline suggestions, and provide business impact analysis.
8
9	Important: This assists with legal workflows but does not provide legal advice. All analysis should be reviewed by qualified legal professionals before being relied upon.
10
11	## Invocation
12
13	```
14	/review-contract <contract file or URL>
15	```
16
17	## Workflow
18
19	### Step 1: Accept the Contract
20
21	Accept in any format: PDF, DOCX, pasted text, or file path.
22	If no contract is provided, prompt the user.
23
24	### Step 2: Gather Context
25
26	Ask:
27	1. Which side are you on? (vendor/supplier, customer/buyer, licensor, licensee, partner)
28	2. Deadline: When does this need to be finalized?
29	3. Focus areas: Any specific concerns?
30	4. Deal context: Deal size, strategic importance, existing relationship?
31
32	Proceed with partial context if needed, noting assumptions.
33
34	### Step 3: Load Standard Positions
35
36	Load standard contract positions from `legal/templates/enterprise-service-agreement.md`.
37
38	If no template exists, proceed with generic review using widely-accepted SaaS commercial standards as baseline. Note clearly.
39
40	### Step 4: Clause-by-Clause Analysis
41
42	1. Identify the contract type (SaaS, services, license, partnership, procurement)
43	2. Determine the user's side
44	3. Read the entire contract before flagging issues - clauses interact
45	4. Analyze each material clause against standard positions
46	5. Consider the contract holistically
47
48	Cover at minimum:
49
50	\| Clause Category \| Key Review Points \|
51	\|----------------\|-------------------\|
52	\| Limitation of Liability \| Cap amount, carveouts, mutual vs. unilateral, consequential damages \|
53	\| Indemnification \| Scope, mutual vs. unilateral, cap, IP infringement, data breach \|
54	\| IP Ownership \| Pre-existing IP, developed IP, open source, license grants \|
55	\| Data Protection \| DPA, processing terms, self-hosted vs. cloud, sub-processors, breach notification \|
56	\| Confidentiality \| Scope, term, carveouts, return/destruction \|
57	\| Warranties \| Scope, disclaimers, survival period \|
58	\| Term & Termination \| Duration, renewal, termination for convenience/cause, wind-down \|
59	\| Governing Law \| Jurisdiction, venue, arbitration vs. litigation \|
60	\| Payment Terms \| Net terms, late fees, taxes, price escalation \|
61	\| SLA & Support \| Uptime, response times, support channels \|
62
63	### Step 5: Flag Deviations
64
65	#### GREEN - Acceptable
66	Aligns with or better than standard position. No action needed.
67
68	#### YELLOW - Negotiate
69	Outside standard position but within negotiable range. Generate redlines.
70
71	#### RED - Escalate
72	Outside acceptable range, poses material risk. Requires escalation.
73
74	### Step 6: Generate Redlines
75
76	For each YELLOW and RED deviation:
77
78	```
79	Clause: [Section reference]
80	Current language: "[quote]"
81	Proposed redline: "[alternative language]"
82	Rationale: [1-2 sentences, suitable for external sharing]
83	Priority: [Must-have / Should-have / Nice-to-have]
84	Fallback: [Alternative position if rejected]
85	```
86
87	### Step 7: Business Impact Summary
88
89	- Overall risk assessment: High-level view
90	- Top 3 issues: Most important items to address
91	- Negotiation strategy: Which issues to lead with, what to concede
92	- Timeline considerations: Urgency factors
93
94	## Notes
95
96	- For non-English contracts, ask if the user wants translation or review in the original language
97	- For long contracts (50+ pages), focus on material sections first
98	- Always remind that analysis should be reviewed by qualified legal counsel
99
100	## Self-improvement
101
102	After the CAO (or legal counsel) reviews the contract analysis:
103
104	1. If they override a risk assessment (e.g. marked something RED that should have been YELLOW, or vice versa), update the risk calibration in this skill
105	2. If they flag a clause type or risk pattern not covered in the Clause-by-Clause table, add it
106	3. Update `legal/_insights.md` with the correction and the reasoning
107	4. If new standard positions emerge from negotiations (e.g. "we now accept mutual liability caps at 2x annual fees"), update `legal/templates/enterprise-service-agreement.md`
108	5. If a review format or negotiation strategy worked well, save it to `legal/_examples/` as a reference

People who liked this also viewed

6 picks

Type