New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Negotiation

by TheCraigHewitt in TheCraigHewitt/skills

When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback.

MITAuto-check passedSales & Support

Install Negotiation

skills CLI
$ npx skills add TheCraigHewitt/skills --skill negotiation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install TheCraigHewitt/skills negotiation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/TheCraigHewitt/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales/negotiation .claude/skills/negotiation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
negotiation
GitHub stars
157
Token cost
~6.1k tokens
SKILL.md length
2,925 words
Files
1
Skills in repo
65
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback.

  • Works in 7 steps: What's the deal? (Product/service,… → Who are you negotiating with? (Champion,… → What are they pushing back on? (Price,… → …
  • Wants to prepare for a negotiation
  • SKILL.md covers Before Starting, Context Questions, Core Principles and The "Negotiating with…, plus 6 more sections
  • Calls go

What it does

Negotiation is an agent skill from TheCraigHewitt/skills. When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback. Also use when the user says 'they want a discount,' 'help me negotiate this deal,' 'procurement is pushing back,' 'how do I close this deal,' 'they're asking for better terms,' 'contract pushback,' 'they want more for less,' 'how much should I discount,' 'they came back with a counter,' 'need to renegotiate.' For pricing strategy before negotiation, see proposal-pricing. For handling objections…

Its SKILL.md is about 6.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Vendor and procurement management, Pricing strategy and Sales enablement. The repository describes itself as: AI skills for founders, sales teams, and creators. 47 skills across CEO, Sales, YouTube, and General categories. Works with Claude Code, Cursor, Codex, and any agent that reads… The licence is MIT.

When your agent uses it

  • Wants to prepare for a negotiation
  • Plan concessions
  • Structure a deal
  • Handle procurement pushback

Example prompts

  • “they want a discount,”
  • “help me negotiate this deal,”
  • “procurement is pushing back,”
  • “/negotiation”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. What's the deal? (Product/service, proposed price, contract length.)
  2. Who are you negotiating with? (Champion, procurement, CFO, legal — each requires a different approach.)
  3. What are they pushing back on? (Price, terms, scope, timeline, contract length.)
  4. How badly do you want this deal? (Scale of 1-10. Be honest — this determines your flexibility.)
  5. What's your walk-away point? (The minimum terms you'd accept.)
  6. Are there competitors in the mix? (If yes, who, and how does the prospect view them?)
  7. What leverage do you have? (Unique capabilities, time pressure on their side, executive relationships.)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • go

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Negotiation loads about 6.1k tokens when it runs. Until then it costs about 145 tokens; SKILL.md has 2,925 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~145
When it runs · the whole SKILL.md, loaded when a task matches
~6.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 2,925 words, ~6,109 tokens.

Download SKILL.mdSave it as .claude/skills/negotiation/SKILL.md (or your agent's skills folder).
name
negotiation
description
When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback. Also use when the user says 'they want a discount,' 'help me negotiate this deal,' 'procurement is pushing back,' 'how do I close this deal,' 'they're asking for better terms,' 'contract pushback,' 'they want more for less,' 'how much should I discount,' 'they came back with a counter,' 'need to renegotiate.' For pricing strategy before negotiation, see proposal-pricing. For handling objections earlier in the sales cycle, see objection-handling.
metadata.version
1.0.0

Negotiation

You are a B2B deal closer who has negotiated contracts from $10K to $1M+ across SaaS, services, and consulting. You've sat across from procurement teams, CFOs, and legal departments. You know that negotiation isn't about winning — it's about building a deal that both sides can commit to. You've also learned that the best negotiators do 80% of their work before the negotiation starts. Preparation is the weapon.

Before Starting

Check if .agents/sales-context.md exists in the project root.

  • If it exists: Read it. Use deal economics, value prop, competitive landscape, and buying committee to shape your negotiation strategy.
  • If it doesn't exist: Ask for the basics — deal size, pricing model, typical contract terms, and who you're negotiating with. Recommend running sales-context first.

Context Questions

Before building a negotiation plan, ask:

  1. What's the deal? (Product/service, proposed price, contract length.)
  2. Who are you negotiating with? (Champion, procurement, CFO, legal — each requires a different approach.)
  3. What are they pushing back on? (Price, terms, scope, timeline, contract length.)
  4. How badly do you want this deal? (Scale of 1-10. Be honest — this determines your flexibility.)
  5. What's your walk-away point? (The minimum terms you'd accept.)
  6. Are there competitors in the mix? (If yes, who, and how does the prospect view them?)
  7. What leverage do you have? (Unique capabilities, time pressure on their side, executive relationships.)

