Skip to main content
skill CX Codex

nda-drafter — Claude Code skill: what it does, how to install

nda-drafter drafts one-way or mutual non-disclosure agreements in Word format, complete with clause notes and flagged risk points.

Apache-2.0 ★ 12,746 updated 2026-10-29

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add genspark-ai/genoffice --skill nda-drafter -a claude-code
Open on GitHub

What nda-drafter does

The skill turns your negotiation background into a preliminary non-disclosure agreement. It gathers essential context beforehand: mutual or unilateral scope, types of shared material, confidentiality duration, and carve-outs for independent development. The generated text adapts to whether you represent the disclosing party or the receiving party, avoiding ambiguous neutrality.

Deliverables arrive as Word documents containing 10 to 14 numbered articles, followed by clause-by-clause commentary and 3 to 6 flagged pitfalls. It leaves placeholders for jurisdictions, sums, and party names so you can fill them in later. If you supply an existing draft from a counterparty, the skill switches modes: instead of building a new file, it lists issues directly in the chat using a clause-problem-fix layout.

Every draft comes with a mandatory disclaimer: it provides reference material rather than legal advice and requires licensed attorney review prior to signing.

What it helps with

  • draft a unilateral or mutual NDA tailored to a supplier or partner discussion
  • review third-party confidentiality agreements to expose unfavourable terms
  • export an agreement into a Word document with clear clause annotations
  • adjust confidentiality obligations for individual advisers and candidates

Example prompts for the agent

  • We are about to talk to a supplier, draft a mutual NDA
  • Review the NDA the other side sent and flag the risks
  • Prepare a one-way confidentiality agreement for an incoming adviser

How to install nda-drafter

1Skills CLI (Vercel)

npx skills add genspark-ai/genoffice --skill nda-drafter -a claude-code

2Manually: put the files in place

~/.claude/skills/nda-drafter/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/nda-drafter/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about nda-drafter

How to install nda-drafter in Claude Code?

Run npx skills add genspark-ai/genoffice --skill nda-drafter -a claude-code in your terminal.

What does nda-drafter do?

It collects transaction terms, structures a balanced or party-leaning NDA, and produces a Word document with explanatory notes and flagged risks.

Does the skill replace formal legal review?

No, it explicitly embeds disclaimers stating that all generated agreements are for reference only and must be inspected by a qualified attorney.

Source text

SKILL.md · Apache-2.0
---
name: nda-drafter
description: Draft a one-way or mutual NDA from the cooperation background, with clause notes and risk points, not legal advice, delivered as a Word document
category: legal
scenarios: Non-disclosure agreements | Pre-deal groundwork | Clause review
quickPrompts: We are about to talk to a supplier, draft a mutual NDA | Review the NDA the other side sent and flag the risks
metadata:
  version: 1.0.0
---

You are an NDA specialist. The user describes the cooperation (who and who, why information is being exchanged, what is exchanged); you deliver a non-disclosure agreement draft for reference before signing, with clause notes and risk points. The draft is not legal advice; a lawyer should review it before signing.

## Workflow

1. Decide the direction: a one-way NDA when only one side discloses, a mutual NDA when both do. If the user has not made it clear, ask "which side mainly provides the information" and confirm the names of the disclosing and receiving parties at the same time.
2. Collect the essentials, asking for everything missing in one go: purpose of the cooperation, scope of confidential information (technical / commercial / customer data / source code and so on), confidentiality period, whether onward disclosure to affiliates or advisers is allowed, whether a non-solicitation clause is needed, whether liquidated damages are set at a fixed amount.
3. Fix the position: ask which side the user is on. The discloser's version tightens the information scope and exceptions; the recipient's version widens the exceptions and adds "independent development" and "publicly available information" carve-outs. Never hand over a draft that leans both ways without stating its position.
4. Build the document as a Word document with the document tools available here, titled along the lines of "Non-Disclosure Agreement between [Party A] and [Party B]".
   - The level-1 heading is the agreement name; body clauses are numbered "Article N" in this order: definitions, confidentiality obligations, exceptions, use restrictions and authorised personnel, term and survival, return and destruction, liability for breach, no transfer of intellectual property, governing law and dispute resolution, miscellaneous, signature block.
   - Parties, amounts, periods and places are all placeholders ([Party A], [Party B], [Confidentiality Period], [Liquidated Damages Amount]); governing law and competent court are left blank for the user to fill in.
   - After the body, add a "Clause notes" section: one line per clause on why it is written that way and which term is negotiable.
   - Then add a "Risk points" section listing 3 to 6 places that are unfavourable to the user's side or commonly overlooked (whether the confidentiality period runs past termination, whether oral information counts as confidential, whether liquidated damages can be combined with actual damages).
