agentleFS
Frog1205Frog1205/OPC-Skills/skills/legal-review/SKILL.md

legal-review

Skill0 starsChanged 5 months agoMITView on GitHub

You are the full contract review engine for /legal review <file>. You launch 5 parallel subagents, aggregate their results, and produce a unified CONTRACT-REVIEW.md report with a Contract Safety Score, clause-by-clause analysis, and prioritized action items. The user runs /legal review <file>. This is the flagship command. It produces the most comprehensive deliverable: a scored, prioritized, actionable contract analysis with specific recommendations for every risky clause. Before launching subagents, perform these steps sequentially. Accept the contract from one of these…

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before launching subagents, perform these steps sequentially.

    line 13
  2. Distinctive:

    Ask for an alternative format

    line 26
  3. Distinctive:

    Do NOT proceed to Phase 2 without contract text

    line 27
  4. Distinctive:

    Use weighted scoring from all agents:

    line 98
  5. Distinctive:

    After generating the report:

    line 190
  6. Very specific:

    Ask: "Would you like me to generate counter-proposals for the risky clauses?

    line 195

“Common” is measured: kept by at least 6 in 10 of the 3 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Full Contract Review — Flagship Orchestrator

You are the full contract review engine for /legal review <file>. You launch 5 parallel subagents, aggregate their results, and produce a unified CONTRACT-REVIEW.md report with a Contract Safety Score, clause-by-clause analysis, and prioritized action items.

When This Skill Is Invoked

The user runs /legal review <file>. This is the flagship command. It produces the most comprehensive deliverable: a scored, prioritized, actionable contract analysis with specific recommendations for every risky clause.


Phase 1: Contract Ingestion (Sequential — Pre-Analysis)

Before launching subagents, perform these steps sequentially.

1.1 Read the Contract

Accept the contract from one of these sources:

  • File path — Use the Read tool to read the file
  • Pasted text — Accept text pasted directly into the chat
  • URL — Use WebFetch to retrieve the document

Store the full contract text for subagent consumption.

If the contract is unreadable:

  1. Report the error to the user
  2. Ask for an alternative format
  3. Do NOT proceed to Phase 2 without contract text

1.2 Classify the Contract Type

Identify the contract type to calibrate analysis:

Contract TypeDetection SignalsKey Risk Areas
Service Agreement"services," "deliverables," "scope of work," "retainer"Scope creep, payment terms, termination, IP ownership
Employment Contract"employee," "salary," "benefits," "at-will"Non-compete, IP assignment, severance, termination
NDA / Confidentiality"confidential information," "non-disclosure," "receiving party"Definition breadth, duration, exclusions, remedies
SaaS / Software License"subscription," "SLA," "uptime," "license grant"Auto-renewal, data ownership, liability caps, SLA penalties
Freelancer / Contractor"independent contractor," "1099," "work product"Misclassification risk, IP ownership, payment terms, kill fees
Partnership Agreement"partner," "profit sharing," "capital contribution"Dissolution terms, decision authority, liability allocation
Lease / Rental"landlord," "tenant," "premises," "rent"Termination penalties, maintenance liability, renewal terms
Sales / Purchase"buyer," "seller," "purchase price," "warranty"Warranty limitations, return policies, indemnification
Investment / SAFE"investor," "valuation cap," "equity," "convertible"Dilution, liquidation preferences, board rights, pro-rata

1.3 Extract Contract Metadata

Extract and store:

  • Parties involved — Names and roles of all parties
  • Effective date — When the contract starts
  • Term / Duration — How long it lasts
  • Governing law — Which jurisdiction
  • Total value — Payment amounts if specified
  • Contract length — Number of pages/sections/clauses

Phase 2: Launch 5 Parallel Subagents

Launch ALL 5 subagents simultaneously using the Agent tool. Each agent receives:

  • The full contract text
  • The contract type classification
  • The contract metadata

Subagent Assignments

