About objection-destroyer
objection-destroyer is a sales and marketing skill that examines the beliefs behind customer objections and turns them into usable responses. It combines reframing, supporting proof, and suggestions for offer changes across sales copy, calls, and messages.
Key features
- 01Identify visible and hidden customer objections
- 02Group objections by value, trust, effort, and other themes
- 03Reframe limiting beliefs into alternative beliefs
- 04Match reframed beliefs with proof or a mechanism
- 05Prioritize objections and create reusable responses
Use cases
- 01Analyze recurring objections in sales call notes
- 02Adapt sales pages or direct messages to customer feedback
- 03Find offer areas that need more proof or less friction
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ alexsmedile/ hormozi-skills --skill objection-destroyerAfter installing, type/objection-destroyerin Claude Code to confirm it loaded.
Details
From the project READMESkill: Objection Destroyer (Belief Shift Engine)
Purpose
Turn objections into reasons to buy.
This skill:
- uncovers hidden resistance
- translates doubt into clarity
- shifts beliefs instead of pushing harder
- increases trust and conversions
Goal: remove every internal “no” before it appears.
When to Use
Activate this skill when:
- people hesitate but don’t say why
- conversions are lower than expected
- buyers say “I’ll think about it”
- the offer is strong but still not selling
- objections repeat in DMs or calls
- trust feels low
Inputs
This skill works with:
- an
OFFER.md - a pitch or sales page
- customer feedback
- sales call notes
- known objections (or none → infer them)
Core Outcome
The assistant produces:
- a list of visible and hidden objections
- the belief behind each objection
- a reframed belief (belief shift)
- proof or mechanism to support the new belief
- objection-handling statements ready to use
Assistant Behavior
1. Identify surface objections
List obvious objections:
Common:
- “It’s too expensive”
- “I don’t have time”
- “This won’t work for me”
- “I need to think about it”
- “I can do it myself”
2. Uncover hidden objections
Go deeper.
Each objection hides a belief.
Example:
- “Too expensive” → “I’m not sure it’s worth it”
- “No time” → “This will take too much effort”
- “I’ll think about it” → “I don’t trust this yet”
Map: Objection → Hidden belief
3. Categorize objections
Group into:
Value
- not worth the price
Trust
- won’t work
- lacks proof
Effort
- too hard
- too complex
Time
- takes too long
Identity
- “this is not for me”
Risk
- fear of failure or loss
4. Create belief shifts
Replace limiting beliefs with stronger ones.
Format: Old belief → New belief
Example:
- “This is risky” → “This is a safe, guided path”
- “This takes too long” → “I can see results quickly”
Rules:
- simple
- believable
- grounded in reality
5. Attach proof to each belief
A belief without proof fails.
Use:
- testimonials
- case studies
- examples
- logic
- demonstration
- mechanism explanation
Format: Belief shift → Proof
6. Rewrite as selling points
Turn objections into persuasive statements.
Format: Objection → Reframe → Proof
Example:
- “I don’t have time” → “This is designed to save you time” → “Most users get their first result in under 30 minutes using the template”
7. Integrate into offer
Place objection handling in:
- sales page
- pitch
- content
- FAQs
- DMs
Make it proactive, not reactive.
8. Strengthen weak areas
If objections repeat, improve the offer:
- add proof
- simplify process
- reduce effort
- clarify outcome
- improve guarantee
9. Prioritize key objections
Focus on:
- top 3–5 objections
- highest impact on buying decision
Avoid overloading.
10. Create reusable responses
Generate:
- short answers (DMs)
- medium answers (landing page)
- long explanations (sales page)
Output Format
# OBJECTIONS.md
## 1. Surface Objections
1. Objection
2. Objection
3. Objection
## 2. Hidden Beliefs
- Objection → Underlying belief
## 3. Objection Categories
- Value
- Trust
- Effort
- Time
- Identity
- Risk
## 4. Belief Shifts
- Old belief → New belief
## 5. Proof Mapping
- Belief shift → Proof
## 6. Objection Handling Statements
### Objection 1
- Objection:
- Reframe:
- Proof:
### Objection 2
- Objection:
- Reframe:
- Proof:
### Objection 3
- Objection:
- Reframe:
- Proof:
## 7. Top Objections to Address
- Priority list
## 8. Integration Points
- Where to use each response
## 9. Offer Improvements Needed
- What to fix in the offer
## 10. Short Responses (DM-ready)
- Quick replies
⸻
Decision Rules
Go deeper when: • objections sound generic • users are vague • “I’ll think about it” appears often
Add proof when: • trust is low • claims feel strong • results seem uncertain
Reframe when: • objection is emotional • logic alone is not enough
Fix the offer when: • objection is valid • friction is real • results are unclear
⸻
Before vs After Example
Before • “It’s too expensive”
After • “This replaces months of trial and error and helps you get your first result fast, which makes the investment small compared to the outcome”
⸻
Style Guidelines • be clear and direct • avoid defensive tone • focus on belief, not argument • keep it simple • support claims with proof
⸻
Success Criteria
The skill works when: • objections are addressed before they arise • buyers feel understood • trust increases • hesitation decreases • conversions improve