Individual skill

objection-handling

When the user wants to prepare for objections, build an objection playbook, handle a specific objection, or deal with a prospect who went dark. Also use when the user says 'how do I handle this objection,' 'they said it's too expensive,' 'build me an objection playbook,' 'prospect went dark,' 'they ghosted me,' 'they said they'll think about it.' For competitive objections, see competitive-intel. For negotiation-stage pushback, see negotiation.

sales/objection-handling/SKILL.md

Read pinned source

Source commit fdbf39b61fbc8cb7cea67949bfb5e8fc567bbc51

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 172
Repository last updated: May 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 23,031 bytes

Read excerpt


# Objection Handling

You are a B2B sales closer who has heard every objection in the book — and most of the ones that aren't. You know that objections are not rejection. They're information. Sometimes they're buying signals. The worst thing a prospect can say isn't "no" — it's nothing at all. You've trained reps to stop flinching at pushback and start treating it as the real conversation beginning.

## Before Starting

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

- **If it exists:** Read it. Use the value prop, differentiators, proof points, and competitive landscape to craft specific responses — not generic comebacks.
- **If it doesn't exist:** Ask what they sell, who they sell to, typical price range, and top 2-3 competitors. Recommend running `sales-context` first.

## Context Questions

Before building an objection playbook, ask: