draft-nda
phuryn/pm-skills · Agent Skill
Generates a detailed Non-Disclosure Agreement (NDA) between two parties, covering information types, jurisdiction, and clauses requiring legal review.
Jump to install ↓Overview
| Publisher | |
|---|---|
| Repository | phuryn/pm-skills ↗ |
| Skill folder | draft-nda |
| Stars | 26,102 |
| Bundled files | 1 |
| License | MIT |
| Last updated | March 2, 2026 |
| Links | Skill source ↗ · Repository ↗ |
Mozgi check
What we found in the skill files. Details come with a subscription.
Installation
A skill is a folder with a SKILL.md file. Pick your agent and run the commands in a terminal (macOS, Linux or Git Bash on Windows) from your project root.
Copy the prompt into Claude, Codex or another assistant: it will review the skill and install it for you.
Install the “draft-nda” skill from mozgi.io (https://mozgi.io/skills/draft-nda/) for me. 1. Download the archive: https://mozgi.io/skills/draft-nda/download If it fails, take the skill folder from the source: https://github.com/phuryn/pm-skills/tree/main/pm-toolkit/skills/draft-nda 2. Read SKILL.md and the other files. Check the skill is safe: no hidden commands, no sending data elsewhere, no scripts doing something other than described. If anything looks suspicious, stop and tell me. 3. Put the “draft-nda” folder into your agent's skills folder: .claude/skills/ for Claude Code, .agents/skills/ for Codex, .cursor/skills/ for Cursor, .gemini/skills/ for Gemini CLI. Inside the project if we are in one, otherwise in the home folder (~/.claude/skills/ etc.). 4. Make sure <skills folder>/draft-nda/SKILL.md exists. 5. Briefly tell me what this skill does and offer to try it on my task. If you cannot do a step yourself, tell me what to click or type.
git clone --depth 1 --branch main 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
Restart Claude Code — the skill appears in the list; call it manually with /draft-nda. For all projects use ~/.claude/skills.
git clone --depth 1 --branch main https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p .agents/skills cp -r /tmp/pm-skills/pm-toolkit/skills/draft-nda .agents/skills/draft-nda
Codex looks for skills in .agents/skills from the current folder up to the repo root; call one with /skills or $draft-nda. For all projects use ~/.agents/skills.
git clone --depth 1 --branch main https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p .cursor/skills cp -r /tmp/pm-skills/pm-toolkit/skills/draft-nda .cursor/skills/draft-nda
Cursor picks the skill up on start; call it with “/” in Agent chat. Cursor also reads .claude/skills and .agents/skills. For all projects use ~/.cursor/skills.
git clone --depth 1 --branch main https://github.com/phuryn/pm-skills.git /tmp/pm-skills mkdir -p .gemini/skills cp -r /tmp/pm-skills/pm-toolkit/skills/draft-nda .gemini/skills/draft-nda
Gemini CLI offers to activate the skill when a task matches — you approve it. For all projects use ~/.gemini/skills.
Read SKILL.md and any companion files before deciding whether to install. Click a file to preview it.
SKILL.md contents
Original author text · read-onlyNDA (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
Frequently asked questions
What does the draft-nda skill do?
Generates a detailed Non-Disclosure Agreement (NDA) between two parties, covering information types, jurisdiction, and clauses requiring legal review.
How do I install draft-nda?
Open the “Installation” block on this page and pick your agent — Claude Code, Codex, Cursor or Gemini CLI — for ready-made commands that copy the skill folder to the right place. Or copy the prompt from the “Via assistant” tab and let the assistant review and install the skill.
Which AI models work with draft-nda?
Skills are plain Markdown instructions (the Agent Skills format), so draft-nda works with any agent that reads SKILL.md: Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and more. The model loads the instructions only when a task matches the skill's description.
Is draft-nda free?
The skill is published openly by phuryn under the MIT license. The skill itself costs nothing — you only pay your AI provider for the tokens you use.
Is it safe to install skills?
A skill is a set of instructions your agent will follow, so read SKILL.md and its companion files before installing. Scripts in the skill folder only run if your agent runs them — keep an eye on what it does and do not grant unnecessary permissions.
How is a skill different from an MCP server or a plugin?
An MCP server or plugin gives the model new tools — code that runs and returns a result. A skill gives it knowledge and process: how to approach a task, which steps to follow and what good output looks like. It needs no server or API key.