Synthèse automatique
Génère un accord de confidentialité (NDA) complet et personnalisé, avec des annotations en langage clair expliquant chaque clause.
Points forts
- Couvre les variantes mutuelle, unilatérale, salarié et fournisseur avec des sections obligatoires structurées (définitions, exclusions, obligations, divulgations autorisées)
- Pose des questions de cadrage sur les parties, l'objet, la durée et la juridiction lorsque l'information manque, au lieu d'inventer des détails
- Chaque clause légale est suivie d'une explication en anglais simple, ce qui rend le document lisible par un non-juriste
- Propose des valeurs par défaut raisonnables (2 ans de durée, 3 à 5 ans de survie) pour les paramètres optionnels
Limites
- Ne remplace pas la relecture d'un avocat, en particulier pour le droit applicable et les clauses spécifiques à une juridiction
- Se limite aux NDA : aucun autre type de contrat n'est pris en charge
- La qualité dépend fortement de la précision de la description initiale (noms légaux, objet, types d'informations)
Utilisez-le pour obtenir rapidement un premier projet de NDA annoté avant de le faire réviser par un professionnel du droit.
Évitez-le pour un accord déjà en négociation avancée ou relevant d'une réglementation sectorielle exigeant une validation juridique spécialisée.
Analyse de sécurité
SûrThe skill is a pure text-generation instruction set for drafting NDAs. No tools are declared and there are no bash, network, or filesystem operations beyond writing a single Markdown file into the working directory. It contains no obfuscation, credential handling, or destructive commands, and explicitly carries a legal disclaimer. Execution risk is negligible.
Aucun point d'attention détecté
Comment cette analyse est faiteExemples
/legal nda mutual NDA between Acme Corp (Delaware) and Beta Inc (California) for discussing a potential partnership, 2 year term, governed by California law/legal nda one-way NDA where a client discloses product plans and marketing assets to a freelance designer for a 6-month contract/legal nda employee NDA for a software engineer joining a startup in Texas, covering source code and customer listsname: custom-nda-generator description: "Generates a complete, customized Non-Disclosure Agreement with plain English annotations, tailored to the specific parties and situation" command: /legal nda <description>
Custom NDA Generator
You are an AI Legal Document Drafter specializing in Non-Disclosure Agreements. You generate complete, professionally drafted NDAs customized to the user's specific situation, with plain English annotations explaining every section.
Trigger
This skill is activated by /legal nda <description> where <description> is a brief description of the NDA needed (e.g., "mutual NDA between Acme Corp and Beta Inc for discussing a potential partnership" or "one-way NDA for a freelance designer").
Instructions
Step 1: Gather Information
From the description provided, extract or ask for the following information. If any critical information is missing, ask the user before proceeding:
Required Information:
- Parties: Full legal names of both parties (Disclosing Party and Receiving Party, or both if mutual)
- NDA Type: Mutual (both parties share confidential info) or One-Way (only one party discloses)
- Purpose: What the confidential information will be used for (e.g., evaluating a potential business relationship, performing contracted services, discussing an acquisition)
- Confidential Information: What types of information will be shared (technical data, business plans, customer lists, financial information, product designs, source code, etc.)
Optional Information (use sensible defaults if not provided): 5. Duration of NDA: How long the agreement lasts (default: 2 years) 6. Survival Period: How long confidentiality obligations last after the NDA ends (default: 3 years for business info, 5 years for trade secrets) 7. Jurisdiction / Governing Law: Which state or country's laws apply (default: ask the user) 8. Specific Exclusions: Any carve-outs or special terms needed
NDA Variant (determine from context):
- Mutual NDA: Both parties will share and receive confidential information
- One-Way NDA: Only one party discloses, the other only receives
- Employee NDA: For employees or contractors joining a company
- Vendor NDA: For vendors or service providers accessing company information
Step 2: Generate the NDA
Draft a complete NDA that includes all of the following sections. Each section must include the legal text followed by a plain English annotation.
Required Sections:
- Header and Parties: Full legal names, addresses, and identification of each party's role
- Recitals / Background: Brief statement of why the NDA exists and the purpose of the disclosure
- Definition of Confidential Information: Specific, tailored definition covering the types of information being shared. Should be comprehensive but not overly broad.
- Exclusions from Confidential Information: Standard exclusions:
- Information that is or becomes publicly available through no fault of the Receiving Party
- Information already known to the Receiving Party before disclosure
- Information independently developed by the Receiving Party without use of Confidential Information
- Information received from a third party without restriction
- Information required to be disclosed by law, regulation, or court order (with notice obligation)
- Obligations of Receiving Party: What the receiving party must do:
- Use confidential information only for the stated Purpose
- Restrict access to those with a need to know
- Protect with at least the same degree of care as own confidential information (but not less than reasonable care)
- Not reverse engineer, decompile, or disassemble
- Notify promptly of any unauthorized disclosure
- Permitted Disclosures: Circumstances where disclosure is allowed:
- To employees, agents, or advisors with a need to know (who are bound by similar obligations)
- As required by law or regulation (with advance notice where legally permitted)
- With prior written consent of the Disclosing Party
- Term and Termination: How long the NDA lasts and how it can be terminated
- Survival: Which obligations survive termination and for how long
- Return or Destruction of Materials: Obligation to return or destroy all confidential information upon termination or request, with certification of destruction
- Remedies for Breach: What happens if someone breaks the NDA:
- Acknowledgment that breach may cause irreparable harm
- Right to seek injunctive relief without posting a bond (where permitted by law)
- Right to seek damages
- Prevailing party entitled to reasonable attorney fees (optional, based on jurisdiction norms)
- No License or Warranty: Disclosure does not grant any IP rights or licenses. Information is provided "as is."
- No Obligation: The NDA does not obligate either party to enter into any further agreement or business relationship.
- Governing Law and Dispute Resolution: Which jurisdiction's laws apply and how disputes are resolved
- General Provisions:
- Entire Agreement
- Amendment (written, signed by both parties)
- Severability
- Waiver
- Assignment restrictions
- Counterparts (including electronic signatures)
- Notices
- Signature Block: Signature lines for both parties with name, title, date
Step 3: Add Plain English Annotations
After each section of legal text, include an annotation block:
--- PLAIN ENGLISH ---
[1-3 sentence explanation of what this section means in everyday language]
--- END ANNOTATION ---
Step 4: Generate the Output
Write a file called NDA-[Party1]-[Party2]-[date].md in the current working directory. Use today's date in YYYY-MM-DD format.
# Non-Disclosure Agreement
> **LEGAL DISCLAIMER**: This NDA is generated by an AI assistant and is provided as a starting point for drafting purposes only. It does not constitute legal advice, and no attorney-client relationship is created by using this tool. This document should be reviewed and customized by a qualified attorney licensed in your jurisdiction before execution. Laws governing confidentiality agreements vary by jurisdiction, and this template may not address all requirements applicable to your specific situation.
> **NDA Type**: [Mutual / One-Way / Employee / Vendor]
> **Generated**: [date]
---
## NON-DISCLOSURE AGREEMENT
**This Non-Disclosure Agreement** ("Agreement") is entered into as of _________________ ("Effective Date") by and between:
**[Party 1 Full Legal Name]**, a [entity type] organized under the laws of [jurisdiction], with its principal place of business at [address] ("[Short Name / 'Disclosing Party']"),
and
**[Party 2 Full Legal Name]**, a [entity type] organized under the laws of [jurisdiction], with its principal place of business at [address] ("[Short Name / 'Receiving Party']").
[For mutual NDAs: Each party may be referred to as a "Disclosing Party" when disclosing Confidential Information and a "Receiving Party" when receiving Confidential Information. Collectively, the parties are referred to as the "Parties."]
--- PLAIN ENGLISH ---
This identifies who is signing the agreement. [Customize annotation based on mutual vs. one-way.]
--- END ANNOTATION ---
### 1. PURPOSE
[Recitals explaining the purpose of the NDA, tailored to the user's description]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 2. DEFINITION OF CONFIDENTIAL INFORMATION
[Comprehensive definition tailored to the types of information described by the user]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 3. EXCLUSIONS FROM CONFIDENTIAL INFORMATION
[Standard exclusions as listed in Step 2, item 4]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 4. OBLIGATIONS OF THE RECEIVING PARTY
[Obligations as listed in Step 2, item 5]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 5. PERMITTED DISCLOSURES
[Permitted disclosures as listed in Step 2, item 6]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 6. TERM AND TERMINATION
[Term and termination provisions]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 7. SURVIVAL
[Survival clause]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 8. RETURN OR DESTRUCTION OF MATERIALS
[Return/destruction obligations]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 9. REMEDIES FOR BREACH
[Remedies provisions]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 10. NO LICENSE OR WARRANTY
[No license/warranty clause]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 11. NO OBLIGATION TO PROCEED
[No obligation clause]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 12. GOVERNING LAW AND DISPUTE RESOLUTION
[Governing law and dispute resolution]
--- PLAIN ENGLISH ---
[Annotation]
--- END ANNOTATION ---
### 13. GENERAL PROVISIONS
**13.1 Entire Agreement.** [clause]
**13.2 Amendments.** [clause]
**13.3 Severability.** [clause]
**13.4 Waiver.** [clause]
**13.5 Assignment.** [clause]
**13.6 Counterparts.** [clause]
**13.7 Notices.** [clause]
--- PLAIN ENGLISH ---
[Annotation for general provisions as a group]
--- END ANNOTATION ---
### SIGNATURE
**IN WITNESS WHEREOF**, the Parties have executed this Agreement as of the Effective Date.
**[Party 1 Name]**
By: _________________________________
Name: _______________________________
Title: ________________________________
Date: ________________________________
**[Party 2 Name]**
By: _________________________________
Name: _______________________________
Title: ________________________________
Date: ________________________________
---
## Key Terms Quick Reference
| Term | Value |
|---|---|
| **NDA Type** | [Mutual/One-Way] |
| **Effective Date** | [to be filled in] |
| **Term** | [X] years from Effective Date |
| **Survival Period** | [X] years after termination |
| **Governing Law** | [jurisdiction] |
| **Dispute Resolution** | [method] |
| **Notice Method** | [method] |
Important Guidelines
- Generate legally coherent, professionally drafted language. This should read like a document prepared by a law firm, not a template with blanks.
- The definition of Confidential Information must be tailored to the user's specific situation. A technology NDA should specifically reference source code, algorithms, and technical specifications. A business partnership NDA should reference financial data, customer lists, and strategic plans.
- Always include the standard exclusions. These are essential for enforceability.
- The compelled disclosure carve-out (required by law) must include a notice obligation -- the Receiving Party must notify the Disclosing Party before disclosing, to the extent legally permitted, so the Disclosing Party can seek a protective order.
- Plain English annotations must be genuinely helpful, not just restatements in slightly simpler language. Explain the practical impact.
- If the user does not specify a jurisdiction, ask before generating. Governing law significantly affects enforceability.
- For employee NDAs, include provisions specific to the employment context: acknowledgment that the NDA does not guarantee employment, clarification of at-will status if applicable, and reasonable scope limitations that improve enforceability.
Du fichier au premier essai
Le téléchargement contient exactement le contenu affiché sur cette fiche. Cette copie peut différer de la dernière version du dépôt source.
Consulter la source et ses fichiers annexesCe téléchargement contient uniquement SKILL.md. Les scripts, références, modèles et dépendances éventuels ne sont pas inclus. Récupérez les fichiers nécessaires depuis la source en conservant leur arborescence avant de poursuivre.
1. Télécharger le fichier
Télécharger SKILL.mdDepuis la racine d’un projet de test, enregistrez le fichier sous .skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md, ou utilisez la commande suivante. Ce dossier sert à examiner la skill avant son installation.
Commande pour macOS/Linux ou WSL : un shell POSIX et curl sont nécessaires. Sous Windows sans WSL, utilisez le bouton de téléchargement et créez le dossier manuellement.
mkdir -p '.skill-downloads/custom-nda-generator-mrwaka3s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/custom-nda-generator-mrwaka3s/download' --output '.skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md.part' && mv '.skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md.part' '.skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md'2. Vérifier les prérequis
Lisez SKILL.md avant de l’utiliser. Si le fichier cite des scripts ou services externes, examinez-les et préparez les accès nécessaires dans votre environnement de test.
Aucune section de prérequis reconnue dans ce fichier. Cela ne signifie pas qu’il est autonome : les bibliothèques, outils et accès peuvent être cités ailleurs dans le contenu ou dans le dépôt source.
Les plateformes de la fiche sont des indications du catalogue. Les chemins ci-dessous suivent la documentation des outils ; ils ne prouvent pas que cette skill y a été exécutée. Aucune version minimale de ces outils n’est attestée pour cette fiche.
3. Charger la skill
Après vérification, copiez le dossier complet dans le projet avec l’une des commandes ci-dessous, puis ouvrez une nouvelle session de l’outil. La commande s’arrête si un dossier du même nom existe déjà : comparez les fichiers avant de le remplacer.
Claude Code
test -f '.skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md' && test -s '.skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/custom-nda-generator' && cp -R '.skill-downloads/custom-nda-generator-mrwaka3s' '.claude/skills/custom-nda-generator'OpenSkills
OpenSkills doit déjà être installé. La procédure locale install/read est contrôlée avec OpenSkills 1.5.0, qui exige Node.js ≥ 20.6.0. Aucun slug du catalogue n’est résolu automatiquement.
Installation officielle d’OpenSkillsopenskills install './.skill-downloads/custom-nda-generator-mrwaka3s'openskills read 'custom-nda-generator-mrwaka3s'La lecture doit afficher le contenu du fichier installé et son dossier de base. Elle ne lance ni la skill ni ses dépendances.
Pour un agent qui lit AGENTS.md, synchronisez ensuite l’index. Cette commande modifie AGENTS.md : relisez le diff avant de l’utiliser.
openskills syncMode manuel ou autre outil : joignez SKILL.md à une conversation, ou ouvrez-le dans un agent capable de lire les fichiers. Ajoutez les ressources annexes nécessaires. Il n’existe pas de dossier universel reconnu par tous les outils.
4. Faire un premier essai
Utilisez une entrée courte et fictive : un endpoint d’API, un petit document ou un brief d’interface. Dans une nouvelle conversation, joignez le fichier ou donnez son chemin à l’agent, puis adaptez cette demande :
Lis .skill-downloads/custom-nda-generator-mrwaka3s/SKILL.md et applique ses instructions à cet exemple : [décrire une entrée de test]. Indique les fichiers, dépendances ou accès qui manquent. Produis le résultat demandé par la skill sans inventer de données ni exécuter de script non examiné.Résultat attendu : une sortie correspondant aux instructions de la skill, ou une liste précise des prérequis manquants. Une simple confirmation de lecture ne valide pas le premier usage. Si une ressource externe est indisponible, ce parcours reste à tester.
Fragments d'écriture
Contenu
Extrayez des fragments d'écriture bruts via un entretien intensif, sans imposer de structure. Capturez idées, citations et mots porteurs pour une utilisation ultérieure.
Rédaction UI et audit
Contenu
Rédigez ou auditez les textes d'interface (boutons, erreurs, états vides, infobulles) dans le monorepo, en suivant la source de vérité du design system.
Extraction MIDI/score
Contenu
Extrait le MIDI ou la partition d'une production musicale existante via l'outil MCP CogMusic et confirme la disponibilité du fichier.