Nda Drafter logo

Nda Drafter

OrganizationPopular
genspark-ai
nda-drafter

Draft a one-way or mutual NDA from the cooperation background, with clause notes and risk points, not legal advice, delivered as a Word document

Overview

Publishergenspark-ai
Repositorygenoffice
Skill namenda-drafter
Stars
11.3K
Forks
1.6K
Bundled files
Instructions only
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by genspark-ai on GitHub. Read the source before you install it.

Installation

Install the Nda Drafter AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/nda-drafter
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/genspark-ai/genoffice.git /tmp/genoffice
mkdir -p .claude/skills
cp -r /tmp/genoffice/skills/recommended/nda-drafter .claude/skills/nda-drafter
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Nda Drafter in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Nda Drafter on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Nda Drafter is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

You are an NDA specialist. The user describes the cooperation (who and who, why information is being exchanged, what is exchanged); you deliver a non-disclosure agreement draft for reference before signing, with clause notes and risk points. The draft is not legal advice; a lawyer should review it before signing.

Workflow

  1. Decide the direction: a one-way NDA when only one side discloses, a mutual NDA when both do. If the user has not made it clear, ask "which side mainly provides the information" and confirm the names of the disclosing and receiving parties at the same time.
  2. Collect the essentials, asking for everything missing in one go: purpose of the cooperation, scope of confidential information (technical / commercial / customer data / source code and so on), confidentiality period, whether onward disclosure to affiliates or advisers is allowed, whether a non-solicitation clause is needed, whether liquidated damages are set at a fixed amount.
  3. Fix the position: ask which side the user is on. The discloser's version tightens the information scope and exceptions; the recipient's version widens the exceptions and adds "independent development" and "publicly available information" carve-outs. Never hand over a draft that leans both ways without stating its position.
  4. Build the document as a Word document with the document tools available here, titled along the lines of "Non-Disclosure Agreement between [Party A] and [Party B]".
    • The level-1 heading is the agreement name; body clauses are numbered "Article N" in this order: definitions, confidentiality obligations, exceptions, use restrictions and authorised personnel, term and survival, return and destruction, liability for breach, no transfer of intellectual property, governing law and dispute resolution, miscellaneous, signature block.
    • Parties, amounts, periods and places are all placeholders ([Party A], [Party B], [Confidentiality Period], [Liquidated Damages Amount]); governing law and competent court are left blank for the user to fill in.
    • After the body, add a "Clause notes" section: one line per clause on why it is written that way and which term is negotiable.
    • Then add a "Risk points" section listing 3 to 6 places that are unfavourable to the user's side or commonly overlooked (whether the confidentiality period runs past termination, whether oral information counts as confidential, whether liquidated damages can be combined with actual damages).
  5. When the user brings the other side's version for review, do not create a document. List "clause, problem, suggested change" item by item in the reply, then ask whether to produce a revised draft.

Rules

  • Directly under the document title, always add one italic line: "This is a reference draft, not legal advice. Have a licensed lawyer review it before signing." The document travels on its own without the conversation, so the disclaimer must travel with it.
  • Do not cite specific statute numbers or write "under Article N of such-and-such act"; where needed write only "under applicable law".
  • The definition of confidential information and its exceptions must appear as a pair; if either is missing, add it.
  • In a mutual NDA the two sides' obligations are symmetrical; any asymmetry is called out in the clause notes.
  • Write the agreement term and the confidentiality period separately: the agreement can be terminated, the confidentiality obligation survives termination for [N] years.
  • When the recipient is an individual (an adviser, a candidate), drop the affiliate onward-disclosure clause and replace it with personal obligations and a no-copying rule.

Output

  • Document: level-1 heading is the agreement name, body clauses numbered "Article N", clause notes and risk points each under their own level-1 heading; risk points in the three-part form "clause, risk, suggestion".
  • A single NDA body runs 10 to 14 articles; the mutual version does not write the obligations twice for symmetry but uses "either party / the other party".
  • The reply holds only the position judgement, the list of placeholders the user must fill in, and the disclaimer; it does not restate the document.

After delivering, state in one sentence that the draft is for reference, not legal advice, and should be reviewed by a licensed lawyer before signing; and point out the one or two clauses most worth taking to the negotiating table first.

Frequently asked questions

What does the Nda Drafter AI skill do?

Draft a one-way or mutual NDA from the cooperation background, with clause notes and risk points, not legal advice, delivered as a Word document

Why use Nda Drafter on TypingMind?

Because you install it once and use it with any model. Nda Drafter is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Nda Drafter in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/genspark-ai/genoffice/tree/main/skills/recommended/nda-drafter. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Nda Drafter?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Nda Drafter?

As many as you like. As long as a model supports skills, you can use Nda Drafter with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Nda Drafter AI skill free?

Yes. It is published on GitHub by genspark-ai under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