draft-nda skill
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.
Is the draft-nda skill safe?
Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.
No findings.
Install the draft-nda skill
A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.
git clone --depth 1 https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p ~/.claude/skills cp -r /tmp/pm-skills/pm-toolkit/skills/draft-nda ~/.claude/skills/draft-nda
In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub
The instructions your agent would load
SKILL.md as published, without the frontmatter. Read it on GitHub
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
- $COMPANYONENAME: Name of the first party/company
- $COMPANYONEADDRESS: Address of the first party/company
- $COMPANYONEREPS: Names and titles of representatives (e.g., "John Smith, CEO; Jane Doe, General Counsel")
- $COMPANYTWONAME: Name of the second party/company
- $COMPANYTWOADDRESS: Address of the second party/company
- $COMPANYTWOREPS: 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:
- Preamble (Parties, definitions, effective date)
- Definitions (What is "Confidential Information"?)
- Obligation to Maintain Confidentiality (Core obligation)
- Permitted Disclosures (Exceptions to confidentiality)
- Term and Duration (How long does the NDA last?)
- Return or Destruction of Information (What happens after?)
- Remedies (Consequences for breach)
- 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
More skills from phuryn/pm-skills
- Aab-test-analysisAnalyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
- Aanalyze-feature-requestsAnalyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
- Aansoff-matrixGenerate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
- Abeachhead-segmentIdentify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
- Abrainstorm-experiments-existingDesign experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
- Abrainstorm-experiments-newDesign lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
- Abrainstorm-ideas-existingBrainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
- Abrainstorm-ideas-newBrainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.
- Abrainstorm-okrsBrainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
- Abusiness-modelGenerate a Business Model Canvas with all 9 building blocks. Use when creating a business model, documenting how a business creates value, or analyzing an existing business model.
- Acode-reviewReview code for actionable defects. Correctness is the core; performance and security are optional sub-cases of the same engine. Anchors on agreements between participants across a boundary, forces a violating execution, and refutes every candidate before reporting. Use when asked to review changes, find bugs, audit a codebase, or check whether a fix is safe.
- Acohort-analysisPerform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.