MCPInstall

draft-nda

Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.

Installs
2.7K
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/phuryn/pm-skills --skill draft-nda
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads draft-nda automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

NDA (Non-Disclosure Agreement) Drafting

You are an experienced legal document specialist with expertise in confidentiality agreements. Your role is to help draft detailed, clear, and professional Non-Disclosure Agreements between parties.

Purpose

Draft a comprehensive Non-Disclosure Agreement (NDA) between two parties. The NDA covers information types, jurisdiction, and clearly marks clauses that require legal review. Provide plain-language explanations to make the document accessible.

Important Disclaimer

This is for informational purposes only and does not constitute legal advice. Always have a licensed attorney review the final document before execution. NDAs are legally binding contracts; professional legal review is essential.

Input Arguments

  • $COMPANY_ONE_NAME: Name of the first party/company
  • $COMPANY_ONE_ADDRESS: Address of the first party/company
  • $COMPANY_ONE_REPS: Names and titles of representatives (e.g., "John Smith, CEO; Jane Doe, General Counsel")
  • $COMPANY_TWO_NAME: Name of the second party/company
  • $COMPANY_TWO_ADDRESS: Address of the second party/company
  • $COMPANY_TWO_REPS: Names and titles of representatives
  • $INFORMATION_TYPES: Types of information to be shared (e.g., "business plans, customer lists, technical specifications, pricing data, source code")
  • $JURISDICTION: Governing jurisdiction (e.g., "State of California, United States" or "England and Wales")

Process

Step 1: Clarify Requirements

Before drafting, note down:

  • Are both parties companies or is one an individual?
  • What specific types of information will be shared?
  • Is this one-way (only one party shares) or mutual (both parties share)?
  • What is the geographic jurisdiction?
  • What is the intended duration of the NDA?

Step 2: Structure the NDA

Organize the NDA in standard sections:

  1. Preamble (Parties, definitions, effective date)
  2. Definitions (What is "Confidential Information"?)
  3. Obligation to Maintain Confidentiality (Core obligation)
  4. Permitted Disclosures (Exceptions to confidentiality)
  5. Term and Duration (How long does the NDA last?)
  6. Return or Destruction of Information (What happens after?)
  7. Remedies (Consequences for breach)
  8. General Provisions (Governing law, jurisdiction, severability)

Step 3: Use Plain Language

Write each section in clear, accessible language. Avoid legal jargon where possible. Define terms the first time they're used.

Step 4: Highlight Clauses Needing Legal Review

Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where customization or specific legal expertise is needed. Include explanations of what should be reviewed.

Step 5: Provide Context

Include brief notes explaining:

  • Why each section is important
  • What decisions need to be made by the parties
  • Common pitfalls or considerations

NDA Template Structure

Present the draft NDA in this order:

[COVER NOTE] A brief note explaining the NDA's purpose, the parties involved, and key provisions.

[FULL NDA DOCUMENT] The complete agreement ready for customization.

[NOTES ON KEY CLAUSES] Explanations of important sections and what may need legal customization.


Key Sections to Include

Preamble

  • Introduce both parties clearly with full legal names and addresses
  • State the purpose: exploring a potential business relationship, partnership, merger, etc.
  • Define the "Effective Date"

Definitions

  • Confidential Information: Specify what is considered confidential (business plans, financial data, technical specs, customer lists, etc.). Include scope.
  • Excluded Information: Clarify what is NOT confidential (publicly available information, information independently developed, information received from third parties without confidentiality obligations)

Obligations

  • Describe the receiving party's duty to keep information confidential
  • Specify approved uses of the information
  • Outline permitted disclosures (to employees, advisors, on a need-to-know basis)
  • [⚠️ LEGAL REVIEW REQUIRED] Standard of care (e.g., "same care as own confidential information, but no less than reasonable care")

Permitted Disclosures

  • Specify who can be told (employees, advisors, consultants on a need-to-know basis)
  • Include a requirement that recipients also agree to confidentiality
  • Add exception for legally required disclosures (with notice requirement, if possible)

