review-contract
Skill1 starsChanged 7 months agoMITView on GitHub
Review a contract against the organization's negotiation playbook -- flag deviations, generate redlines, and provide business impact analysis. Use when reviewing vendor or customer agreements, or when generating redline recommendations. Trigger with "review this contract", "contract review", "redline this agreement", or "check against playbook".
6 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/cat-agent-skillstheir own version, first seen Nov 8, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- cardano-foundation/cardano-dev-skillstheir own version, first seen Sep 27, 2026
- alebgl77/claude-inctheir own version, first seen Jul 28, 2026
- thestratcore/My-skillstheir own version, first seen Jul 10, 2026
- getnao/sylphtheir own version, first seen May 19, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- anthropics/knowledge-work-plugins★ 36ksame name
- getnao/sylph★ 195same name
- microsoft/cat-agent-skills★ 108same name
- cardano-foundation/cardano-dev-skills★ 38same name
- alebgl77/claude-inc★ 21same name
- thestratcore/My-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 43
Verify presence of: DPA (if personal data involved), insurance requirements, compliance representation, force majeure, assignment …
- Distinctive: line 78
Action: Check for embedded non-compete or non-solicitation clauses, overly broad confidential information definition, residuals clause, and …
- Distinctive: line 86
Check cross-references between sections to catch internal inconsistencies.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Contract Review
Review contracts clause-by-clause against the negotiation playbook. Flag deviations, classify risk, generate redline language, and assess business impact.
Workflow
Step 1: Identify Contract Type and Playbook
Select the applicable playbook: MSA/SaaS (SLAs, liability, IP), NDA (scope, term, exclusions), SOW (scope, fees, acceptance), DPA (roles, sub-processors, breach notification), License (grant scope, restrictions, audit), Employment (non-compete, IP assignment, severance).
Step 2: Analyze Key Clauses
For each material clause evaluate: current language, playbook position, deviation direction (favorable/neutral/unfavorable), risk level (LOW/MEDIUM/HIGH/CRITICAL), and business impact.
Step 3: Generate Redlines
For each MEDIUM+ deviation: draft preferred alternative language, provide a fallback position, and note the business justification for the change.
Step 4: Check for Missing Provisions
Verify presence of: DPA (if personal data involved), insurance requirements, compliance representation, force majeure, assignment restrictions, audit rights, governing law.
Output Format
## Contract Review Report
**Contract**: [Type] | **Counterparty**: [Name] | **Date**: [YYYY-MM-DD]
**Overall Risk**: [LOW / MEDIUM / HIGH / CRITICAL]
**Recommendation**: [Approve / Approve with Redlines / Reject / Escalate]
### Clause Analysis
| # | Clause | Section | Playbook | Contract | Risk |
|---|--------|---------|----------|----------|------|
| 1 | Liability cap | 8.1 | 12mo fees | Unlimited | CRITICAL |
### Finding 1: [Clause] -- [RISK LEVEL]
- Contract says: [Exact language]
- Playbook requires: [Standard position]
- Business impact: [Why it matters]
- Recommended redline: [Alternative language]
- Fallback: [Secondary position]
### Missing Provisions
- [ ] [Missing clause] -- Risk: [Level]
### Summary
[Total deviations: X | Critical: X | High: X | Medium: X | Low: X]Examples
User: "Review this SaaS vendor agreement" Action: Compare all clauses against the vendor playbook, flag unlimited liability, missing SLA credits, broad IP license, and weak data processing terms. Generate specific redlines for each.
User: "Quick review of this NDA -- anything unusual?" Action: Check for embedded non-compete or non-solicitation clauses, overly broad confidential information definition, residuals clause, and excessive term.
Best Practices
- Review the entire contract, not just sections that seem important. Risk hides in boilerplate.
- Quote exact contract language when flagging deviations.
- Provide both preferred redline and fallback to give negotiators flexibility.
- Assess business impact in practical terms, not just legal terms.
- Check cross-references between sections to catch internal inconsistencies.
- Note governing law and dispute resolution early -- they affect enforceability of every provision.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

