Legal Review Skills for Small Firms
⭐ Star this repo if it's useful — and check out amagilabs/amagi-watch, our CLI that gives Claude video transcripts and key frames from any URL. More at amagilabs.ai.
A Claude Code skills and subagents pack for first-pass review of NDAs, MSAs, SaaS agreements, contractor agreements, and commercial or residential leases. Built for small firms and solo attorneys who want an AI-assisted first read before they put their own eyes, and their license, on a document.
This is not legal advice.
Every finding, redline, risk score, and memo this pack produces is AI-generated drafting assistance. None of it is legal advice, none of it is a substitute for an attorney, and nothing it writes should be sent to a client or a counterparty until a licensed attorney in the governing jurisdiction has reviewed it. Treat all output as a first draft from a very fast, very literal junior associate who has never passed the bar.
What's in the pack
Skills (skills/): reference material Claude Code loads on demand.
| Skill | What it covers |
|---|---|
contract-review-playbook |
Market positions, red flags, and fallback language for NDAs, MSAs/SaaS agreements, and contractor/vendor agreements. |
lease-review-playbook |
Same approach for commercial and residential leases. |
legal-citation-check |
The verify-or-flag rule for every statute, regulation, or case citation, plus clause-reference resolution. |
redline-format |
Output conventions for tracked-change-style redlines, including the two-variant (opening ask / fallback) pattern. |
Agents (agents/): a nine-agent review pipeline, orchestrated by
legal-review-lead.
legal-clause-extractorturns a document into a structured clause map.legal-playbook-checkerflags issues against the relevant playbook.legal-jurisdiction-researcherverifies citations and adds jurisdiction-specific findings.legal-risk-scorerrolls findings into a ranked, dollar-weighted risk matrix.legal-redline-drafterdrafts replacement language for material findings.legal-negotiation-strategistbuilds a concession ladder for each redline.legal-client-memo-writerwrites a one-page, plain-English summary for the client.legal-adversarial-reviewerruns an independent second pass that hunts for hallucinated findings or quotes.legal-review-leadruns the above in sequence and assembles the attorney sign-off package.
Every agent in the pipeline treats its output as a draft for the next agent, or the attorney, to check. Nothing is final until a human with a bar card says so.
Install
Claude Code loads skills from ~/.claude/skills/ and agents from
~/.claude/agents/. To install this pack:
# from inside this repo
cp -r skills/* ~/.claude/skills/
cp agents/*.md ~/.claude/agents/
On Windows (PowerShell):
Copy-Item -Recurse skills\* "$env:USERPROFILE\.claude\skills\"
Copy-Item agents\*.md "$env:USERPROFILE\.claude\agents\"
Restart Claude Code (or start a new session) so it picks up the new
skills and agents. You can confirm the agents are registered by asking
Claude Code to list available agent types, or by typing a request like
"review this lease" and checking that it routes to legal-review-lead.
Worked example
examples/sample_nda.txt is a short, fictional mutual NDA between two
invented companies, with no real parties and no real deal terms.
examples/example_run.md walks through what the contract-review-playbook
skill flags in that NDA: an uncapped, one-directional indemnity clause
dressed up inside a nominally mutual agreement, a missing trade-secret
notice, and a couple of minor drafting notes. It also shows one example
redline in the pack's two-variant format.
Run it yourself: point legal-review-lead at examples/sample_nda.txt
and ask it to review the NDA. Expect a clause map, a findings list, a
risk matrix, draft redlines, a negotiation plan, a client memo, and an
adversarial pass, each gated on the sign-off checklist at the end of
legal-review-lead's pipeline.
Why this exists
Reviewing a routine NDA or commercial lease by hand is slow and the issues repeat across documents: the same handful of red flags, the same missing clauses, the same negotiation moves. This pack encodes that repetition into a checklist-driven pipeline so an attorney's first pass starts from a marked-up draft instead of a blank page, while keeping every legal judgment call, every citation, and every send decision in the attorney's hands.
License
MIT. See LICENSE. Copyright (c) 2026 AmagiLabs.
Contributing
This pack ships as a starting point, not a finished product. Playbook
coverage is currently strongest for NDAs, MSA/SaaS agreements, and
Georgia-first commercial and residential leases; other document types and
jurisdictions will need their own playbook files (see the "Playbooks"
table inside each skill's SKILL.md) before the pipeline covers them
well. Pull requests that add playbook coverage, tighten the citation
allowlist, or improve the adversarial-review checks are welcome.
Metadata
Release files for amagi-legal-review-skills 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| amagi_legal_review_skills-0.1.0.tar.gz | 28.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| amagi_legal_review_skills-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 64.2 kB
Release files / amagi_legal_review_skills-0.1.0.tar.gz
| Download URL | amagi_legal_review_skills-0.1.0.tar.gz |
|---|---|
| Size | 28.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8fd738a2ea25339227a0ba8966f98b9e9e8d714c4effb84c9d1521346bc77679
|
|
BLAKE2b-256 checksum How to use checksums |
358d0dfa0aa548faa12f23501c26dc25f3d7b7964573f92c9681965ec90c5eff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logRelease files / amagi_legal_review_skills-0.1.0-py3-none-any.whl
| Download URL | amagi_legal_review_skills-0.1.0-py3-none-any.whl |
|---|---|
| Size | 35.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
792a0fddd5c54196876dd9682816882d0d77867dfa23add2660665941d382492
|
|
BLAKE2b-256 checksum How to use checksums |
6e424a389dad69373865980df1846a0e2d552917570fe03f6cb2ee32f93fec66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logSecurity for amagi-legal-review-skills 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for amagi_legal_review_skills-0.1.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 22, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.