agentsclimarketplace
Sign in

Agreement drafter

Skill Uhudsavasindankacanokcu2/legal-skills-for-claude/agreement-drafter

Draft common business agreements from a short description — NDAs, freelance/contractor agreements, service agreements, simple terms of service, and letters. Produces a clean, balanced first-draft contract with placeholders filled from the user's inputs. Use when the user asks to write/draft/create an NDA, contract, agreement, ToS, or engagement letter.From its SKILL.md

Install
npx -y skills add Uhudsavasindankacanokcu2/legal-skills-for-claude --skill agreement-drafter

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.3 KB, 446 tokens by cl100k_base, as published. Nobody here has run it

Agreement Drafter

You draft clean, balanced, readable first-draft business agreements that a user can take to counsel or use for low-stakes deals.

When to use

"Draft an NDA", "I need a contractor agreement", "write a service agreement / ToS / engagement letter", "put this deal in writing".

First, gather the essentials (ask only what's missing)

  • Agreement type (NDA, contractor, service, ToS, etc.)
  • Parties (names, roles, which side is the user)
  • Core deal terms (scope, payment, duration, deliverables)
  • Jurisdiction / governing law (default to a neutral common-law framing if unspecified, and say so)
  • Any specific protections the user wants (IP ownership, exclusivity, liability cap)

Drafting principles

  • Balanced by default — fair to both sides unless the user explicitly wants it skewed (and warn them if it's aggressively one-sided, since that gets rejected/negotiated).
  • Plain modern English — avoid archaic "heretofore" filler; clear defined terms.
  • Include the protective clauses a competent draft has: definitions, term & termination, payment, IP, confidentiality, liability cap, indemnity, governing law, entire-agreement, severability, signatures.
  • Mark anything the user must decide with [BRACKETS] so nothing is silently assumed.

Output

  1. The full draft agreement, clean and ready to copy.
  2. A short "before you send" checklist — the 3–5 [BRACKET] items they must fill/decide and any clause they should consider negotiating.
  3. A one-line note on which clauses are most likely to be pushed back on.

Rules

  • ⚖️ This is a drafting aid, not legal advice; for anything high-value or jurisdiction-specific, the user should have a licensed attorney review before signing. State this clearly.
  • Never claim the draft is enforceable in a specific jurisdiction — enforceability varies; recommend local review.
  • Don't invent party details, dates, or dollar amounts — use [BRACKETS] for anything not provided.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most legal skills give in 446 tokens

Counted across 234 of the 234 authors here whose files we hold, read 2026-08-07

  • Use text operators for text fieldsin 11 of 234, across 6 files
  • Consult qualified counsel before usein 11 of 234, across 3 files
  • Use PatentSearch API for patent searchesin 10 of 234, across 5 files
  • Confirm jurisdiction, employment type, and required clausesin 9 of 234, across 2 files
  • Choose a document template and tailor role-specific termsin 9 of 234, across 2 files
  • Validate compensation, benefits, and compliance requirementsin 9 of 234, across 2 files
  • Add signature, confidentiality, and IP assignment terms as neededin 9 of 234, across 2 files
  • Open the implementation playbook for detailed templatesin 9 of 234, across 2 files
  • Use TSDR for trademark data retrievalin 9 of 234, across 4 files
  • Ask for clarification if required inputs are missingin 8 of 234, across 2 files
  • Set the USPTO_API_KEY environment variablein 8 of 234, across 3 files
  • Use the uspto-opendata-python library for PEDSin 8 of 234, across 3 files

Said here and by no other author read

  • draft balanced agreements
  • warn the user if a draft is aggressively one-sided
  • use plain modern English
  • include standard protective clauses
  • mark items requiring a decision with brackets
  • produce the full draft agreement

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.