agentleFS
genspark-aigenspark-ai/genoffice/skills/recommended/nda-drafter/SKILL.md

nda-drafter

Skill11k starsChanged 3 months agoApache-2.0View on GitHub

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

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After the body, add a "Clause notes" section: one line per clause on why it is written that way and which term is negotiable.

    line 21
  2. Distinctive:

    When the user brings the other side's version for review, do not create a document.

    line 23
  3. Distinctive:

    Do not cite specific statute numbers or write "under Article N of such-and-such act".

    line 28
  4. Distinctive:

    Write the agreement term and the confidentiality period separately: the agreement can be terminated, the confidentiality obligation …

    line 31
  5. Distinctive:

    When the recipient is an individual (an adviser, a candidate), drop the affiliate onward-disclosure clause and replace it with personal …

    line 32
  6. Distinctive:

    Document: level-1 heading is the agreement name, body clauses numbered "Article N", clause notes and risk points each under their own …

    line 36
  7. Distinctive:

    After delivering, state in one sentence that the draft is for reference, not legal advice, and should be reviewed by a licensed lawyer …

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about genspark-ai/genoffice

The biggest 5 of 66 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 66

Talked about on GitHub, YouTube, Bluesky, the web and Hacker News (66 times).

On GitHub · 31

26 more on GitHub

On YouTube · 23

18 more on YouTube

On Bluesky · 5

On the web · 4

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.