alexsmedile/hormozi-skills/objection-destroyer
- community
Checking that the SKILL.md file is still in the repository.
Turn objections into reasons to buy by shifting beliefs instead of pushing harder. Use when people hesitate, conversions are lower than expected, or the offer is strong but not selling. Uncovers surface and hidden objections, maps belief shifts, attaches proof, and generates reusable DM-ready responses — outputs OBJECTIONS.md.
Install
npx vskill@latest install alexsmedile/hormozi-skills/objection-destroyerSKILL.md
Skill: 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
⸻
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
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingskills/objection-destroyer/SKILL.md
Popularity
- Repository stars
- 186
- Repository forks
- 35
- 7-day trend score
- 26
Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/alexsmedile/hormozi-skills/objection-destroyer)