NDA / Contract Draft is a Claude AI skill — Produces a deal-specific draft framework covering confidentiality scope, term, jurisdiction flags, and mutual vs. unilateral structure. Starting point for review, not a DIY replacement for legal counsel.
A founder takes a partnership meeting. The other party asks for an NDA before sharing their roadmap. The founder downloads the first free template that appears in a search, swaps the company names, sends it over. Everyone signs. Six months later, when the relationship breaks down and information ends up somewhere it shouldn't, the founder discovers that the template's definition of "confidential information" was so broad it was unenforceable — and the jurisdiction clause defaulted to a state neither party operates in.
The document looked right. It had the structure, the whereas clauses, the signature block. What it didn't have was the specific language that would have made it usable in an actual dispute. Generic templates are written to look complete. A draft built from your deal's actual parameters is written to work.
Most founders, freelancers, and small business operators don't need a lawyer for every NDA or simple service contract. They need a well-structured starting point that covers the right provisions for their specific situation — something they can review, adjust, and sign with confidence rather than hope.
Why Generic Templates Leave You Exposed
The problem with free NDA templates isn't that they're fraudulent — it's that they're written for nobody in particular, which means they're not quite right for anybody. A mutual NDA for a two-way vendor relationship needs different language than a unilateral NDA for a job candidate receiving proprietary information. An NDA protecting software architecture needs a different confidential information definition than one protecting a client list. Generic templates can't know which of these you need, so they pick a middle path that often serves neither.
Three provisions account for the majority of NDA disputes: the definition of confidential information (too narrow and it doesn't cover what you care about; too broad and it's unenforceable), the term clause (how long confidentiality obligations last after the agreement ends), and the jurisdiction clause (which law governs and where disputes are heard). Free templates routinely leave all three as boilerplate — which means they're technically present but practically useless.
A template NDA gives you a document that will pass a quick glance. A deal-specific draft gives you a document that will hold up when it matters — because the provisions reflect your actual situation, not a hypothetical average one.
Vanilla Claude has the same limitation. Ask it to draft an NDA and it will produce something structurally sound, written in appropriate legal register, and missing the deal-specific calibration that determines whether the document does the job. It doesn't know whether the relationship is mutual or unilateral, what the confidential information actually is, how long the term should run, or which jurisdiction flags apply to your parties. Without those inputs, it defaults to generic — same as the free template, just formatted more nicely.
That gap is exactly what the NDA / Contract Draft skill for Claude was built to close.
What Deal-Specific Calibration Actually Changes
Before the NovaKit NDA / Contract Draft skill produces a single clause, it interviews you on the parameters that determine what the document needs to do. Mutual or unilateral agreement. The nature of the confidential information — IP, client data, financial projections, technical architecture, or a combination. The relationship type: potential partnership, contractor engagement, employment, investor conversation, or vendor due diligence. The intended duration of confidentiality obligations. And the jurisdiction of both parties, which determines which law governs and whether specific statutory language applies.
Those five inputs produce a draft that is structurally different from a generic template — not cosmetically different. The confidential information definition is scoped to what you're actually protecting. The term is appropriate to the relationship type. The jurisdiction clause reflects the actual parties rather than a legal fiction. The mutual vs. unilateral structure matches the deal.
The difference between a template and a calibrated draft isn't formatting. It's whether the provisions reflect the deal you're actually doing.
The skill also flags jurisdiction-specific considerations — areas where the law governing your parties may require specific language or where a generic clause is likely to create ambiguity. These are surfaced as review notes in the output, not buried in boilerplate, so you know exactly where to focus attention before signing.
What the NDA / Contract Draft Skill Produces
The skill's three-question interview covers relationship type, confidential information scope, and jurisdiction of both parties. From those inputs:
Template Output vs Calibrated Draft Output
Same scenario — a founder sharing technical architecture with a prospective integration partner — run through a standard free NDA template versus the NDA / Contract Draft skill. The difference shows up most clearly in the confidential information definition, which is where most template NDAs quietly fail.
Jurisdiction: State of Delaware. Term: 2 years from date of disclosure.
📍 Review note: Both parties are UK-incorporated — consider whether English law governing clause better serves dispute resolution costs vs. Delaware default. Term set to 3 years given IP sensitivity of disclosed material; adjust downward if partnership timeline is shorter.
The template definition is technically present and will survive a quick read. The calibrated draft defines exactly what's being protected, builds in the standard carve-outs that prevent overreach, and surfaces the two decisions — governing law and term length — that a founder in this situation actually needs to think about. One gets signed without being read closely. The other gets reviewed and understood before execution.
Who Gets the Most from This Skill
Founders and operators who need NDAs regularly — partnership conversations, contractor engagements, investor due diligence — and want a properly structured starting point rather than a free template. Freelancers negotiating service contracts where scope, IP ownership, and payment terms need to be clearly defined. Small business owners who can't justify hourly legal fees for every standard agreement but want to arrive at a lawyer's desk with a well-formed draft rather than a blank page.
The skill is not the right tool for high-stakes agreements where the cost of getting it wrong significantly exceeds the cost of professional review — an M&A NDA, a co-founder agreement, or a contract with cross-border employment implications. For those, it can still accelerate the drafting process and reduce the time a lawyer spends on structure rather than substance. But the final document warrants qualified review.
For everything in the middle — the NDAs that need to exist and be taken seriously, but don't warrant $800 in legal fees — it gives you a document that reflects your actual deal rather than a hypothetical average one.
The Output You Walk Away With
A complete NDA or simple contract draft: parties and recitals, a scoped confidential information definition, obligations of the receiving party, standard exclusions, term and survival clause, jurisdiction and governing law with flags, and a signature block — all calibrated to your five inputs. Inline review annotations on the provisions most likely to need adjustment. The full document is ready to paste into a Word file, share with the other party, or bring to a lawyer for a targeted review of the flagged sections rather than a full-document redraft.
Most people use it to move faster on agreements that have been sitting in a "need to sort this out" folder for two weeks, because starting from a structured calibrated draft is a different task — and a shorter one — than trying to adapt a generic template that wasn't written for your situation in the first place.
The NDA that holds is the one whose provisions actually match the deal. Everything else is a document that looks right until the moment it needs to work.
The next piece most people tackle from here is terms and privacy policy that reflect your actual data practices. If you're working across the full Legal & Biz workflow, the Legal & Biz bundle covers everything in one place.
Put this to work: the NDA / Contract Draft skill for Claude turns everything above into one guided workflow you run in a normal Claude chat. Not ready to buy? Start with a free Claude skill and see how it works first.
Related reading: The Free NDA Template Problem: What Standard Documents Leave Out