draft-nda
by phuryndraft-nda helps draft a detailed Non-Disclosure Agreement between two parties, covering information types, jurisdiction, and clauses flagged for legal review. Use this draft-nda skill when preparing confidentiality agreements, partnership NDAs, or a structured first draft for legal teams and review workflows.
This skill scores 74/100, which is acceptable for listing with caveats. Directory users can expect a real, triggerable NDA-drafting workflow with enough structure to reduce guesswork versus a generic prompt, but they should also expect limited supporting assets and some adoption friction around setup and legal review.
- Explicit trigger language for drafting NDAs, including when to use it for confidentiality agreements and partnerships.
- Substantial workflow content: detailed inputs for parties, information types, jurisdiction, and review-marked clauses, plus plain-language explanations.
- Clear legal cautioning and role framing that helps agents avoid overclaiming legal authority.
- No supporting scripts, references, or install command, so users must rely on the single SKILL.md for implementation guidance.
- The skill is informative rather than jurisdiction-specific legal guidance, and it repeatedly requires attorney review before execution.
Overview of draft-nda skill
What draft-nda does
The draft-nda skill helps generate a detailed Non-Disclosure Agreement between two parties, with the core terms organized for legal review rather than casual copywriting. It is built for users who need a practical first draft that covers party details, protected information, jurisdiction, and reviewable clause language.
Who this is for
Use draft-nda if you are preparing an NDA for a partnership, vendor relationship, collaboration, or pre-contract discussion and want a structured starting point. It is most useful for legal ops, founders, project leads, and assistants supporting draft-nda for Legal workflows where speed matters but the document still needs review.
What makes it different
This is not a generic “write me an NDA” prompt. The skill expects specific party data and clause inputs, then produces a document that flags areas needing legal attention. That makes draft-nda more decision-ready than a freeform prompt when you need both readability and drafting discipline.
How to Use draft-nda skill
Install draft-nda
Install the draft-nda skill in the repo context you use for skills, then confirm the skill files are available before prompting. A typical install path looks like npx skills add phuryn/pm-skills --skill draft-nda, followed by checking pm-toolkit/skills/draft-nda/SKILL.md.
Give the skill the right inputs
draft-nda usage works best when you provide complete party metadata and the business context up front. At minimum, include company names, addresses, representative names, the information types to protect, jurisdiction, term length, and any special clauses you know you need, such as mutual vs. one-way confidentiality or permitted disclosures.
Read the right files first
Start with SKILL.md to understand the drafting flow and required arguments. If your environment mirrors the source repo, also inspect surrounding skill conventions in pm-toolkit/skills/ so you can align tone, output shape, and any downstream review process before asking for a final draft.
Turn a rough ask into a usable prompt
A weak request like “draft an NDA” leaves too many variables open. A stronger draft-nda guide prompt is: “Draft a mutual NDA between Acme Labs and Northstar Data for a product integration discussion. Use California law, 2-year term, include customer data, source code, pricing, and roadmaps, and mark any clauses that need attorney review.” That kind of input improves clause coverage and reduces back-and-forth.
draft-nda skill FAQ
Is draft-nda for Legal only?
No, but draft-nda for Legal is the best fit when a legal team or legal-adjacent workflow will review the output. Non-legal users can draft a starting point, but the skill explicitly expects attorney review before execution.
How does it compare with a normal prompt?
A normal prompt can produce a generic NDA, but draft-nda gives you a more controlled drafting workflow with explicit fields and legal caution points. The main advantage is less guesswork around party data, scope of confidential information, and review-sensitive clauses.
Is it beginner-friendly?
Yes, if you can supply basic deal information. The skill is approachable for beginners because the required inputs are concrete, but it still depends on you knowing the business arrangement and jurisdiction you want reflected.
When should I not use it?
Do not use draft-nda when you need final legal advice, jurisdiction-specific negotiation strategy, or a document that must be tailored to a regulated transaction without review. If the deal has unusual data-transfer, IP assignment, export-control, or privacy issues, treat the output as a draft only.
How to Improve draft-nda skill
Provide clause-level decisions, not just party names
The biggest quality jump comes from specifying what the NDA should actually do. Tell the skill whether the NDA is mutual or one-way, what counts as confidential information, whether oral disclosures are covered, and whether exceptions for prior knowledge, public information, or compelled disclosure should be included.
Add the facts that change the legal shape
If you want a stronger draft-nda output, include the governing law, duration, survival period, venue expectations, and any special business constraints. These details matter more than stylistic preferences because they affect enforceability, scope, and whether the draft is usable at all.
Use the first draft to find missing decisions
The first output should be treated as a review draft, not a finished contract. Look for gaps in signatory authority, defined terms, return-or-destruction obligations, and any clause the skill marks for legal review, then rerun draft-nda with those missing decisions filled in.
Avoid vague source material
If you only say “for a partnership,” the skill has to guess about information risk and contract structure. Better inputs look like: “two technology vendors sharing roadmap data for a 90-day evaluation, mutual confidentiality, Delaware law, and disclosure limited to named employees.” Specificity helps draft-nda produce a cleaner, more reviewable document.