From hormozi-skills
Design a bonus stack that kills objections and increases perceived value. Use when the offer feels weak, price resistance is high, or conversions are low. Maps objections to bonus solutions, assigns delivery formats and perceived values, and outputs a structured bonus stack.
How this skill is triggered — by the user, by Claude, or both
Slash command
/hormozi-skills:bonus-stackThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design bonuses that increase perceived value and remove reasons to say no.
Design bonuses that increase perceived value and remove reasons to say no.
This skill:
Goal: make the buyer think
“I’d be stupid not to take this”
Activate this skill when:
This skill works with:
OFFER.mdThe assistant produces:
List the main reasons someone would not buy:
Common objections:
If not provided, infer based on:
For each objection, define:
Objection → What removes it
Example:
Convert each solution into a tangible asset.
Format:
Examples:
For each bonus:
Bad:
Good:
Assign formats that feel valuable:
Options:
Prefer:
Order matters.
Structure:
Estimate perceived value:
Then:
Too many bonuses reduce clarity.
Rules:
Ensure:
Add urgency if needed:
# BONUS_STACK.md
## 1. Core Offer Summary
- What the offer does
- Who it’s for
## 2. Key Objections
1. Objection
2. Objection
3. Objection
## 3. Objection → Bonus Mapping
- Objection → Bonus idea
## 4. Bonus Stack
### Bonus 1
- Name
- What it does
- Outcome
- Format
- Value
### Bonus 2
- Name
- What it does
- Outcome
- Format
- Value
### Bonus 3
- Name
- What it does
- Outcome
- Format
- Value
## 5. Total Bonus Value
- Sum of all bonuses
## 6. Stack Strategy
- Why this order
- What objections are removed
## 7. Optional Fast Action Bonuses
- Bonus
- Condition (time/limit)
## 8. Final Notes
- What was removed
- Why this stack works
⸻
Decision Rules
Add a bonus when: • it removes a clear objection • it increases speed or ease • it improves perceived value
Avoid a bonus when: • it adds confusion • it’s low value • it doesn’t support the outcome
Prioritize bonuses that: • save time • reduce effort • increase certainty • simplify execution
⸻
Before vs After Example
Before • core product only
After • core product • • templates • • checklist • • audit • • support
⸻
Style Guidelines • be specific • focus on outcomes • avoid generic names • keep it clean • prioritize value over quantity
⸻
Success Criteria
The skill works when: • objections are neutralized • value feels higher than price • the offer feels complete • the buyer has fewer doubts • conversions increase
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub alexsmedile/hormozi-skills --plugin hormozi-skills