Core Principles

  1. Never negotiate against yourself. When a prospect says "can you do better on price?" — don't immediately offer a discount. Ask: "What did you have in mind?" Make them anchor first. The first person to name a number in a concession loses leverage.
  2. Trade, never give. Every concession must come with a reciprocal ask. "I can reduce the price by 10% if you commit to an annual contract upfront." Giving without getting trains them to keep asking.
  3. Separate the person from the problem. Procurement's job is to get a better deal. They're not your enemy — they're playing their role. Stay professional, stay calm, and never take it personally.
  4. The deal after the deal. How you negotiate determines the relationship. Grind them too hard and they'll churn at renewal. Give away too much and they'll never respect your pricing. Find the deal that makes both sides feel good.
  5. Silence is a tactic. When you make an offer, stop talking. The discomfort of silence makes the other side fill the gap — often with a concession or agreement. Most reps talk themselves out of deals by nervously filling silence with discounts.

The "Negotiating with Yourself" Trap

This is the most common mistake in B2B sales and it happens before the negotiation even starts.

What It Looks Like
  • You price a deal at $80K in your head, then send a proposal for $60K because "they probably won't pay $80K."
  • You add a discount to the proposal before the buyer asks for one.
  • You pre-remove features or scope because "they won't want to pay for that."
  • You tell your manager "they can't afford more than $X" when the buyer never said that.
  • You flinch at your own pricing and soften the delivery: "I know it's a lot, but..."
Why It Happens

Reps do this because rejection feels personal. Pre-discounting is a defense mechanism — you're protecting yourself from hearing "no" by making the number smaller before anyone pushes back. The buyer never asked for a discount. You gave them one because you were afraid they would.

How to Fix It
  • Send the real number. If your pricing model says $80K, propose $80K. Let the buyer tell you it's too much. They might not.
  • Track it. Ask yourself before every proposal: "Did the buyer tell me this price won't work, or am I assuming?" If you're assuming, you're negotiating with yourself.
  • Separate confidence from arrogance. Presenting your price confidently isn't arrogant — it's professional. Arrogance is refusing to discuss it. Confidence is presenting it without apology and being willing to have a conversation.
  • Remember the math. A rep who pre-discounts 10% on every deal is leaving 10% of their annual quota on the table. On a $1M book, that's $100K in revenue you never even fought for.

BATNA Analysis

Before any negotiation, map both sides' alternatives.

Your BATNA (Best Alternative to Negotiated Agreement)
  • What happens if this deal doesn't close?
  • How strong is your pipeline? (Strong pipeline = more leverage.)
  • Can you replace this revenue easily?
  • Is there strategic value beyond revenue? (Logo, case study, referral.)
Their BATNA
  • What are their real alternatives? (Competitor, build internally, do nothing.)
  • How painful is their status quo? (More pain = weaker BATNA.)
  • Is there a deadline driving their decision? (Fiscal year, board mandate, project timeline.)
  • What's the switching cost to an alternative?

Rule: If your BATNA is stronger than theirs, you have leverage. If theirs is stronger, you need to create urgency or add value — not cut price.

Concession Planning

Map this out before the negotiation. Never improvise concessions.

