review-alexchlou

name	review-alexchlou
title	$commercial-legal:review
description	Review a vendor agreement, NDA, or SaaS subscription against your playbook. Identifies the agreement structure from titles, routes to the right review skill (vendor-agreement-review, nda-review, saas-msa-review), and integrates the output into a single memo. Use when the user says "review this contract", "check this MSA", "is this NDA okay", "look at this SaaS agreement", or attaches an inbound agreement for review.
author	alexchlou
author_url	https://github.com/alexchlou/codex-for-legal/tree/main/plugins/commercial-legal/skills/review
license	Apache-2.0
version	0.1.0
execution_mode	open
jurisdiction	general
practice	contracts
language	en

Codex v1 local-input note: This migrated skill supports local files and pasted text by default. References to Drive, CLM IDs, Slack, Westlaw, iManage, Ironclad, eDiscovery, dockets, or other remote systems require a separately configured Codex connector/MCP server. When a connector is unavailable, ask for a local export, local file path, or pasted excerpts. If config/local/codex-for-legal/<practice>/CLAUDE.md is missing, ask the user to run the relevant cold-start-interview or customize skill and copy from config/templates/codex-for-legal/<practice>/CLAUDE.md.

$commercial-legal:review

Reviews an inbound agreement against the playbook in config/local/codex-for-legal/commercial-legal/CLAUDE.md. Identifies the agreement structure from titles, selects the appropriate skill(s), and — if confirm_routing is enabled — checks with the user before proceeding.

Instructions

1. Load config/local/codex-for-legal/commercial-legal/CLAUDE.md. If the file is missing or placeholders are present, stop and prompt: "Run $commercial-legal:cold-start-interview first — I need to learn your playbook before I can review against it."

   Also read config/local/codex-for-legal/commercial-legal/CLAUDE.md → ## Review preferences → confirm_routing. If the field is missing, treat it as true.

2. Get the agreement: From file path, local file path or pasted text (Drive requires a separately configured connector), local CLM export or pasted text (CLM connector required for IDs), or pasted text. If none provided, ask.

3. Read the document structure — titles first.

   Before reading the body, extract:

   • The main agreement title (e.g., "Master Services Agreement", "Non-Disclosure Agreement")
   • All exhibit, schedule, addendum, and attachment titles (e.g., "Exhibit A — Data Processing Addendum", "Schedule 1 — Subscription Order Form", "Annex B — Service Level Agreement")

   This is the routing signal. Do not rely on body keywords alone — a 40-page MSA with "confidential" throughout is not an NDA.

4. Select the skill(s) based on document structure.

   Map each identified document or section to a skill:

   Document / section title contains	Skill
   Non-Disclosure, NDA, Confidentiality Agreement (as the agreement)