.claude/skills/draft-nda/SKILL.md
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.
npx skillsauth add shalevamin/The-_Ultimate_agents draft-ndaInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
4 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
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.
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.
$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")Before drafting, note down:
Organize the NDA in standard sections:
Write each section in clear, accessible language. Avoid legal jargon where possible. Define terms the first time they're used.
Mark sections with [⚠️ LEGAL REVIEW REQUIRED] where customization or specific legal expertise is needed. Include explanations of what should be reviewed.
Include brief notes explaining:
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.
Present the NDA in three parts:
Bullet-point overview of:
A complete, ready-to-customize NDA document.
Guidance on:
development
Use when building cross-platform applications with Flutter 3+ and Dart. Invoke for widget development, Riverpod/Bloc state management, GoRouter navigation, platform-specific implementations, performance optimization.
testing
Use when fine-tuning LLMs, training custom models, or adapting foundation models for specific tasks. Invoke for configuring LoRA/QLoRA adapters, preparing JSONL training datasets, setting hyperparameters for fine-tuning runs, adapter training, transfer learning, finetuning with Hugging Face PEFT, OpenAI fine-tuning, instruction tuning, RLHF, DPO, or quantizing and deploying fine-tuned models. Trigger terms include: LoRA, QLoRA, PEFT, finetuning, fine-tuning, adapter tuning, LLM training, model training, custom model.
tools
Use the Figma MCP server to fetch design context, screenshots, variables, and assets from Figma, and to translate Figma nodes into production code. Trigger when a task involves Figma URLs, node IDs, design-to-code implementation, or Figma MCP setup and troubleshooting.
tools
Translate Figma nodes into production-ready code with 1:1 visual fidelity using the Figma MCP workflow (design context, screenshots, assets, and project-convention translation). Trigger when the user provides Figma URLs or node IDs, or asks to implement designs or components that must match Figma specs. Requires a working Figma MCP server connection.