Skip to main content
ClaudeWave
Skill17k estrellas del repoactualizado 6d ago

draft-nda

# ClaudeWave: draft-nda This Claude Code skill generates a customized Non-Disclosure Agreement template between two parties, incorporating specified information types, jurisdiction, and governing law. Users input party names, addresses, representatives, information categories, and jurisdiction to receive a structured NDA document with standard sections including definitions, confidentiality obligations, permitted disclosures, term duration, and remedies. Use this skill when preparing preliminary NDA frameworks for partnerships, business discussions, or vendor relationships that require legal counsel review before execution.

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/draft-nda && cp -r /tmp/draft-nda/pm-toolkit/skills/draft-nda ~/.claude/skills/draft-nda
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# 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
intended-vs-implementedSkill

The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.

shipping-artifactsSkill

The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.

ab-test-analysisSkill

Analyze 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.

cohort-analysisSkill

Perform 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.

sql-queriesSkill

Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.

brainstorm-okrsSkill

Brainstorm 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.

create-prdSkill

Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.

dummy-datasetSkill

Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.