How do I install the Objection Handler skill?

Run npx skillmds@latest add alebgl77/objection-handler in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Objection Handler safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Objection Handler?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Objection Handler free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Objection Handler?

alebgl77 (@alebgl77) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Objection Handler by alebgl77 — Agent Skill

Name: Objection Handler
Author: alebgl77

Objection Handler

Turns prospect pushback into progress — diagnoses the real objection behind the stated one and scripts calm, honest responses for price, timing, competitor, authority and brush-off objections. Use when the user says "they said it's too expensive", "prospect went silent", "they're comparing us to X", "how do I answer this objection", or pastes a tricky reply.

alebgl77 5efb74c 2.8 KB Updated Sep 17, 2026

File contents

Objection Handler — Persuader

"An objection is a question wearing armor."

When to use

"They said {objection} — how do I respond?"
"Prospect ghosted after the proposal"
"They're going with a competitor unless..."
Paste the exact message or describe the moment; works for email replies and live-call scripting

Workflow

Capture the objection verbatim — the words matter more than the summary.
Diagnose the objection behind the objection: price usually means unclear value; "not now" means no burning pain or hidden stakeholder; "send me info" means unconvinced champion. State your diagnosis and confidence.
Choose the frame: clarify (ask before answering), reframe (change the comparison), evidence (proof/case), trade (concede X for Y), or release (walk away with grace). Never argue.
Script the response: acknowledge → explore with ONE question → respond to the real objection → propose a next step. ≤ 120 words for email, ≤ 4 lines for live.
Prepare the branch: their 2 most likely replies to your response, and yours to each (one level deep only).
Honesty check: if the objection is RIGHT (bad fit, real overprice, missing feature), say so and script the honest version — releasing a bad-fit deal is a win.
Log it: append objection + what worked to an objections-log.md so patterns accumulate.

Output format

## Objection play — "{verbatim}"
Diagnosis: stated {X} → real {Y} (confidence: high/med/low)
Frame: {clarify/reframe/evidence/trade/release}

**Response ({channel})**: ...
**If they say** "{likely reply 1}" → ...
**If they say** "{likely reply 2}" → ...
**If the objection is simply true** → {honest path}
Next step to propose: ...

Quality bar

Response opens with acknowledgment, not rebuttal
Exactly one exploratory question before countering
No pressure tactics, fake scarcity or manufactured urgency
The "objection is true" path is genuinely considered
Ends by proposing a concrete next step

Example

Ask: "'Too expensive, competitor is half the price' — answer this email." Produced: diagnosis (value not landed, comparison on wrong axis), reframe response asking which outcome they're pricing, evidence of switching cost, branch replies, and the honest path ("if budget is truly {X}, competitor Y is the right call — here's what to check in their contract").

---name: objection-handlerdescription: Turns prospect pushback into progress — diagnoses the real objection behind the stated one and scripts calm, honest responses for price, timing, competitor, authority and brush-off objections. Use when the user says "they said it's too expensive", "prospect went silent", "they're comparing us to X", "how do I answer this objection", or pastes a tricky reply.---# Objection Handler — Persuader> "An objection is a question wearing armor."## When to use- "They said {objection} — how do I respond?"- "Prospect ghosted after the proposal"- "They're going with a competitor unless..."- Paste the exact message or describe the moment; works for email replies and live-call scripting## Workflow1. **Capture the objection verbatim** — the words matter more than the summary.2. **Diagnose the objection behind the objection**: price usually means unclear value; "not now" means no burning pain or hidden stakeholder; "send me info" means unconvinced champion. State your diagnosis and confidence.3. **Choose the frame**: clarify (ask before answering), reframe (change the comparison), evidence (proof/case), trade (concede X for Y), or release (walk away with grace). Never argue.4. **Script the response**: acknowledge → explore with ONE question → respond to the real objection → propose a next step. ≤ 120 words for email, ≤ 4 lines for live.5. **Prepare the branch**: their 2 most likely replies to your response, and yours to each (one level deep only).6. **Honesty check**: if the objection is RIGHT (bad fit, real overprice, missing feature), say so and script the honest version — releasing a bad-fit deal is a win.7. **Log it**: append objection + what worked to an `objections-log.md` so patterns accumulate.## Output format```## Objection play — "{verbatim}"Diagnosis: stated {X} → real {Y} (confidence: high/med/low)Frame: {clarify/reframe/evidence/trade/release}**Response ({channel})**: ...**If they say** "{likely reply 1}" → ...**If they say** "{likely reply 2}" → ...**If the objection is simply true** → {honest path}Next step to propose: ...```## Quality bar- [ ] Response opens with acknowledgment, not rebuttal- [ ] Exactly one exploratory question before countering- [ ] No pressure tactics, fake scarcity or manufactured urgency- [ ] The "objection is true" path is genuinely considered- [ ] Ends by proposing a concrete next step## Example**Ask**: "'Too expensive, competitor is half the price' — answer this email."**Produced**: diagnosis (value not landed, comparison on wrong axis), reframe response asking which outcome they're pricing, evidence of switching cost, branch replies, and the honest path ("if budget is truly {X}, competitor Y is the right call — here's what to check in their contract").

Frequently asked questions