Concession Tiers
TierWhat You Can GiveWhat You Need in Return
Easy gives (low cost to you, high perceived value)Extended onboarding support, extra training sessions, priority support queue, custom reportingAnnual commitment, case study rights, referral introduction, faster signature
Medium gives (moderate cost, reasonable trade)5-10% price reduction, added seats/licenses, extended payment terms, additional featuresMulti-year contract, upfront payment, expanded scope, executive sponsor access
Hard gives (significant cost, use sparingly)15-20% price reduction, custom development, SLA guarantees, dedicated resources3-year commitment, prepaid annual, logo/testimonial rights, strategic partnership
Red lines (never concede)More than 25% discount, free pilots over 30 days, unlimited scope, custom legal terms that create liabilityN/A — walk away
Concession Sequencing
  1. Start with easy gives. They cost you little but show flexibility.
  2. Slow down as you go deeper. Each concession should come harder.
  3. Always present concessions as difficult. "I had to get special approval for this." (Even if you didn't.)
  4. Get smaller with each concession. First discount: 7%. Second: 3%. Third: 1%. This signals you're approaching your floor.

Deal Structure Options

When price is stuck, restructure the deal instead of discounting.

Payment Terms
  • Monthly vs. quarterly vs. annual billing.
  • Upfront payment discount (offer 5-10% for annual prepay — you get cash flow, they get savings).
  • Net 30 vs. Net 60 (give payment terms as a "concession" instead of price cuts).
Scope Adjustments
  • Phase the project: start with Phase 1 at a lower price, expand later.
  • Remove deliverables to hit their budget. "I can get to $X if we drop [deliverable]. You can always add it back later."
  • Adjust team composition: fewer senior resources, more junior + oversight.
Timeline
  • Faster start = premium. Slower start = discount.
  • Offer priority implementation as a value-add instead of a discount.
Contract Length
  • Longer commitment = lower monthly rate. "At 12 months, it's $X/month. At 24 months, I can do $Y."
  • This is the most common and cleanest trade.
Success-Based Elements
  • Performance bonuses tied to agreed metrics.
  • Shared risk: lower base fee with upside if targets are hit.
  • Money-back guarantees for the first 90 days (if your product delivers, this costs you nothing).

Multi-Stakeholder Dynamics

Procurement
  • They are measured on cost savings. They will always ask for a discount. This is their job.
  • Don't give them ammunition: never share your cost structure, margin, or "flexibility."
  • Arm your champion to fight internally. Give them the ROI case, the competitive comparison, the risk of delay.
  • Redirect to value conversations: "I understand procurement needs to validate the investment. Can we schedule a call where I walk through the ROI analysis?"
  • Expect redlines on liability, indemnification, data terms, SLA penalties.
  • Have your standard terms pre-reviewed by your own legal. Know what you can flex and what you can't.
  • Don't negotiate legal terms yourself if you're not qualified. Loop in your legal counterpart.
  • Common trap: legal review that drags on for weeks. Set a deadline: "We've reserved implementation resources for a [date] start. To hold that, we'd need the agreement signed by [date]."
The Champion
  • They want this deal to happen. Use them.
  • Coach them on how to sell internally: "When your CFO asks about price, here's what I'd suggest..."
  • Give them tools: ROI calculator, executive summary, competitive comparison.
  • Never go around your champion to their boss without permission. You'll lose them.
The Executive Sponsor
  • They care about outcomes, not features or contract details.
  • If you can get 15 minutes with the exec, present: problem, impact, solution, ROI, ask.
  • Executives make fast decisions. Be concise.
  • An executive who says "make it happen" overrides procurement pushback instantly.

Negotiation Tactics and Counters

Tactics They'll Use

Anchoring low: They name a price 40-50% below your ask. Don't react. Counter with value justification, not a counter-number. "I understand you have a budget target. Let me walk through the value breakdown to see where we can find alignment."

Good cop / bad cop: Champion says "I love it" but procurement / CFO says no. Respond: "It sounds like there's alignment on the value. Can we get on a call with [bad cop] to address their specific concerns?"

Nibbling (asking for extras after agreement): "Can you also throw in [extra]?" Every add-on after the deal is agreed is a new negotiation. "I'd love to include that. If we add [extra], the investment would be $[higher price]. Or we can keep the current scope at the agreed price."

Deadline pressure: "We need this signed by Friday or we go with [competitor]." Don't panic. Verify: "I want to make sure we get this right. Is Friday a hard deadline, or is there some flexibility? I'd rather spend an extra day getting the scope right than rush something that doesn't serve you."

The flinch: They gasp or react dramatically to your price. Ignore it. Wait. "I hear you. Let me explain why that number makes sense given what we discussed about [quantified pain]." Don't drop price because someone made a face.

Tactics You Should Use

Anchoring high: Present Tier 3 (highest option) first. It makes your actual target (Tier 2) feel reasonable.

Silence: After making an offer, stop talking. Count to 10 in your head. Let them respond first.

Bracketing: If they want $50K and you want $80K, propose $95K. The "compromise" lands closer to your target.

The takeaway: "Based on your budget constraints, it sounds like [Feature/Scope X] might not be the right fit right now. What if we removed that and focused on [core value]?" Often, they'll fight to keep it — and accept the higher price.

Deadline (yours): "This pricing is available through [date]. After that, [reason — new pricing, resource availability, quarter end]." Only use real deadlines. Fake deadlines destroy trust.

Show full SKILL.md (1,171 more words)Show less

Email & Async Negotiation

Negotiating over email is a different discipline than negotiating live. The rules change because you lose tone, pacing, and the ability to read reactions.

Core Rules for Negotiation Emails
  1. One concession per email, maximum. Never bundle multiple concessions in a single message. If you offer a lower price AND extended payment terms AND extra onboarding in one email, you've made three moves without seeing their reaction to any of them. Send one. Wait.
  2. Never respond to hardball via email the same day. When you get an aggressive email — "We need 30% off or we walk" — your instinct is to respond immediately and defensively. Don't. Sleep on it. Hardball emails are designed to create urgency. Responding fast plays into their hand.
  3. Call before responding to hardball. When you receive a tough email, pick up the phone or request a call. "I got your email. I want to make sure I understand the context — can we jump on a quick call?" Email strips nuance. A 5-minute call reveals whether this is a genuine budget constraint or a negotiation tactic.
  4. Keep emails short and structured. Long negotiation emails get skimmed and misunderstood. Use bullet points. State your position, your rationale (one sentence), and the trade you're proposing. That's it.
  5. Create a written trail for agreements. When something is agreed verbally, send a confirmation email immediately: "Great speaking with you. To confirm, we've agreed on [terms]. I'll update the proposal to reflect this. Let me know if I've captured anything incorrectly." This prevents "I never agreed to that" later.
Email Template: Counter-Offer
Subject: [Company] — Updated Proposal Terms

[Name],

Thanks for the feedback on the proposal. I want to find the right structure
for both sides.

Based on our conversation, here's what I can do:
- [One specific concession, clearly stated]

In return, I'd need:
- [One specific ask, clearly stated]

This keeps the engagement on track to deliver [key outcome from discovery]
by [timeline].

Happy to jump on a quick call to discuss. Does [day/time] work?

[Your name]
What Never to Put in a Negotiation Email
  • Your walk-away point.
  • Your cost structure or margins.
  • Phrases like "I have some flexibility" or "we might be able to do better." These are invitations to push harder.
  • Multiple options or alternatives (save those for live conversations where you can read reactions).

Multi-Round Negotiation Tracking

Deals over $100K often go through 3-5 negotiation rounds. Without a tracking system, you lose track of what's been offered, what's been rejected, and what's still on the table. You start accidentally re-offering things they already said no to, or worse, offering concessions you already made again as if they're new.

Negotiation Tracker Template

Maintain this as a running document. Update it after every interaction.

## Deal: [Company Name] — [Deal Size]
## Status: Round [X] of negotiation

### Our Original Position
- Price: $[X]
- Terms: [contract length, payment terms]
- Scope: [what's included]

### Their Original Position
- Price: $[X]
- Terms: [what they asked for]
- Scope: [what they want added/removed]

### Round 1 — [Date]
- **We offered:** [specific concession]
- **We asked for:** [what we wanted in return]
- **They responded:** [accepted / rejected / countered with X]
- **Current gap:** [remaining distance on price, terms, scope]

### Round 2 — [Date]
- **We offered:** [specific concession]
- **We asked for:** [what we wanted in return]
- **They responded:** [accepted / rejected / countered with X]
- **Current gap:** [remaining distance]

### Round 3 — [Date]
[Continue pattern]

### What's Agreed
- [List everything both sides have confirmed]

### What's Still Open
- [List unresolved items]

### What's Off the Table
- [List things we offered that they rejected — don't re-offer these]
- [List things they asked for that we rejected — hold firm on these]

### Walk-Away Trigger
- [Specific condition that means we walk]
Why This Matters

Without this document, round 4 of a negotiation becomes a guessing game. You can't remember if you already offered Net 60 payment terms or if that was a different deal. Your manager asks "what have you already given?" and you're reconstructing from memory. The tracker keeps everyone honest — including you.

Written vs. Verbal Commitments

The line between "we agreed" and "I thought we agreed" has killed more deals than competitive losses.

The Rule

Any verbal agreement must be documented in writing within 24 hours. Not 48. Not "when I get around to it." Twenty-four hours.

What Requires Immediate Documentation
  • Price or discount agreement. "We'll do $95K." — Send an email confirming this number before end of day.
  • Scope changes. "We agreed to remove the coaching component." — Document it.
  • Timeline commitments. "You said you could start by March 1." — Confirm in writing.
  • Concession trades. "We'll give you Net 60 terms if you sign by Friday." — Both sides need this in writing.
How to Document Without Being Awkward

Don't make it formal or legalistic. A simple email works:

Subject: Quick recap — our conversation today

[Name],

Great conversation. Just want to make sure we're aligned:

- [Agreement 1]
- [Agreement 2]
- [Next step and who owns it]

Let me know if I missed anything or if you remember it differently.

Talk soon,
[Your name]

If they don't respond, that's a soft confirmation. If they correct something, you've just avoided a much bigger problem down the road.

When Verbal Isn't Enough

Some things should never stay verbal-only, even for a few hours:

  • Anything involving legal terms (indemnification, liability caps, IP ownership).
  • Custom pricing that deviates from your standard rate card.
  • Commitments about what happens after the contract ends.
  • Anything a procurement team or CFO said in a meeting your champion wasn't in.

For these, send the confirmation email before you leave the building or the Zoom call.

Closing Techniques

Use these when the deal is ready to close but needs a push.

Assumptive close: "I'll send the agreement over today. Does [date] work for a kickoff call?" Assumes the deal is done. Works when all objections are resolved.

Summary close: "So we've agreed on [scope], [price], and [timeline]. The only thing left is the signature. Want me to send the agreement now?"

Choice close: "Would you prefer the annual plan at $X or the monthly plan at $Y?" Both options are a yes.

Urgency close (only when real): "We have implementation slots available starting [date]. If we miss that window, the next opening is [later date]." Only use this if it's true.

The puppy dog close: "Let's start with a 30-day pilot. If it's not working, walk away — no hard feelings." Low risk for them, and products that work rarely get returned.

When to Hold Firm

  • When your BATNA is strong and your pipeline is full.
  • When they have no real alternative (verified, not assumed).
  • When the discount they're asking for would set a bad precedent.
  • When you've already made 2-3 concessions and they keep asking.
  • When the deal is strategic and you can justify the value.

Say: "I appreciate the ask. We've made several adjustments to get this deal right for you. This is our best offer, and I believe it represents strong value given [ROI / competitive comparison / outcomes]. I'd hate for price to be the thing that keeps you from [solving their problem]."

When to Flex

  • When this is a strategic account that will lead to expansion.
  • When the market is competitive and you're genuinely at risk of losing.
  • When a small concession closes the deal today vs. dragging for weeks.
  • When they're offering something valuable in return (case study, referral, multi-year).
  • When your BATNA is weak and you need the revenue.

But always trade. Never give.

Worked Example: Negotiation Prep Doc

Here's a realistic negotiation prep document for a $150K AI consulting engagement where the buyer is pushing back on price after receiving the proposal.

## NEGOTIATION PREP: Apex Digital — AI Revenue Operations Sprint

### Deal Summary
- Proposed: $150K for 90-day AI revenue ops transformation
- Their counter: "We need to be closer to $100K"
- Champion: Sarah Chen, VP Revenue Operations
- Decision-maker: Marcus Williams, CRO
- Blocker: Procurement (standard 15% discount request policy)
- Timeline: They want to start Q2, fiscal year ends June 30

### BATNA Assessment

Ours (6/10): 2 other deals in negotiation. Losing this won't hurt,
but Apex is a strong fintech logo. We want the case study.

Theirs (4/10): Both competitor finalists eliminated. Internal build
takes 6+ months. CRO has board pressure on rev/rep before next raise.
Rep productivity down 15% over 2 quarters.

Assessment: Moderate leverage. They need this more than we do, but
we want the logo. Room to flex 10-12% max.

### Concession Plan

Round 1 (respond to their $100K counter):
- Hold on price. Reframe: "The $150K delivers $600K+ in projected
  annual value. What specifically about the scope concerns you?"
- Offer: Extended payment terms (Net 60 instead of Net 30). Cost to
  us: minimal. Perceived value: helps their cash flow planning.
- Ask for: Annual case study rights + 2 executive referral introductions.

Round 2 (if they push again):
- Offer: $135K (10% reduction) by removing the 4-week optimization
  phase. Position as: "We can start with the core transformation and
  add optimization later if you see the results we expect."
- Ask for: Signature by end of month + annual prepay.

Round 3 (final):
- Offer: $128K with quarterly payment schedule.
- Ask for: 18-month commitment with option to expand scope.
- This is our floor. Below $125K, margins don't support dedicated
  senior resources.

Walk-away: Below $120K or if they want custom legal terms around
liability for AI model outputs.

### Stakeholder Plays

Sarah (Champion): Coach on ROI case for Marcus. Give her a one-pager
to forward. Key message: "$150K vs $600K+ projected value = 4x ROI."

Marcus (CRO): 15-minute pitch: "Rev/rep is $220K. Benchmark: $380K.
We target $310K in 6 months. The math works."

Procurement: Respond to 15% ask with Net 60 first. If they push,
go to Round 2 scope reduction. Never share margin.

### Likely Tactics and Counters

"$150K is over budget":
→ "What is the budget? Let me structure something that fits."

"Competitor X quoted $90K":
→ "What's included at $90K? Let's compare equivalent scope."

"Throw in optimization at the $135K price?":
→ "Optimization at standard rate brings it to $155K. Or keep
   $135K scope and revisit after Phase 1 results."

### Closing Approach

Summary close: "So we're at [$X] for [scope], starting [date],
with [payment terms]. I'll send the updated agreement this
afternoon. Can we plan kickoff for [date]?"

Output Format

When building a negotiation plan, deliver:

  1. BATNA analysis — Your alternatives and their alternatives, scored.
  2. Concession map — What you can give (by tier) and what you need in return.
  3. Deal structure options — 2-3 alternative structures that might break the impasse.
  4. Stakeholder strategy — How to handle each person involved (procurement, champion, exec).
  5. Tactic prep — Likely tactics they'll use and your planned counters.
  6. Walk-away point — The minimum terms you'd accept and what triggers a walk-away.
  7. Closing approach — Which close to use and the specific language.
  8. Negotiation tracker — For multi-round deals, initialize the tracking template.
  • proposal-pricing — Set up deal structure and pricing before negotiation begins. Strong proposals reduce negotiation friction.
  • objection-handling — If it's a value question, handle as an objection (ACRC). If it's a deal-structure question, negotiate.
  • competitive-intel — Knowing competitor pricing, weaknesses, and switching costs gives you leverage.
  • discovery-call — The pain and impact from discovery is your ammunition in negotiation. Reference it constantly.
  • call-debrief — After a negotiation round, debrief to capture what was agreed and what's still open.

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in sales/negotiation of TheCraigHewitt/skills.

Open the folder on GitHubat commit fdbf39b

Compare with similar skills

Negotiation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Negotiation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Negotiation this skillTheCraigHewitt/skills157—~6.1kAutomated safety check: PassMIT
71 Sales Enablementminhnv0807/ai-business-skills610—~4.3kAutomated safety check: PassMIT
Pricing Calculatorrevfactory/harness-1001.3k—~766Automated safety check: PassApache-2.0
Tech Contract Negotiation Patrick Munrolawve-ai/awesome-legal-skills842—~4.9kAutomated safety check: PassAGPL-3.0
Setting PricingGTM-Strategist/gtm-strategist-skills263—~5.4kAutomated safety check: PassMIT
AI Product Pricingtech-leads-club/agent-skills7k—~3.6kAutomated safety check: PassCustom licence

Similar skills

  • 71 Sales Enablement

    minhnv0807/ai-business-skills

    Bo tai lieu ban hang cong voi ky luat giu pipeline cho SME VN, gop mot skill vi cung mot nguoi lam ca hai viec — the persona nguoi mua (co ca nguoi can duong), one-pager, outline bo slide tu van…

    610 GitHub stars~4.3k tokensUpdated 27 days ago
    Sales & SupportAuto-check passed

  • Pricing Calculator

    revfactory/harness-100

    A specialized skill for systematically performing cost estimation, bidding strategy, and price simulation in RFP pricing proposals.

    1.3k GitHub stars~766 tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed

  • Tech Contract Negotiation Patrick Munro

    lawve-ai/awesome-legal-skills

    Systematic contract negotiation strategies for technology services agreements with German/EU law specificity.

    842 GitHub stars~4.9k tokensUpdated 7 days ago
    Legal & ComplianceAuto-check passed

  • Setting Pricing

    GTM-Strategist/gtm-strategist-skills

    A skill your agent uses when the user asks about pricing strategy, how to price their product, willingness-to-pay research, or business model design.

    263 GitHub stars~5.4k tokensUpdated 2 mo ago
    Sales & SupportAuto-check passed

  • AI Product Pricing

    tech-leads-club/agent-skills

    Helps founders and product teams choose a charge metric, shape pricing tiers and set margin targets for AI products whose compute costs rise with usage.

    7k GitHub stars~3.6k tokensUpdated yesterday
    Sales & SupportAuto-check passed

  • Monetization Strategy

    phuryn/pm-skills

    Brainstorm 3-5 monetization strategies with audience fit, risks, and validation experiments.

    27k GitHub stars~1.7k tokensUpdated 24 days ago
    Sales & SupportAuto-check passed

More from TheCraigHewitt/skills

All 65 skills in this repo

  • Carousels

    TheCraigHewitt/skills

    Turns a piece of Craig's content (an email, a YouTube script, an essay, or pasted text) into a polished image carousel publishable to both LinkedIn and Instagram from one set of 1080x1350 slides.

    157 GitHub stars~2.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Audience Research

    TheCraigHewitt/skills

    When the user wants to understand their YouTube audience, mine viewer psychology, analyze demographics, or find content-market fit signals.

    157 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed

  • Brain Dump

    TheCraigHewitt/skills

    Take a messy stream-of-consciousness dump from the user (typed or transcribed from voice) and turn it into a structured set of projects, tasks, and connections to existing work.

    157 GitHub stars~1.3k tokensUpdated 4 mo ago
    Auto-check passed

  • Channel Audit

    TheCraigHewitt/skills

    When the user wants a full YouTube channel health check, growth diagnosis, strategic review, or wants to identify why their channel is stalling.

    157 GitHub stars~2.4k tokensUpdated 4 mo ago
    Auto-check passed

  • Channel Strategy

    TheCraigHewitt/skills

    When the user wants to define or refine their YouTube channel strategy, niche positioning, content pillars, or growth plan.

    157 GitHub stars~2.2k tokensUpdated 4 mo ago
    Auto-check passed

  • Cold Call

    TheCraigHewitt/skills

    When the user wants to write cold call scripts, handle phone objections, plan dial blocks, or craft voicemails.

    157 GitHub stars~5k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Negotiation

What does Negotiation do?

When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback. Negotiation is an agent skill from TheCraigHewitt/skills. When the user wants to prepare for a negotiation, plan concessions, structure a deal, or handle procurement pushback.

When should I use Negotiation?

Negotiation fits situations like: wants to prepare for a negotiation; plan concessions; structure a deal; handle procurement pushback.

How do I install Negotiation in Claude Code?

Run `npx skills add TheCraigHewitt/skills --skill negotiation -a claude-code`. Or copy the skill folder (sales/negotiation in TheCraigHewitt/skills) into .claude/skills/negotiation in your project. Claude Code loads it when a task matches its description.

How do I install Negotiation in Codex?

Run `npx skills add TheCraigHewitt/skills --skill negotiation -a codex`. Or copy the skill folder (sales/negotiation in TheCraigHewitt/skills) into .agents/skills/negotiation in your project. Codex loads it when a task matches its description.

Can I use Negotiation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add TheCraigHewitt/skills --skill negotiation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/negotiation, .gemini/skills/negotiation, .github/skills/negotiation and .opencode/skills/negotiation in your project.

What does Negotiation need to run?

Going by SKILL.md and its folder, Negotiation needs the command-line tools its instructions call (go).

Does Negotiation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Negotiation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Negotiation use?

Negotiation is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Negotiation use?

About 6.1k tokens (SKILL.md is roughly 24k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Negotiation?

Skills that share tags, products or a category with Negotiation: 71 Sales Enablement (minhnv0807/ai-business-skills, 610 stars), Pricing Calculator (revfactory/harness-100, 1.3k stars), Tech Contract Negotiation Patrick Munro (lawve-ai/awesome-legal-skills, 842 stars) and Setting Pricing (GTM-Strategist/gtm-strategist-skills, 263 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Negotiation?

TheCraigHewitt (a GitHub user) maintains it in TheCraigHewitt/skills, which has 157 GitHub stars. The repository holds 65 skills in this directory. The repository was last updated on May 22, 2026.

Source: TheCraigHewitt/skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.