nda-analyser

$npx mdskill add mohitagw15856/pm-claude-skills/nda-analyser

NDAs are often treated as routine paperwork but contain terms with significant long-term consequences. This skill analyses them systematically.

SKILL.md

.github/skills/nda-analyserView on GitHub ↗
---
name: nda-analyser
description: "Analyse a Non-Disclosure Agreement (NDA) and flag key terms, unusual provisions, and negotiation points. Use when asked to review an NDA, mutual NDA, confidentiality agreement, or non-disclosure deed. Produces clause-by-clause analysis with risk flags and a negotiation checklist."
---

# NDA Analyser Skill

NDAs are often treated as routine paperwork but contain terms with significant long-term consequences. This skill analyses them systematically.

## Required Inputs
- **NDA text** (paste in full or describe key clauses)
- **Your party position** (disclosing / receiving / mutual)
- **Purpose of the NDA** (e.g. pre-sales, hiring, M&A, partnership)
- **Industry context** (optional)

## Output Structure

### 1. NDA Type and Parties
- **Type:** Unilateral / Mutual
- **Disclosing party:** [Name]
- **Receiving party:** [Name]
- **Purpose:** [As stated]
- **Governing law:** [Jurisdiction]
- **Term:** [Duration of obligations]

### 2. Definition of Confidential Information
- **How broadly defined?** Narrow / Standard / Very broad
- **Oral disclosures included?** Yes / No / With conditions
- **Standard exclusions present?** [public domain, prior knowledge, independently developed, legally required disclosure]
- **Flag:** [Unusual inclusions or missing exclusions]

### 3. Key Clause Analysis

**[Clause name] — Concern / Watch / Standard**
- **What it says:** [Plain English]
- **Issue:** [Why flagged]
- **Standard position:** [What this typically looks like]
- **Negotiation suggestion:** [If applicable]

Clauses always covered: permitted use, non-solicitation/non-compete, term and post-termination obligations, return/destruction of information, remedies, liability, residuals clause.

### 4. Negotiation Checklist

| Point | Current position | Suggested ask |
|---|---|---|
| [e.g. Confidentiality term] | [e.g. 5 years] | [e.g. Reduce to 2 years] |

### 5. Plain English Verdict
2-3 sentences. Standard NDA, one-sided, or needs a lawyer?

---

WARNING: This analysis is for informational purposes only and is not legal advice. Consult a qualified solicitor before signing.

## Quality Checks

- [ ] Definition of confidential information assessed for scope (narrow / standard / very broad)
- [ ] Residuals clause checked (allows memory use of disclosed information — high-risk)
- [ ] Non-solicitation / non-compete provisions flagged
- [ ] Post-termination obligations duration noted
- [ ] Plain English verdict given (standard / one-sided / needs lawyer)
- [ ] Disclaimer is included

## Example Trigger Phrases
- "Analyse this NDA"
- "Review this confidentiality agreement"
- "Is this NDA standard or unusual?"
- "What should I negotiate in this mutual NDA?"

More from mohitagw15856/pm-claude-skills

SkillDescription
360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.