Contract Review
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
Reference for the standard clauses found in commercial non-disclosure agreements (mutual and one-way) — what each clause does, the surface forms it appears in, and how to recognise it in unfamiliar…
$ npx skills add benchflow-ai/skillsbench --skill nda-clause-taxonomy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install benchflow-ai/skillsbench nda-clause-taxonomy --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/benchflow-ai/skillsbench.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .claude/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .claude/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomyType 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 benchflow-ai/skillsbench --skill nda-clause-taxonomy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install benchflow-ai/skillsbench nda-clause-taxonomy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benchflow-ai/skillsbench.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .agents/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .agents/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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 benchflow-ai/skillsbench --skill nda-clause-taxonomy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install benchflow-ai/skillsbench nda-clause-taxonomy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benchflow-ai/skillsbench.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .cursor/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .cursor/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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/benchflow-ai/skillsbench.git --path tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy--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 benchflow-ai/skillsbench --skill nda-clause-taxonomy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install benchflow-ai/skillsbench nda-clause-taxonomy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benchflow-ai/skillsbench.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .gemini/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .gemini/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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 benchflow-ai/skillsbench nda-clause-taxonomyInstalls 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 benchflow-ai/skillsbench --skill nda-clause-taxonomy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/benchflow-ai/skillsbench.git skills-src && mkdir -p .github/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .github/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .github/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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 benchflow-ai/skillsbench --skill nda-clause-taxonomy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install benchflow-ai/skillsbench nda-clause-taxonomy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/benchflow-ai/skillsbench.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy .opencode/skills/nda-clause-taxonomy && 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-clause-taxonomy" agent skill from https://github.com/benchflow-ai/skillsbench/tree/main/tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy into .opencode/skills/nda-clause-taxonomy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nda-clause-taxonomy", 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.
nda-clause-taxonomyReference for the standard clauses found in commercial non-disclosure agreements (mutual and one-way) — what each clause does, the surface forms it appears in, and how to recognise it in unfamiliar…
Nda Clause Taxonomy is an agent skill from benchflow-ai/skillsbench. Reference for the standard clauses found in commercial non-disclosure agreements (mutual and one-way) — what each clause does, the surface forms it appears in, and how to recognise it in unfamiliar drafting. Use when reviewing, comparing, or extracting provisions from any confidentiality / NDA / mutual NDA / standstill-and-confidentiality agreement.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Legal & Compliance, covering Contract review. The repository describes itself as: SkillsBench evaluates how well skills work and how effective agents are at using them. The licence is Apache-2.0.
12 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9a1f4dd. It shows what the files ask for, not the result of running them.
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.
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.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Nda Clause Taxonomy loads about 2.9k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 1,473 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.
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.
The full file from benchflow-ai/skillsbench at commit 9a1f4dd, republished under its Apache-2.0 licence (© benchflow-ai). 1,473 words, ~2,874 tokens.
.claude/skills/nda-clause-taxonomy/SKILL.md (or your agent's skills folder).A working reference for someone reviewing a commercial NDA. Every NDA reuses the same handful of clauses; the wording varies. Use this to recognise which provision is which when the section headings don't match the clause function.
Before applying any review rule, identify which kind of NDA you're looking at, because conventions differ:
Apply rules in their proper context — a "must_be_absent" rule for standstills is appropriate for ordinary NDAs but not for M&A NDAs.
NDAs almost always order clauses this way:
Each entry below is "what it does", "names you'll see", "what to look for when reviewing".
What it does — sets the scope of what counts as protected. Usually written broadly ("all information disclosed... in oral, written, graphic, electronic or other form"), often with an illustrative list. Names — "Confidential Information", "Proprietary Information", "Information". Things to notice — does it cover oral disclosures? Are summaries/derivatives included? Does it pull the existence of the agreement and negotiations into the protected set (common in M&A)? Does it require markings like "Confidential" to attach (a "marking requirement")?
What it does — pulls four standard categories out of the definition, so the recipient is not on the hook for them. Names — "Exceptions", "Limitations on Confidential Information", "Confidential Information shall not include..." The four standard exceptions — (a) public domain through no fault of recipient, (b) prior knowledge evidenced by written records, (c) third-party received without restriction, (d) independent development without reference to the disclosed CI. A fifth — residuals (information unintentionally retained in the unaided memory of personnel) — is sometimes added, mostly by tech-company recipients; it is contentious and the disclosing side often resists it.
What it does — the operative restriction. Recipient must use CI only for the "Authorized Purpose" and not disclose except to permitted recipients. Names — "Non-Use and Non-Disclosure Obligations", "Confidentiality Obligations", "Use Restrictions". Things to notice — what is the standard of care ("same as own confidential information of like importance" vs. "reasonable care" vs. "best efforts")? Is non-use as tightly drawn as non-disclosure?
What it does — lets the recipient share with employees, advisors, affiliates who need to know. Names — "Representatives", "Authorized Recipients", embedded inside the use clause. Things to notice — does the recipient have to "advise" representatives, or "ensure" they comply, or "be responsible for breach by" them? "Be responsible for" is the strongest formulation and is what most playbooks want.
What it does — allows disclosure if required by court order, subpoena, regulatory request, or law. Names — "Required Disclosure", "Authorized Disclosure", "Disclosure Required by Law". Things to notice — does the recipient have to give prior written notice (where lawful) and reasonably cooperate with the disclosing party's effort to seek a protective order? Both are standard playbook asks.
What it does — on termination or request, recipient returns or destroys CI. Names — "Return of Information", "Copies", "Return or Destroy". Things to notice — does the clause allow destruction in lieu of return (it should — physically returning files is impractical)? Is there a back-up carve-out for routine IT-system backups (it should — purging tape/cloud backups is impractical and most playbooks accept retention if access is limited)? Is there a legal/compliance archive carve-out for one secure copy?
What it does — prevents the disclosure from being construed as a licence to use the underlying IP. Names — "No License", "Reservation of Rights", "Ownership".
What it does — disclaims warranties about the accuracy or completeness of the CI. Names — "No Warranty", "No Representations", "As Is".
What it does — sets when the agreement expires AND how long obligations survive afterwards. Names — "Term", "Term and Termination", "Duration", "Survival". Things to notice — these are two different periods and reviewers regularly conflate them. Term is how long new disclosures may be made (often 1–3 years). Survival is how long the confidentiality obligations continue once the agreement ends (often 3–5 years for general CI; trade secrets are often kept confidential indefinitely or "for as long as the information remains a trade secret"). Combined effective protection = term + survival.
What it does — recipient acknowledges that money damages would be inadequate and the disclosing party may seek an injunction or specific performance. Names — "Injunctive Relief", "Equitable Relief", "Remedies", "Specific Performance". Things to notice — best practice clauses include "without bond" (the disclosing party shouldn't have to post a bond to get an injunction). Some say "without prejudice to other remedies" — that's the cumulative-remedies clause and is also good.
What it does — picks which state's law governs. Names — "Governing Law", "Choice of Law", "Applicable Law". Things to notice — does it say "without regard to conflicts of laws principles" (it should, otherwise renvoi can pull in a different jurisdiction's law)? Is there a forum-selection clause separately? Most US playbooks specify Delaware, New York, or California.
What it does — restricts the parties' ability to transfer their rights and obligations. Names — "Assignment", "Successors and Assigns", "Binding Effect". Things to notice — most playbooks want a mutual written-consent requirement, often with a carve-out for assignment to affiliates and successors in interest (mergers, asset sales). Bare "no assignment without consent" without an affiliate carve-out is a common review item.
What it does — prohibits one party (usually the prospective acquirer) from acquiring securities, soliciting proxies, or otherwise pursuing a change-of-control transaction for some period. Names — "Standstill", "Standstill Provision", "No Acquisition". Things to notice — standstills are normal in M&A NDAs (12 months is typical) but inappropriate in an ordinary mutual NDA for vendor evaluation, partnership discussions, or technical diligence. If you see one in a non-M&A context, flag it. Even in M&A, watch for fall-away triggers (does it terminate on the target's announcement of a definitive agreement with a third party? on a public tender offer?).
What it does — restricts hiring of the other party's employees. Names — "Non-Solicitation", "No-Hire", "Employees". Things to notice — usual asks: limited duration (≤ 12 months), limited to employees with whom the receiving side actually had contact, carve-outs for general advertising, carve-outs for employees who initiated contact unsolicited.
Severability — invalid provision is severed/reformed, rest survives. Notice — how parties give notice (mail, email, courier). Counterparts — separate signatures combine into one agreement. Entire agreement — supersedes prior understandings. Waiver / non-waiver — failure to enforce is not a waiver. Interpretation — headings for convenience only, English controls.
When a draft uses non-standard headings, identify clauses by operative verbs:
When applying any deviation policy, these are the postures most often used:
© benchflow-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy of benchflow-ai/skillsbench.
Open the folder on GitHubat commit 9a1f4dd
Nda Clause Taxonomy 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 Clause Taxonomy this skillbenchflow-ai/skillsbench | 1.8k | — | ~2.9k | Automated safety check: Pass | Apache-2.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 |
evolsb/claude-legal-skill
Review legal contracts, NDAs, employment agreements, SaaS terms, and M&A documents.
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).
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…
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.
Imbad0202/tw-formal-writing
台灣正式文件撰寫助手 — 涵蓋政府公文、政府機關其他文件、法律文件、人民對政府文書四類中文正式文件的撰寫(不含學術論文、商業文書、私人書信等,見下方排除清單)。
CSlawyer1985/contract-review-pro
专业合同审核 Skill:7步工作流(含立场声明、框架审阅、类型路由)、5类通用门禁+16个专项门禁、终稿三件套+HTML可视化报告、8维度风险评分、修订5分类路由。完全自包含,零外部依赖。
benchflow-ai/skillsbench
This skill should be used when working on Lean 4 formalization projects to maintain persistent memory of successful proof patterns, failed approaches, project conventions, and user preferences…
benchflow-ai/skillsbench
World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, real-time streaming, and data infrastructure.
benchflow-ai/skillsbench
AC branch pi-model power flow equations (P/Q and |S|) with transformer tap ratio and phase shift, matching acopf-math-model.md and MATPOWER branch fields.
benchflow-ai/skillsbench
Civilization 6 district mechanics library. An agent skill from benchflow-ai/skillsbench.
benchflow-ai/skillsbench
Build deterministic, verifiable data visualizations with D3.js (v6).
benchflow-ai/skillsbench
DC power flow analysis for power systems. An agent skill from benchflow-ai/skillsbench.
Categories
Reference for the standard clauses found in commercial non-disclosure agreements (mutual and one-way) — what each clause does, the surface forms it appears in, and how to recognise it in unfamiliar…. Nda Clause Taxonomy is an agent skill from benchflow-ai/skillsbench. Reference for the standard clauses found in commercial non-disclosure agreements (mutual and one-way) — what each clause does, the surface forms it appears in, and how to recognise it in unfamiliar drafting.
Nda Clause Taxonomy fits situations like: extracting provisions from any confidentiality / NDA / mutual NDA / standstill-and-confidentiality agreement; tasks that involve Contract review.
Run `npx skills add benchflow-ai/skillsbench --skill nda-clause-taxonomy -a claude-code`. Or copy the skill folder (tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy in benchflow-ai/skillsbench) into .claude/skills/nda-clause-taxonomy in your project. Claude Code loads it when a task matches its description.
Run `npx skills add benchflow-ai/skillsbench --skill nda-clause-taxonomy -a codex`. Or copy the skill folder (tasks-extra/nda-playbook-review/environment/skills/nda-clause-taxonomy in benchflow-ai/skillsbench) into .agents/skills/nda-clause-taxonomy in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add benchflow-ai/skillsbench --skill nda-clause-taxonomy -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-clause-taxonomy, .gemini/skills/nda-clause-taxonomy, .github/skills/nda-clause-taxonomy and .opencode/skills/nda-clause-taxonomy in your project.
SKILL.md names no scripts, command-line tools or credentials: Nda Clause Taxonomy is instructions for the agent only.
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.
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.
Nda Clause Taxonomy is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Nda Clause Taxonomy: 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.
benchflow-ai (a GitHub organization) maintains it in benchflow-ai/skillsbench, which has 1,835 GitHub stars. The repository holds 189 skills in this directory. The repository was last updated on July 23, 2026.
Source: benchflow-ai/skillsbench on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.