The AI Negotiator skill for Claude
You describe the negotiation that is coming up and you get back a preparation built on the Harvard Negotiation Method. Positions separated from interests, your own BATNA honestly rated as strong, reasonable or weak, the ZOPA in numbers with the point where you walk away, at least five win-win options that are not about the price, and an opening line you can say out loud. What the skill does not know, it marks as an assumption. It does not advise bluffing.
the instructions above come from the zip on this page · SKILL.md is 15,618 bytes
Situation in, strategy out
reg. N.001This is the worked example from the SKILL.md itself, shown here in shortened form: your biggest client wants to renew but is asking for a twenty per cent discount. Watch what happens in step three. It does not tell you that you are in a strong position, it says exactly the opposite, and that is why the rest of the strategy looks the way it does.
What the AI Negotiator is
The AI Negotiator is a free skill from our skill library. A skill is an instruction file, SKILL.md, that gives an AI assistant a fixed method for a task. No software to install, no subscription, no link to your CRM: a 2,452-word text file that tells Claude how to prepare a negotiation using the Harvard Negotiation Method, what information it needs to ask for, in what order the strategy is built, and what it must never make up itself.
You download the zip at the top of this page, put it in your Claude environment, and from that moment Claude prepares conversations following this logic. What a SKILL.md actually is, and why a text file steers an AI's behaviour, is explained in what Claude skills are NL.
You probably recognise the problem the skill solves. A conversation about money is coming up, you roughly know what you want, and beyond that you do not really prepare because you do not know how you would. Then the conversation starts, the other side opens with a number, and from that point it is only ever about that number. You nudge it up, they nudge it down, and whoever holds out longest wins. That is called positional bargaining, and the method this skill rests on is explicitly an answer to it.
It is written for people who negotiate without it being their profession: freelancers and agencies who have to defend their rate, business owners renewing a supplier contract, employees having a salary conversation, anyone with an expiring contract on their desk. It is part of the skill library NL we make available for free through the AI and automation service, with no account and no sales email afterwards.
One thing you should know upfront: the skill does not negotiate for you. It prepares you for a conversation you have yourself. It delivers a strategy, not a pep talk, it does not invent a counteroffer you have never heard, and it does not promise that a particular outcome will be reached. What it does do is make explicit the two things most people leave implicit: what you do if there is no deal, and where the line sits above which a deal is better than no deal.
Why negotiations get stuck on money
When a conversation gets stuck on price, price is rarely the actual problem. The problem is that there is only one variable on the table. As soon as there is only one number to divide, every euro one side wins is a euro the other side loses, and then there is no solution left, only an outcome.
The position gets mistaken for the interest. The position is what someone asks for. The interest is why they ask for it. Behind fifteen per cent discount, according to the file, there is often a fixed internal budget, a buyer who has to justify their decisions, or a cash flow that only frees up in two months. On the position you can only say yes or no. On the interest you can think up five different answers, and three of those cost you nothing.
The BATNA is never spelled out. Your best alternative if this deal falls through determines your negotiating position, not your arguments. And it is not what you hope, it is what you would actually do. Two outstanding proposals are not two clients. As long as you have not said that out loud, you behave at the table as if your alternative is stronger than it is, and the other side notices that before you do.
Brainstorming and deciding happen at the same time. The method says: first think up options that leave both sides better off, and only then choose. Do those two things at once and you shoot down every idea before it is fully formed, leaving you with exactly the one variable you started with.
There is no objective standard. Without an external standard the outcome is decided by whoever pushes hardest, and nobody walks away from that feeling good. Market prices, benchmarks, third-party quotes, an index or a valuation move the conversation away from willpower and onto facts.
Every concession is free. This is the mistake that runs deepest. You give something away to create movement, you ask for nothing in return, and the only thing you learn is that there is more to be had. In its review mode the skill therefore flags every concession made without a counter-ask, and it never proposes one itself either.
In diff form, with lines from the skill's own example: what comes out and what replaces it.
Your power comes from your alternative
reg. N.002BATNA stands for Best Alternative To a Negotiated Agreement: what you will actually do if this deal falls through. It is the starting point of the whole preparation, because your BATNA determines your power, not your powers of persuasion. The BATNA analysis from the example, with both sides side by side. The counterparty's side is estimated too, but with the word assumption attached, because that side you cannot actually know.
What is actually in the SKILL.md
A skill is only as good as its instructions, so we simply describe them here. The file opens with a frontmatter that states when Claude should pick up the skill. Not only for the obvious terms like negotiating, BATNA, ZOPA, price negotiation and salary negotiation, but also for laments: they want twenty per cent off my price, I do not dare defend my rate, the conversation is stuck on money, I do not want to ruin the relationship, I always give in too fast, I do not know whether I should walk away. The frontmatter also names when it should not fire: for legal advice on contract clauses, for labour disputes with a formal procedure, and for mediation between two parties where you do not take a side.
Then comes the theory section, with the four pillars of the method spelled out. Separate the person from the problem, so tough on substance and soft on the relationship. Focus on interests, not positions. Think up options that leave both sides better off before you choose, and pull brainstorming and deciding apart. And use objective criteria, so the outcome is not decided by whoever pushes hardest. Alongside that, BATNA and ZOPA appear as the two concepts that steer the entire preparation, with the emphasis that a BATNA is what you actually do, not what you hope for.
The core is a list of seven fixed actions. It summarises the situation in a short diagnosis and states whether this is mainly distributive or integrative. It splits the positions from the interests for both parties. It makes your BATNA explicit, including an honest verdict of strong, reasonable or weak, plus at least one way to strengthen it. It estimates the counterparty's BATNA, with the assumption behind that estimate clearly marked.
It determines the ZOPA in concrete numbers or conditions and names the walk-away point. It delivers at least five win-win options that are not about price, such as payment term, contract length, volume, scope, exclusivity, reference rights or a start date. And it writes an opening line that names the counterparty's interest out loud, plus answers to the two or three most likely objections.
Before anything gets worked out, the skill runs through a mandatory input checklist: what is being negotiated and what is currently on the table, who the counterparty is and what role that person has within their own organisation, your goal in a number or a concrete condition, what you actually do if the deal falls through, your floor and whether that is yours or someone else's in your business, what you already know about the pressure the counterparty is under, and whether the relationship continues after this deal or is a one-off.
It asks for everything missing all at once and then stops asking. If you do not know something, it proceeds with a marked assumption instead of continuing to press for an answer.
The output has a fixed structure of eight blocks, always in the same order: situation diagnosis, positions and interests per party, the BATNA analysis, ZOPA and walk away, five or more win-win options each stating what it costs you and which interest of the other side it addresses, objective criteria, an opening line with objections, and finally a source and accountability section stating which model was used and which assumptions the analysis rests on.
Here too, remarkably many rules are about language. The file requires the you-form, forbids dashes in running text, forbids rule-of-three lists, and keeps a list of AI words that may not be used. There is one more rule specific to this skill that makes the difference: conversation lines are written as spoken language, because you need to be able to say them out loud without cringing. You can hear that in the opening line in FIG.01, which sounds like someone talking, not someone reading aloud.
Finally, the file has a separate mode for reviewing existing work. Hand it a proposal, an email exchange or a planned approach, and you get five things back: a diagnosis of where the weakness lies, a marking per passage placing POSITION or INTEREST after each sentence so you can see how positional your writing is, a list of what is missing from the checklist, a concession analysis flagging every concession made without a counter-ask, and a rewritten version in the standard output structure. If you want to learn how to set up an instruction file like this yourself, writing a SKILL.md NL explains how that structure works.
The zone where a deal exists
reg. N.003ZOPA stands for Zone Of Possible Agreement: the space between your floor and the counterparty's ceiling. If there is no overlap, no deal is the right result. The zone from the same example, drawn to scale. The client's opening bid sits below your floor, so inside the red zone. That is not a reason to walk away, it is the reason five other variables need to come into play.
The theory the skill rests on
Negotiating is one of the few business skills with a clear canon, and the SKILL.md names its sources by name. That is deliberate: it means you can read them yourself and decide whether you agree.
The method comes from Getting to Yes, 1981. Roger Fisher and William Ury described the work of the Harvard Negotiation Project in that book, in later editions together with Bruce Patton. The method is also known as principled negotiation and is explicitly meant as an answer to positional bargaining: two parties inching towards each other from an opening bid, where the outcome is decided mainly by whoever holds out longest.
BATNA comes from the same source. The term is generally credited to the Harvard Negotiation Project and is by now the most cited piece of negotiation vocabulary there is. The core is simpler than the acronym suggests: your power comes not from your arguments but from what you will do if the conversation fails. Whoever improves that alternative first has to perform less well at the table.
Getting Past No covers the difficult counterparty. Ury wrote that follow-up in 1991, for situations where the other side attacks, blocks or uses tricks. As an addition, it comes in if the other side threatens to walk away or keeps adding new demands after you have given in: it adds a block on naming that behaviour without answering it.
3-D Negotiation widens the field of play. David Lax and James Sebenius described in 2006 that the table is only one of three dimensions. Alongside what you say at the table, the setup of the deal itself and the question of who you invite to the table also matter. If a conversation gets stuck on the table itself, it reaches for this: look at who else should be sitting there, or how you could carve up the deal differently.
Never Split the Difference supplies the tone. Chris Voss described tactical empathy, labelling and calibrated questions in 2016, based on his work as a hostage negotiator. For emotionally charged conversations it draws on this, for example a salary conversation or a conflict with a long-running client, with labels like it sounds like this is mainly about timing.
Distributive versus integrative. Finally, the file uses the distinction between dividing a fixed pie and growing it. That distinction sits in step 1 of the skill for good reason: it determines the whole approach. In a one-off transaction with no follow-up, such as selling a used piece of business equipment, the anchor price matters more than the interest analysis. In a relationship that continues, it is exactly the other way round.
Even without installing the skill, you can use these principles to prepare your next conversation better: write down what you do if there is no deal, find an objective standard to go with it, and make sure there is more than one variable on the table before you sit down.
What the skill refuses
reg. N.004The SKILL.md contains a list of six things the skill never does, and in negotiating that list is the difference between advice and damage. A made-up market price that gets challenged at the table costs you more than the amount it was about. In the conversation these rules play out like this: each one is a request you could make, with the response the skill gives according to its own instructions.
Installing in Claude Code, Claude.ai or Codex
The zip is 6.5 KB and contains a folder, ai-onderhandelaar, with the SKILL.md inside. Installing means putting the file in the right place, and that place differs per environment. SKILL.md has been an open standard since December 2025, so the same skill also works in Codex, Cursor and Gemini CLI. So you are not downloading a Claude file but a working instruction any modern AI assistant can read.
- Unzip it into
~/.claude/skills/(or.claude/skills/in your project). - Claude then recognises the skill automatically as soon as you start talking about a counteroffer, a discount request or a contract renewal.
- You can also call it directly, with
/ai-onderhandelaar.
- Go to Customize and then Skills.
- Upload the zip there as a skill.
- Or paste the contents of SKILL.md into the project instructions of a Project.
- Open
AGENTS.mdin your repo. - Paste the contents of SKILL.md into it, or place SKILL.md next to it as a separate file and refer to it from
AGENTS.md. - Codex reads that along with every session.
After that, using it is simple: describe the negotiation in plain sentences, as in FIG.01. What is on the table, who the counterparty is and what role that person has, your goal in a number, what you do if it falls through, your floor, and whether the relationship continues afterwards. If you do not know something, just say so: the skill proceeds with a marked assumption instead of continuing to press for an answer. If you get stuck on the installation itself, the full route is in installing Claude skills NL. Want your team to learn how to set this kind of work up? That is the subject of our AI training NL.
When to use it, and when not to
It is at its strongest for business deals where the relationship continues afterwards: contract renewals, rate increases, procurement conversations, partnerships. That is where principled negotiation pays off most, because there is nothing to gain from winning a conversation you will have again next year with someone who still remembers it.
The file itself names, per situation, which addition applies. When a counterparty attacks, threatens to walk away or keeps adding new demands after you have given in, Getting Past No comes into play, with a block on naming that behaviour without answering it. If the deal gets stuck on the table itself, it switches to 3-D Negotiation: look at who else should be sitting at the table, or how you could carve up the deal differently.
If the conversation is emotionally charged, for example a salary conversation or a conflict with a long-running client, the tactical empathy from Never Split the Difference comes into play. And for a one-off transaction with no follow-up, it switches back to purely distributive negotiating, because then the anchor price matters more than the interest analysis.
There are also situations where you are better off leaving it be, and those are stated in the file itself. Legal advice on contract clauses is one: preparing for a conversation is a different thing from writing down what becomes binding, and for that you need a lawyer. Labour disputes with a formal legal procedure are the second. And mediation between two parties where you do not take a side is the third: this skill by definition takes your side, so it is no good as a neutral mediator.
The biggest limitation is a different one, and it is not technical. It prepares the negotiation, it does not conduct it. You are the one sitting at the table, and all sorts of things happen there that no preparation catches: the other side names a number you did not expect, it turns out someone else has a say who you did not know about, or the conversation suddenly turns to something completely different. What the preparation gives you is that in those moments you know where your line sits and which variables you can still use, and that is exactly what disappears first under pressure.
One more honest limit: the quality of the analysis depends entirely on the quality of your description. If you do not mention that your contact does not decide alone, the skill will not account for that. If you name a floor that actually belongs to your business partner, it builds a strategy on a number that is not yours. The checklist asks about this on purpose, and that is not a formality but exactly where most preparations quietly go wrong.
Run it yourself, or have it run for you
reg. N.005This skill is the free do-it-yourself version of work we also deliver as a service. It stays complete and with no catches, but be clear about what a skill is: it teaches your AI how to do something, while every new session starts empty. It is not the engine and not the memory. You prompt, you supply your rates, your floors and your client history again every time, you check the result. Anyone who wants that differently has two next steps: hand off the engine, or sort out the memory.
where you are now The skill: you are the engine You run the AI Negotiator yourself in Claude, Codex or Cursor. Costs nothing, works today, and you keep full control: no trial period, no locked-off parts. The limit is your own time: it only happens when you describe a conversation and ask for it.
have it prepared The AI employee: it is ready without you having to prompt Exactly this work, but as a service: the Sales Employee prepares prospect research and commercial conversations without you having to sit behind Claude for it. Control stays with you, because output remains a draft until a human gives approval. We deliver this through Mansotti, the company TheSEO trades under, which alongside the Sales Employee also builds a Quoting Employee (enquiries and quotes) and a Reporting Employee (weekly and monthly reports). Read what an AI employee is and does.
everything from one source Jarvis: all your AIs work from the same company knowledge The skill teaches the AI, the brain is where the memory lives. Want all your AIs to work from the same company knowledge: that is Jarvis, the organisation brain. It connects ChatGPT, Claude, Codex and your people to the same projects, core knowledge and decisions, so your next AI session does not start from zero. Jarvis selects context, delegates work and only keeps what has been approved: client knowledge stays isolated and every step leaves an auditable trail. This particular skill benefits from that directly, because you no longer need to look up your floors and earlier agreements for every conversation. What that delivers in practice, from the plans to your first week, you can read at Jarvis itself.
What Jarvis actually delivers
reg. N.006Step 3 deserves more than a paragraph, because this is the difference between a smart chat and a system you can build on. Jarvis is the organisation brain: it remembers what your AIs need to know, distributes the work and keeps track of what happened. With negotiating that is extra concrete, because the data the skill needs is exactly the data you now dig up again every time: your floors, what you agreed with this client last year, and which concession you made then.
We have been running on this system ourselves for months. Every agent session, every task and every decision gets logged in it and can be read back. A new session therefore does not start blank: it first pulls up the recorded decisions, the running projects and the latest changes, and carries on from where the previous one stopped. What was agreed with a supplier last time is still there, even if nobody remembers it any more. We are not describing a promise here but the way we work ourselves, every day.
See the four plans at jarvis/prijzen NL. Through the waiting list NL you only pass on your preferred plan, without obligation. That does not create an account, an order or a payment obligation. We discuss business custom work first.
The skills around it
reg. N.007A negotiation never stands alone: a conversation and a quote came before it, and an agreement follows from it. These skills from the same library each cover a different part of that chain.
Before the bid
the run-upThere is little to negotiate if the groundwork is not right. These three do that groundwork.
SPIN Sales ConversationThe questioning technique that surfaces the cost of the problem before money is discussed.SKILL NL Intake SummaryTurns the conversation into a report where the client's interests are already separated from their wishes.SKILL AI Quote WriterThe document that comes before the negotiation, with three options instead of a bare figure.SKILLAround the amount
the priceThe negotiator works with the floor you supply. This skill sets that floor.
Pricing Strategy CoachDetermines what your work is worth based on value instead of hours, and so where your floor should sit.SKILL NL Case Study GeneratorTurns a completed project into the proof you can use as an objective criterion at the table.SKILLAround the conversation
the languageNegotiating is a conversation. These three cover what you say and why it works.
Cialdini PersuasionThe psychology behind persuading, with the same honesty rule: no scarcity that is not real.SKILL Persuasiveness AnalystTests whether your argument holds up, before you use it at the table.SKILL Nonviolent Communication CoachFor conversations where tension is high and the relationship needs to stay intact.SKILLLook further
the contextWhere this skill comes from and what else is out there.
The whole skill libraryAll 100 free skills at a glance, sorted by topic.HUB NL AI and automationThe service behind it: from loose skills to working automation in your business.SRV What Claude skills areThe basics: what a SKILL.md is and why a text file steers an AI's behaviour.DOC NL Knowledge baseArticles on SEO, AI and online visibility, searchable.DOCFrequently asked questions
What does the AI Negotiator skill cost?
Nothing. The skill is free, falls under the MIT licence, and you do not need to create an account or leave an email address. You download a 6.5 KB zip containing a folder and a single file, SKILL.md of 2,452 words, and that is the complete skill. There is no paid version and no sales email follows.
Does this skill also work in Codex, Cursor or Gemini CLI?
Yes. SKILL.md has been an open standard since December 2025, so the same file also works in Codex, Cursor, Gemini CLI and other tools that follow the standard. In Codex you unzip it into .agents/skills/ in your project, or into ~/.agents/skills/ for all your projects; Codex has supported SKILL.md directly since the open standard of December 2025. Putting the contents of SKILL.md into your AGENTS.md still works too. The instructions are just readable text, so any AI assistant that accepts instruction files can work with it.
What is a BATNA and why does the skill start there?
BATNA stands for Best Alternative To a Negotiated Agreement: what you will actually do if this deal falls through. Not what you hope, but what you do. The skill starts there because your BATNA determines your power, not your powers of persuasion. Anyone with no alternative negotiates with their back against the wall, however good their arguments are. That is why the BATNA analysis always ends with an action you can use to strengthen your alternative before the conversation.
Does the skill make up market prices or the counterparty's bid?
No. Making up numbers, client names, market prices and results is on the list of things the skill never does. What it does not know it marks as an assumption or asks about. That applies above all to the counterparty: the skill does estimate their interests and BATNA, but attaches the word assumption and never presents that estimate as fact. The opening line therefore contains a question, so you test your assumption before you steer on it.
What happens if there is no ZOPA?
Then no deal is the right result, and the skill writes that down too. The ZOPA is the zone between your floor and the counterparty's ceiling. If there is no overlap, there is nothing to close without one side dropping below their line. The skill names in one sentence when you walk away and which words you use, so walking away is a prepared step and not an emotional outburst.
Can the skill review an existing proposal or email exchange?
Yes, there is a separate mode for that in the file. You then get a diagnosis of where the weakness lies, a marking per passage placing POSITION or INTEREST after each sentence so you can see how positional your writing is, a list of what is missing from the checklist, a concession analysis flagging every concession made without a counter-ask, and finally a rewritten version in the standard output structure.
Is this also suited to a salary conversation or a labour dispute?
For a salary conversation, yes, and the file even recommends an addition there: the tactical empathy from Never Split the Difference, with labels like it sounds like this is mainly about timing. For a labour dispute with a formal legal procedure, no, and not for advice on contract clauses or liability either. That is stated as a limit in the file, and the skill refers you to a lawyer for that.
A stronger BATNA starts with more enquiries
The most honest way to negotiate better is not found in a conversation technique. It is found in your diary. Anyone with enough enquiries can let a deal go, and that is exactly what a strong BATNA is. If too few enquiries come in, that is where the real work sits. The free SEO scan shows in seconds where your site stands. And if you want to talk further about what else AI can do for your business, from loose skills to full automation, we simply do that in a conversation.