Contract Review
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log…
Install Nda Review Jamie Tso
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tso --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .claude/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .claude/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tsoType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tso --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .agents/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .agents/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tso --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .cursor/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .cursor/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/lawve-ai/awesome-legal-skills.git --path skills/nda-reviewer-jamie-tso--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tso --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .gemini/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .gemini/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tsoInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .github/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .github/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install lawve-ai/awesome-legal-skills nda-review-jamie-tso --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/lawve-ai/awesome-legal-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/nda-reviewer-jamie-tso .opencode/skills/nda-review-jamie-tso && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nda-review-jamie-tso" agent skill from https://github.com/lawve-ai/awesome-legal-skills/tree/main/skills/nda-reviewer-jamie-tso into .opencode/skills/nda-review-jamie-tso/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-review-jamie-tso", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nda-review-jamie-tso- GitHub stars
- 847
- Token cost
- ~3k tokens
- SKILL.md length
- 1,349 words
- Files
- 8 (incl. references)
- Skills in repo
- 154
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log…
- Works in 5 steps: Identify stance (Recipient vs Discloser) → Triage the NDA (fast risk scan) → Clause-by-clause review (use the… → …
- Tasks that involve Contract review
- SKILL.md covers Overview, LEGAL DISCLAIMER, Inputs to collect (ask before… and Deliverables (output format), plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Nda Review Jamie Tso is an agent skill from lawve-ai/awesome-legal-skills. Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log with preferred redlines, fallbacks, rationales, owners, and deadlines.
Its SKILL.md is about 3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 8 other files, including reference files (for example `README.md`, `references/DURATION_SCOPE.md` and `references/KEY_CLAUSES.md`).
It sits in Legal & Compliance, covering Contract review. The repository describes itself as: A curated list of awesome Agent Skills for automating legal work. The licence is AGPL-3.0.
When your agent uses it
- Tasks that involve Contract review
Example prompts
- “/nda-review-jamie-tso”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 045f738. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Nda Review Jamie Tso loads about 3k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 73 tokens; SKILL.md has 1,349 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from lawve-ai/awesome-legal-skills at commit 045f738, republished under its AGPL-3.0 licence (© lawve-ai). 1,349 words, ~2,972 tokens.
Download SKILL.mdSave it as
.claude/skills/nda-review-jamie-tso/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- nda-review-jamie-tso
- description
- Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log with preferred redlines, fallbacks, rationales, owners, and deadlines.
- metadata.author
- Jamie Tso
- metadata.license
- AGPL-3.0
- metadata.version
- 2025.12.30
NDA Review Playbook (Commercial, Jurisdiction-Agnostic)
Overview
| What this skill does | What it does not do |
|---|---|
| Reviews an NDA and outputs issues, risks, and suggested redlines | Provide jurisdiction-specific legal conclusions |
| Supports Recipient or Discloser perspectives (user-chosen) | Guarantee enforceability |
| Produces an executive summary + clause-by-clause markup guidance | Replace counsel for complex deals |
Scope limitation (important): this playbook supports one-way (unilateral) commercial NDAs only.
If the NDA is mutual, stop: this playbook is out of scope and you should escalate to counsel or use a separate mutual-NDA review approach.
Variation callouts appear throughout:
- M&A / Due diligence
- Employment / contractor
- Investor / VC
LEGAL DISCLAIMER
THIS IS NOT LEGAL ADVICE. This skill is provided for informational and educational purposes only. Laws vary by jurisdiction and individual circumstances, and only a licensed attorney can provide advice tailored to your specific situation. When the NDA is high-risk, high-value, cross-border, or otherwise sensitive, escalate to qualified counsel.
Remember: All outputs from this skill must be reviewed by a qualified legal professional before being used for any legal purposes.
Inputs to collect (ask before reviewing)
A. Role and deal context (required)
- Are we reviewing as Recipient (we receive confidential info) or Discloser (we disclose confidential info)?
- Confirm the NDA is one-way (unilateral). If it is mutual, stop: this playbook cannot be used.
- What is the purpose / permitted use (e.g., evaluation of partnership, vendor RFP, diligence)?
- What are the parties (legal names) and any affiliates that should be covered?
- What information types are expected (tech, pricing, customer data, product roadmap, source code)?
- Desired timeline: when do we need to sign?
B. Practical constraints (recommended)
- Do we need to share with affiliates, advisors, contractors, auditors, or potential acquirers?
- Will we need to export data across borders or store in cloud tools?
- Will any personal data be shared? If yes, are there separate data-processing terms?
Jurisdiction-agnostic note: avoid asserting “this clause is invalid” without the governing law details; focus on commercial risk, operational feasibility, and market norms.
Deliverables (output format)
Quick start (default output template)
ALWAYS output:
- Executive summary
- Clause-by-clause issue log (single table)
A. Executive summary (1 page)
- Party role (Recipient or Discloser) and confirmation it is one-way (unilateral)
- Top 5 negotiation points (ranked)
- “Sign as-is” / “Sign with changes” / “Escalate” recommendation
B. Clause-by-clause issue log (lawyer-style, thorough)
Use a single table so counsel and business owners can track issues, owners, and deadlines.
| Clause | Issue (1 line) | Risk (H/M/L) | Preferred redline | Fallback | Rationale (1–2 sentences) | Owner | Deadline |
|---|---|---|---|---|---|---|---|
| Definition | Overbroad; includes unmarked info with no reasonableness | ||||||
| Term & survival | Perpetual confidentiality for all information | ||||||
| Use restriction | Purpose too broad; blocks internal evaluation | ||||||
| Disclosures | Representatives undefined; strict liability | ||||||
| Return/destruction | No backup carve-out | ||||||
| Remedies | One-way fees + automatic injunction | ||||||
| Liability | Indemnity + unlimited consequential damages | ||||||
| Boilerplate | Assignment prohibits change of control |
Example (compact)
Executive summary (example skeleton):
- Role: Recipient (one-way NDA)
- Recommendation: Sign with changes
- Top 5 points: definition scope; term/survival; representatives; backup carve-out; remedies/fees
Issue log (example rows):
| Clause | Issue (1 line) | Risk (H/M/L) | Preferred redline | Fallback | Rationale (1–2 sentences) | Owner | Deadline |
|---|---|---|---|---|---|---|---|
| Term & survival | Perpetual confidentiality for all information | H | Add 2–5 year survival; trade secret carve-out only | 5-year survival for all | Reduces indefinite operational burden while protecting truly sensitive info | Legal | Before signature |
| Return/destruction | No backup carve-out | M | Add backup/legal hold exception + continued confidentiality | Allow retention in immutable backups only | Required for standard IT operations; avoids impossible compliance | Security + Legal | Before signature |
5-step workflow
Step 1 — Identify stance (Recipient vs Discloser)
- Confirm which side we are on for this specific NDA (titles are often misleading).
- Confirm the NDA is one-way (unilateral). If it is mutual, stop (out of scope).
Quick heuristic:
- If we are being asked to keep their info secret → we are Recipient.
- If we are sharing our sensitive info → we are Discloser (if the NDA is mutual, stop: out of scope).
Step 2 — Triage the NDA (fast risk scan)
Flag these immediately:
- Perpetual confidentiality for all information (no trade secret distinction)
- Residuals clause allowing use of “memory” or generalized knowledge
- Injunctive relief + attorneys’ fees one-way against Recipient
- Indemnity for breach or broad third-party claims
- No carve-outs for compelled disclosure or prior knowledge
- Overbroad definition: “all information, whether marked or not” with no reasonableness
- Affiliate coverage missing when we must share internally
If any are present and the NDA matters, proceed with full review and consider escalation.
Step 3 — Clause-by-clause review (use the reference modules)
Use these references while reviewing:
Step 4 — Draft redlines and negotiation positions
For each issue, produce:
- Preferred redline (best risk outcome)
- Fallback position (acceptable compromise)
- Rationale (1–2 sentences: business + operational feasibility)
- Owner (who needs to approve / negotiate: Legal, Sales, Security, Product)
- Deadline (by when the counterparty needs the change)
Negotiation discipline: do not propose 20 changes. Focus on the 5–10 that materially change risk.
Show full SKILL.md (555 more words)Show less
Step 5 — Finalize the package
- Ensure consistency (definitions used the same way everywhere)
- Confirm operational feasibility (can we actually comply?)
- Re-scan the Step 2 triage list and ensure each flagged item is represented in the issue log
- Provide a short “what we changed and why” summary
Perspective-specific checklists
A. Recipient checklist (incoming NDA — typical case)
| Topic | Red flags | Typical ask |
|---|---|---|
| Definition of Confidential Information | Overbroad; includes independently developed info; no marking/identification standard | Add reasonableness + identification standard; add exclusions |
| Purpose / Permitted Use | Any use restriction beyond evaluation; bans on internal sharing | Tie to stated purpose; allow internal need-to-know |
| Representatives | We are liable for any representative breach without control | Limit to those under written confidentiality; commercially reasonable care |
| Term & survival | Perpetual for everything; unclear start date | Fixed term; longer only for trade secrets |
| Return / destruction | Requires deletion of backups immediately | Add practical backup carve-out |
| Remedies | One-way fees + broad injunction language | Mutuality or reasonableness; clarify equitable relief scope |
| Liability / indemnity | Indemnity; unlimited damages; consequential damages | Cap or exclude categories; remove indemnity |
| Residuals | Allows use of “retained in memory” | Delete or narrow heavily |
M&A / Due diligence: ensure diligence sharing (advisors, financing, affiliates) is permitted and that data room exports/notes are covered.
B. Discloser checklist (when we are sharing sensitive info)
| Topic | Red flags | Typical ask |
|---|---|---|
| Definition | Too narrow; requires marking only; excludes oral disclosures | Add oral confirmation mechanism; broaden categories reasonably |
| Security standard | Only “reasonable” with no baseline | Add minimum safeguards, or align with internal policy |
| Exclusions | Too broad (e.g., “independently developed” with no proof) | Require written evidence of prior knowledge/independent development |
| Term & survival | Too short | Extend for sensitive categories; trade secret survival |
| Remedies | No equitable relief, no fees | Add equitable relief and/or fees (carefully) |
Investor / VC: watch for standstill, solicitation, and “no contact” provisions—these are not standard in plain NDAs and may need separate agreement.
Risk rating guide
| Rating | Meaning | Example |
|---|---|---|
| High | Creates material, uncapped, or operationally impossible risk | Broad indemnity + unlimited damages for any breach |
| Medium | Risk is real but manageable with process controls | Strict notice deadlines for compelled disclosure |
| Low | Mostly cosmetic or market-standard | Minor notice method issues |
Common pitfalls (issue → risk → fix)
| Issue | Risk | Suggested fix |
|---|---|---|
| “All information is confidential forever” | Operational burden; unfair risk allocation | Add fixed term + trade secret carve-out |
| No compelled disclosure carve-out | Breach if subpoenaed | Add “required by law” disclosure path |
| Return/destruction requires purge of backups | Impossible to comply | Add backup and system integrity exception |
| Recipient indemnifies discloser | Open-ended exposure | Remove indemnity; use direct damages only |
| Residuals clause | Allows de facto use of confidential info | Delete or restrict to non-trade-secret, non-source-code |
Review prompts (copy/paste)
A. Minimal prompt (fast)
- Role: Recipient/Discloser
- NDA type: one-way (unilateral)
- Purpose: …
- Please produce (1) exec summary, (2) clause-by-clause issue log table with: Clause, Issue, Risk, Preferred redline, Fallback, Rationale, Owner, Deadline, (3) top 5 negotiation points.
B. Deep prompt (recommended)
- Add constraints: affiliates, advisors, contractors, cross-border sharing, personal data, cloud tools.
- Ask for: preferred redline + fallback + rationale per issue.
Ownership & timing defaults (if the user does not specify)
Use these defaults to populate Owner and Deadline in the issue log:
| Topic | Default owner | Default deadline |
|---|---|---|
| Confidentiality scope/definition, exceptions, term/survival | Legal | Before signature |
| Security standards / audit rights | Security + Legal | Before signature |
| Return/destruction and backups | Security + IT + Legal | Before signature |
| Liability cap / damages / indemnity / fees | Legal + Finance | Before signature |
| Operational constraints (representatives, affiliates, tooling) | Legal + Business owner | Before signature |
© lawve-ai, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/nda-reviewer-jamie-tso of lawve-ai/awesome-legal-skills.
- SKILL.md
- LICENSE.txt
- README.md
- references/DURATION_SCOPE.md
- references/KEY_CLAUSES.md
- references/PARTY_OBLIGATIONS.md
- references/REMEDIES_LIABILITY.md
- references/STANDARD_EXCEPTIONS.md
Open the folder on GitHubat commit 045f738
Compare with similar skills
Nda Review Jamie Tso next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Nda Review Jamie Tso this skilllawve-ai/awesome-legal-skills | 847 | — | ~3k | Automated safety check: Pass | AGPL-3.0 | |
| Contract Reviewevolsb/claude-legal-skill | 464 | 1 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Commercial Legal Plapiotrowski-afk/commercial-legal-pl | 176 | 1 repos | ~4.1k | Automated safety check: Pass | Apache-2.0 | |
| Hand Drawnthreerocks/hand-drawn-styles | 2.2k | — | ~398 | Automated safety check: Pass | MIT | |
| Tabular Document Reviewanthropics/claude-for-legal | 9.6k | 3 repos | ~4.3k | Automated safety check: Pass | Apache-2.0 | |
| Tw Formal WritingImbad0202/tw-formal-writing | 179 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Commercial Legal Pl
apiotrowski-afk/commercial-legal-pl
Skill do analizy i tworzenia umów według polskiego prawa, ze szczególnym uwzględnieniem umów B2B, IP i IT (body leasing, NDA, wdrożenia, SaaS, przeniesienie praw autorskich, ugody).
Hand Drawn
threerocks/hand-drawn-styles
A skill your agent uses when users ask for a hand-drawn or illustrated image prompt, name one of the repository's 20 numbered styles or the 3.1 stable variant, or mention triggers such as…
- Official
Tabular Document Review
anthropics/claude-for-legal
Builds a review grid with one row per document and one column per data point, each cell cited to a verbatim quote, built for M&A diligence and other batch reviews.
Tw Formal Writing
Imbad0202/tw-formal-writing
台灣正式文件撰寫助手 — 涵蓋政府公文、政府機關其他文件、法律文件、人民對政府文書四類中文正式文件的撰寫（不含學術論文、商業文書、私人書信等，見下方排除清單）。
Contract Review Pro
CSlawyer1985/contract-review-pro
专业合同审核 Skill：7步工作流（含立场声明、框架审阅、类型路由）、5类通用门禁+16个专项门禁、终稿三件套+HTML可视化报告、8维度风险评分、修订5分类路由。完全自包含，零外部依赖。
More from lawve-ai/awesome-legal-skills
All 154 skills in this repoCustoms Trade Law Onur Kafkas
lawve-ai/awesome-legal-skills
U.S. An agent skill from lawve-ai/awesome-legal-skills.
Eu Data Act Oliver Schmidt Prietz
lawve-ai/awesome-legal-skills
Practitioner skill for advising on EU Regulation 2023/2854 (Data Act).
Litigation Deadline Calendar
lawve-ai/awesome-legal-skills
Calendar litigation and arbitration deadlines from a scheduling order.
Outlook Emails Lawvable
lawve-ai/awesome-legal-skills
Read, search, and download emails and attachments from Microsoft Outlook via OAuth2.
Ambiguity Report
lawve-ai/awesome-legal-skills
Turn an interpretive-ambiguity audit of a legal text — contract, statute, regulation, or judicial opinion — into a polished deliverable.
Az Eu Website Privacy Audit
lawve-ai/awesome-legal-skills
Audits a website for compliance with Azerbaijan's Law on Personal Data No.
Related
Categories
Questions about Nda Review Jamie Tso
What does Nda Review Jamie Tso do?
Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log…. Nda Review Jamie Tso is an agent skill from lawve-ai/awesome-legal-skills. Guide to review incoming one-way (unilateral) commercial NDAs in a jurisdiction-agnostic way, from either a Recipient or Discloser perspective (user-selected), producing a clause-by-clause issue log with preferred redlines, fallbacks, rationales, owners, and deadlines.
When should I use Nda Review Jamie Tso?
Nda Review Jamie Tso fits situations like: tasks that involve Contract review.
How do I install Nda Review Jamie Tso in Claude Code?
Run `npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a claude-code`. Or copy the skill folder (skills/nda-reviewer-jamie-tso in lawve-ai/awesome-legal-skills) into .claude/skills/nda-review-jamie-tso in your project. Claude Code loads it when a task matches its description.
How do I install Nda Review Jamie Tso in Codex?
Run `npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a codex`. Or copy the skill folder (skills/nda-reviewer-jamie-tso in lawve-ai/awesome-legal-skills) into .agents/skills/nda-review-jamie-tso in your project. Codex loads it when a task matches its description.
Can I use Nda Review Jamie Tso in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add lawve-ai/awesome-legal-skills --skill nda-review-jamie-tso -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nda-review-jamie-tso, .gemini/skills/nda-review-jamie-tso, .github/skills/nda-review-jamie-tso and .opencode/skills/nda-review-jamie-tso in your project.
What does Nda Review Jamie Tso need to run?
SKILL.md names no scripts, command-line tools or credentials: Nda Review Jamie Tso is instructions for the agent only.
Does Nda Review Jamie Tso access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Nda Review Jamie Tso safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Nda Review Jamie Tso use?
Nda Review Jamie Tso is published under the AGPL-3.0 licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Nda Review Jamie Tso use?
About 3k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5k tokens, read only when the agent opens those files.
What are the alternatives to Nda Review Jamie Tso?
Skills that share tags, products or a category with Nda Review Jamie Tso: Contract Review (evolsb/claude-legal-skill, 464 stars), Commercial Legal Pl (apiotrowski-afk/commercial-legal-pl, 176 stars), Hand Drawn (threerocks/hand-drawn-styles, 2.2k stars) and Tabular Document Review (anthropics/claude-for-legal, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Nda Review Jamie Tso?
lawve-ai (a GitHub organization) maintains it in lawve-ai/awesome-legal-skills, which has 847 GitHub stars. The repository holds 154 skills in this directory. The repository was last updated on October 2, 2026.
Source: lawve-ai/awesome-legal-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.