본문으로 건너뛰기
cccskills
무료GitHub에 공개

draft-nda

Prepare a confidentiality agreement for two parties using their details, the information being shared, and the governing jurisdiction. Receive a summary, a customizable draft, and plain-language notes identifying decisions and clauses that need legal review.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

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.

설치 방법 보기

이럴 때 유용합니다

  • Preparing an NDA draft before partnership discussions
  • Drafting a one-way or mutual confidentiality agreement
  • Defining which shared information should be protected
  • Organizing clauses and decisions for a lawyer to review

포함된 파일(1)

  • SKILL.md7.3 KB

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: 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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7만2026년 10월 16일 업데이트

phuryn의 스킬 모두 보기

이 스킬의 문제 신고