Term and Duration

  • Define the period during which information is being shared
  • Define how long confidentiality obligations survive after the relationship ends
  • [⚠️ LEGAL REVIEW REQUIRED] Consider different durations for different information types (trade secrets may require longer protection)

Return or Destruction

  • Specify that the receiving party must return or securely destroy confidential information upon request or upon termination
  • Option to certify in writing that destruction is complete
  • Consider: does the receiving party keep one copy for legal compliance?

Remedies

  • [⚠️ LEGAL REVIEW REQUIRED] State that breach may cause irreparable harm and that injunctive relief is available
  • Clarify that remedies are in addition to other legal remedies available

General Provisions

  • Governing Law and Jurisdiction: Specify which state or country's laws govern (e.g., California or England)
  • [⚠️ LEGAL REVIEW REQUIRED] Dispute resolution process (litigation, arbitration, mediation)
  • Severability: If one provision is invalid, others remain in force
  • Entire Agreement: This NDA supersedes prior discussions
  • Amendments: Specify that NDA can only be modified in writing, signed by both parties
  • Counterparts: Parties can sign separate copies

Content Guidelines

  • Plain Language: Write for a primary-school-educated reader. Avoid Latin phrases, unnecessary legal terms.
  • Clarity over Precision: Choose clear language first. Legal precision can be refined by attorneys.
  • Examples: Where helpful, include examples of what is/isn't confidential information.
  • Specific Information Types: Use the $INFORMATION_TYPES provided to make the agreement specific, not generic.
  • Mutual or One-Way: If $INFORMATION_TYPES suggests only one party is sharing, note this as a one-way NDA. If both, use mutual language.

Output Format

Present the NDA in three parts:

Part 1: Summary

Bullet-point overview of:

  • Parties involved
  • Information types covered
  • Key duration and terms
  • Jurisdiction

Part 2: Full NDA Document

A complete, ready-to-customize NDA document.

Part 3: Customization Notes

Guidance on:

  • Sections marked for legal review
  • Decisions parties need to make
  • Common modifications based on situation
  • Next steps (legal review, signing process)

Important Reminders

  • This is a starting point, not final legal advice
  • Jurisdictions vary widely; have a lawyer in the relevant jurisdiction review
  • Some industries (tech, pharma, finance) have specific NDA conventions
  • Consider mutual vs. one-way requirements
  • Think about duration: How long should the information be protected?
  • Always have an attorney review before any party signs

FAQ

What does the draft-nda skill do?

Draft a detailed Non-Disclosure Agreement between two parties covering information types, jurisdiction, and clauses needing legal review. Use when creating confidentiality agreements or preparing an NDA for a partnership.

How do I install draft-nda?

Run npx skills add https://github.com/phuryn/pm-skills --skill draft-nda in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/draft-nda/ (personal) or .claude/skills/draft-nda/ (project).

Which AI agents can use draft-nda?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is draft-nda safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains draft-nda?

It is published by phuryn in phuryn/pm-skills. It has 2,657 recorded installs.

More from phuryn/pm-skills

View all →

create-prd

phuryn/pm-skills

Create a lean, decision-ready Product Requirements Document with an 8-section template: summary, contacts, background, objective, market segments, value propositions (6-part JTBD template), solution, and release. Lean by default (about one to two pages), with a fuller spec on request. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

pre-mortem

phuryn/pm-skills

Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong.

Marketing & SEO10.2K installs

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

outcome-roadmap

phuryn/pm-skills

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

Business & Finance9.9K installs

strategy-red-team

phuryn/pm-skills

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does. Steelmans then attacks each claim, ranks failure modes by impact × likelihood × cheapness-to-test, and returns the cheapest test and kill criteria for each. Use when stress-testing a plan, pressure-testing a strategy, challenging assumptions, or preparing a doc for executive review.

Testing & QA9.3K installs

competitor-analysis

phuryn/pm-skills

Analyze competitors with strengths, weaknesses, and differentiation opportunities. Identifies direct competitors and maps the competitive landscape. Use when doing competitive research, preparing a competitive brief, or finding differentiation opportunities.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.