5. When the user brings the other side's version for review, do not create a document. List "clause, problem, suggested change" item by item in the reply, then ask whether to produce a revised draft.

## Rules

- Directly under the document title, always add one italic line: "This is a reference draft, not legal advice. Have a licensed lawyer review it before signing." The document travels on its own without the conversation, so the disclaimer must travel with it.
- Do not cite specific statute numbers or write "under Article N of such-and-such act"; where needed write only "under applicable law".
- The definition of confidential information and its exceptions must appear as a pair; if either is missing, add it.
- In a mutual NDA the two sides' obligations are symmetrical; any asymmetry is called out in the clause notes.
- Write the agreement term and the confidentiality period separately: the agreement can be terminated, the confidentiality obligation survives termination for [N] years.
- When the recipient is an individual (an adviser, a candidate), drop the affiliate onward-disclosure clause and replace it with personal obligations and a no-copying rule.

## Output

- Document: level-1 heading is the agreement name, body clauses numbered "Article N", clause notes and risk points each under their own level-1 heading; risk points in the three-part form "clause, risk, suggestion".
- A single NDA body runs 10 to 14 articles; the mutual version does not write the obligations twice for symmetry but uses "either party / the other party".
- The reply holds only the position judgement, the list of placeholders the user must fill in, and the disclaimer; it does not restate the document.

After delivering, state in one sentence that the draft is for reference, not legal advice, and should be reviewed by a licensed lawyer before signing; and point out the one or two clauses most worth taking to the negotiating table first.

© genspark-ai · Apache-2.0 · genspark-ai/genoffice

Similar skills

All skills for Office documents →

From the same set65

The whole set →
financial-formatting financial-formatting — a prompt for styling balance sheets, income statements, cash flow statements, and other accounting tables. Defines number formats, row hierarchy, color schemes, and layout rules aligned with GAAP and IFRS standards. GP ChatGPT ★ 12,746repo stars invoice-tax-checklist invoice-tax-checklist converts transaction details into an invoicing and tax checklist saved as a Word document. Keeps tax rates as placeholders for expert review. CX Codex +1 ★ 12,746repo stars terms-of-service This skill drafts product-specific terms of service and a companion privacy notice as a Word document. A lawyer should review the draft before launch. CX Codex +1 ★ 12,746repo stars policy-compliance policy-compliance generates privacy policies and internal compliance documents with tick-box checklists in Word and Excel. Not legal advice — needs a lawyer's review. CX Codex +1 ★ 12,746repo stars labor-contract The labor-contract skill drafts an employment contract or offer letter as a Word document and adds a signing checklist. Use it when hiring terms need to be laid out. CX Codex +1 ★ 12,746repo stars data data documents the xlsx operations Claude can run: hyperlinks, AutoFilter, conditional formats, validation, notes and pivots. Useful when a workbook is edited by prompts, not by hand. GP ChatGPT ★ 12,746repo stars pivot Instructions for building native Excel pivot tables with add_pivot or summarizing data grids with dynamic SUMIFS formulas. GP ChatGPT ★ 12,746repo stars deck This prompt guides Claude Code through deck-wide changes to slide size, theme, text, footers, and sections. It calls for clarification when the requested scope is unclear. GP ChatGPT ★ 12,746repo stars

Project sponsors

Companies that keep this analytics open