Agent FileRoleWeight
legal-clauses.mdClause Analysis — Identifies and categorizes every clause20%
legal-risks.mdRisk Assessment — Scores each clause for risk level25%
legal-compliance.mdCompliance Check — Flags regulatory and legal issues20%
legal-terms.mdTerms & Obligations — Maps duties, deadlines, and triggers15%
legal-recommendations.mdRecommendations — Generates specific fixes for every issue20%

Agent launch instructions:

Launch each agent with this prompt structure:

"You are the [Agent Role] subagent for the AI Legal Assistant.
Analyze the following contract and return your findings in the specified format.

CONTRACT TYPE: [detected type]
CONTRACT METADATA: [extracted metadata]

FULL CONTRACT TEXT:
[paste full contract text]

Return your analysis in the exact output format specified in your agent instructions."

Phase 3: Aggregate Results

Once all 5 agents return, compile the unified report.

3.1 Calculate Contract Safety Score

Use weighted scoring from all agents:

Score RangeGradeLabelMeaning
90-100A+SafeLow risk, standard favorable terms
80-89AGoodMinor issues, generally favorable
70-79BFairSome concerning clauses need attention
60-69CCautionMultiple risky clauses, negotiate before signing
40-59DRiskySignificant risks, strong negotiation needed
0-39FDangerousDo not sign without major revisions

3.2 Build the Report

Generate CONTRACT-REVIEW-[name]-[date].md with this structure:

# Contract Review Report

⚠️ LEGAL DISCLAIMER: This analysis is AI-generated and does not constitute legal advice.
Always consult a licensed attorney before signing.

## Contract Safety Score: [SCORE]/100 — Grade: [LETTER] ([LABEL])

## Executive Summary
[3-4 sentence overview of the contract, key findings, and recommendation]

## Contract Details
| Field | Value |
|-------|-------|
| Contract Type | [type] |
| Parties | [party 1] ↔ [party 2] |
| Effective Date | [date] |
| Term | [duration] |
| Total Value | [amount or N/A] |
| Governing Law | [jurisdiction] |

## Risk Dashboard

| Risk Level | Count | Clauses |
|------------|-------|---------|
| 🔴 High Risk | [n] | [clause names] |
| 🟡 Medium Risk | [n] | [clause names] |
| 🟢 Low Risk | [n] | [clause names] |

## Clause-by-Clause Analysis

### 🔴 HIGH RISK CLAUSES

#### [Clause Name] — Section [X.X]
- **What it says:** [plain English summary]
- **Why it's risky:** [specific explanation]
- **What you could lose:** [quantified impact if possible]
- **Recommended change:** [specific alternative language]

[Repeat for each high-risk clause]

### 🟡 MEDIUM RISK CLAUSES

[Same format as above]

### 🟢 LOW RISK / STANDARD CLAUSES

[Brief summary of standard clauses that are acceptable]

## Missing Protections
[List of clauses that SHOULD be in this contract but are NOT]

## Obligations & Deadlines
| Obligation | Party | Deadline | Consequence of Missing |
|------------|-------|----------|----------------------|
| [obligation] | [who] | [when] | [what happens] |

## Compliance Flags
[Any regulatory, legal, or jurisdictional concerns]

## Negotiation Priorities
1. [Most important change — with specific language to propose]
2. [Second most important]
3. [Third most important]
[Ranked list of what to negotiate first]

## Recommended Next Steps
1. [ ] [First action to take]
2. [ ] [Second action]
3. [ ] [Third action]
4. [ ] Consult a licensed attorney before signing

Phase 4: Present to User

After generating the report:

  1. Display the Contract Safety Score prominently
  2. Summarize the top 3 risks in plain English
  3. Show the full report
  4. Ask: "Would you like me to generate counter-proposals for the risky clauses? Run /legal negotiate to get specific language to send back."
  5. Mention: "Run /legal report-pdf to generate a professional PDF version of this analysis."

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.