legal-review

Review contracts and NDAs against a playbook, classifying clauses as GREEN, YELLOW, or RED.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/kmjy98-sketch/khulaw --skill legal-review-kmjy98-sketch
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: legal-review
Source: https://github.com/kmjy98-sketch/khulaw/tree/main/.agent/skills/legal-review
Command: npx skills add https://github.com/kmjy98-sketch/khulaw --skill legal-review-kmjy98-sketch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, and includes scripts (resource) components.

What problem does it solve? Reviewing contracts and NDAs clause-by-clause against internal legal positions is slow and inconsistent. This Skill automates the first pass: it reads PDF, DOCX, TXT, or MD documents, matches clauses against a local legal playbook, and produces a structured review report with status flags, redline suggestions, fallback positions, and business impact notes. ## Core Features & Use Cases - Playbook-Based Clause Triage: Classifies each clause as GREEN, YELLOW, or RED using keyword matching, favorable signals, and escalation triggers defined in a local legal_playbook.md file. - Structured Review Reports: Generates Markdown reports with key findings, suggested redlines, fallback positions, business impact, and next steps for both contract-review and nda-triage modes. - Full Legal Suite Pipeline: A dry-run runner chains review, compliance checklists, briefing memos, response drafts, Socratic study packets, and Korean law evidence lookups via korean-law-mcp. - Use Case: A legal ops user receives a vendor SaaS agreement as a PDF, runs the contract-review mode, and gets a report flagging unlimited liability and cross-border data transfer clauses as RED with concrete redline language. ## Quick Start Ask the assistant to review a contract file with the legal-review skill, for example: run render_review.py on my vendor agreement PDF in contract-review mode and summarize the RED clauses.

Frequently Asked Questions about legal-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a contract against a legal playbook automatically?▼

Run render_review.py with the contract file path and --mode contract-review. The script parses PDF, DOCX, TXT, or MD input, matches clauses against playbook keywords and escalation triggers, and outputs a Markdown report with GREEN/YELLOW/RED statuses and redline suggestions.

How do I triage an NDA for one-way confidentiality risks?▼

Use the nda-triage mode, which filters the playbook to confidentiality, governing law, and dispute resolution clauses. It flags one-way confidentiality language as a RED escalation trigger and suggests converting obligations to mutual form.

What document formats does the legal review script support?▼

The script supports PDF, DOCX, TXT, and MD files. PDFs are parsed with pypdf, DOCX files are read by extracting word/document.xml from the zip archive, and plain text files are read directly. Inline text can also be passed via the --text flag.

Can the review work without a custom legal playbook file?▼

Yes. If the playbook path does not exist, the script falls back to a built-in default playbook covering Limitation of Liability, Data Protection, and NDA Mutuality with standard positions, fallbacks, and escalation triggers.

What are the limitations of this contract review approach?▼

It is a keyword and trigger-based local reviewer, not a full legal analysis engine. Redline output is suggestion-level text, not DOCX track-changes editing, and it does not verify regulatory currency or connect to external CLM systems.

Why is the Korean law evidence step skipped in the pipeline?▼

The build_law_evidence.py step is skipped when the LAW_API_KEY environment variable is unset or still the placeholder value. It writes a skipped-status JSON artifact instead, and the pipeline continues since this step is optional.