Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Objection Handling

ASecurity

Handle sales objections using tactical empathy. Use when the user says "how do I handle this objection", "prospect said [X]", "they pushed back on price", "they said they're not ready", "how to respond to 'we already have a solution'", "they said 'send me more information'", "objection response", "they went dark after the proposal", "how to handle 'we don't have budget'", or wants to craft a response to a specific sales objection.

20 stars
0 votes
0 copies
0 views
Added 10/4/2026
ai-agentsgo

Security Analysis

A100/100

Scanned 10/4/2026

$npx -y skills add qa-aman/claude-skills --skill objection-handling --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Objection Handling?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Objection Handling
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/qa-aman-objection-handling/badge)](https://www.skillsdirectory.com/skills/qa-aman-objection-handling)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: objection-handling
description: >
  Handle sales objections using tactical empathy. Use when the user says "how do I handle
  this objection", "prospect said [X]", "they pushed back on price", "they said they're not
  ready", "how to respond to 'we already have a solution'", "they said 'send me more
  information'", "objection response", "they went dark after the proposal", "how to handle
  'we don't have budget'", or wants to craft a response to a specific sales objection.
---

## Overview

Based on **"Never Split the Difference"** by Chris Voss. Voss, former FBI lead hostage negotiator, argues that rational argument rarely moves people in high-stakes conversations - emotional acknowledgment does. His Tactical Empathy framework - labeling emotions, using calibrated questions, and getting the prospect to say "that's right" - is directly applicable to sales objections. The goal is not to counter the objection. The goal is to make the prospect feel heard, then redirect.

## Workflow

### Step 1: Identify the objection type

Before responding, classify the objection. Different types require different responses.

| Type | What it sounds like | What it usually means |
|---|---|---|
| **Smokescreen** | "Send me more info" / "We'll revisit next quarter" | They don't see enough value yet or don't want to say no |
| **Genuine concern** | "We're worried about integration complexity" | A real blocker that needs a real answer |
| **Stall** | "We're not ready to make a decision right now" | Stakeholder alignment is incomplete internally |
| **Price** | "This is more than we expected / budgeted" | Value hasn't been established relative to cost |
| **Competitor** | "We're also looking at [competitor]" | You haven't differentiated clearly enough |

Responding to a smokescreen with a feature argument makes it worse. Classify first.

### Step 2: Label the emotion before addressing the content

Voss's core move: name what you think the prospect is feeling. This is a "label." It starts with "It seems like..." or "It sounds like..." - never "I feel like you..."

A label does two things: it makes the prospect feel understood, and it invites them to correct you if you're wrong. Either way, you learn more.

Examples:
- "It seems like the timing isn't quite right on your end."
- "It sounds like you've had some bad experiences with implementations like this before."
- "It seems like there's some internal uncertainty about whether this is the right priority right now."

Pause after the label. Do not fill the silence. Let them respond.

### Step 3: Use a calibrated question to open them up

After the label, ask an open-ended question that starts with "What" or "How." Avoid "Why" - it sounds accusatory.

Examples by objection type:
- Price: "What would need to be true for the investment to make sense for your team?"
- Timing: "What does your timeline look like for getting this solved?"
- Competitor: "What would make you confident you were making the right call here?"
- Stall: "How does your team typically work through a decision like this?"

Do not answer your own calibrated question. Ask it and stop.

### Step 4: Apply the specific response by objection type

**"We don't have budget."**
"It sounds like budget is a real constraint right now. What would the ROI need to look like for this to be justifiable to your finance team?" - then build the business case together.

**"We already have a solution."**
"It sounds like you've invested in this area before. What's working well with what you have, and where does it still fall short?" - this reveals the gap your product fills without attacking their current choice.

**"Send me more information."**
"It sounds like there's something specific that's still unclear. What would be most useful for me to address?" - never send a generic one-pager in response to this.

**"We're not ready yet."**
"It sounds like the timing isn't quite right. What needs to happen internally before this becomes a priority?" - surfaces the real blocker and gives you a re-engagement trigger.

**"Your price is too high."**
"It seems like the investment is higher than you expected. How far apart are we?" - get the number. Then: "What would you need to see to make the difference feel justified?"

### Step 5: Get to "that's right"

Voss's key indicator that you've succeeded: when the prospect says "that's right" - not "you're right." "You're right" means they're placating you. "That's right" means they feel understood.

Before moving forward, summarize their position back to them completely and accurately. Include their concerns, their constraints, and their goals.

"So if I'm hearing you correctly - the value is there, but the timing is the issue because [X] is happening this quarter, and you'd want to revisit in [month] once [condition]. Is that right?"

Wait for their confirmation before advancing.

## Anti-Patterns

**1. Immediately counter-arguing**
Bad: "I understand budget is tight, but if you look at the ROI..."
Good: Label the emotion first. "It sounds like budget is a real constraint right now." Then pause.

**2. Sending more material in response to "send me more info"**
Bad: Sending a 20-page deck in response to "send me more information."
Good: Ask what specifically is unclear. The request for info is almost always a soft no in disguise.

**3. Accepting the stated objection at face value**
Bad: Taking "we already have a solution" as a closed door.
Good: "It sounds like you've invested in this area before. What's working well, and where does it still fall short?"

**4. Pushing for a close during the objection conversation**
Bad: "So based on all that, are you ready to move forward?"
Good: Get to "that's right" first. Confirm next steps only after full acknowledgment.

## Quality Checklist

- [ ] Objection classified by type before responding
- [ ] Used a label ("It seems like..." / "It sounds like...") before any content response
- [ ] Paused after the label - did not fill the silence
- [ ] Used a calibrated "What" or "How" question, not a "Why" question
- [ ] Did not send generic materials in response to "send me more info"
- [ ] Got the prospect to say "that's right" before advancing
- [ ] Left the conversation with a specific next step or re-engagement trigger

Attribution

qa-amanqa-aman
View sourceSee grades on GitHubMore from qa-aman →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →