Individual skill
nda-drafter
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
skills/recommended/nda-drafter/SKILL.md
Source commit e1f50e90d246f3ecc6427d2a0af90f04f37810ec
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 12,119
- Repository last updated
- Nov 10, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- office-suite Repository topic
- ai-agent Repository topic
- ai Repository topic
- spreadsheet Repository topic
- pdf-editor Repository topic
- docx Repository topic
- xlsx Repository topic
- pptx Repository topic
- excel Repository topic
- powerpoint Repository topic
- legal Derived category
- productivity Derived category
- productivity-notes Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
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.