audit-offer
Audit an offer to find weak points and get specific fixes. Use when an offer is not converting, conversions are low, or something…
Increase how valuable an offer feels without increasing cost. Use when the offer is good but not converting, price feels too high, or users don't understand the value instantly. Upgrades naming, packaging, framing, value stacking, anchoring, and contrast to improve perceived
$ npx -y skills add alexsmedile/hormozi-skills --skill value-perception --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/value-perceptionContext preview
The summary Claude sees to decide when to auto-load this skill.
Increase how valuable an offer feels without increasing cost. Use when the offer is good but not converting, price feels too high, or users don't understand the value instantly. Upgrades naming, packaging, framing, value stacking, anchoring, and contrast to improve perceived
name: value-perception description: Increase how valuable an offer feels without increasing cost. Use when the offer is good but not converting, price feels too high, or users don't understand the value instantly. Upgrades naming, packaging, framing, value stacking, anchoring, and contrast to improve perceived value — outputs VALUE_PERCEPTION.md.
Increase how valuable the offer *feels* without increasing cost.
This skill focuses on perception, not creation.
Same offer → better perception → higher conversions
It improves:
---
Activate this skill when:
---
This skill works with:
---
The assistant produces:
---
Analyze:
Then summarize:
> The value exists, but it is not clearly communicated or felt.
---
---
Names shape perception.
Weak names feel cheap. Strong names feel valuable.
Upgrade:
Bad:
Better:
Output:
---
Same content, better structure.
Improve:
Shift from:
To:
Example:
→ “3-Step Growth System”
Output:
---
How you describe the offer changes how it feels.
Reframe:
Example:
→ “Step-by-step system to get your first client”
Output:
---
Stack value visually and logically.
Instead of:
Use:
Example: 1. Core system 2. Execution tools 3. Support layer 4. bonuses
Output:
---
Increase perceived value through comparison.
Methods:
Example:
---
Value feels higher when contrast is clear.
Improve:
Output:
---
Confusion lowers perceived value.
Simplify:
---
Expose what users don’t notice.
Examples:
Output:
---
Even text structure matters.
Improve:
---
# VALUE_PERCEPTION.md ## 1. Current Perception Issues - What feels weak - What is unclear ## 2. Naming Improvements - Offer name options - Component names - Bonus names ## 3. Packaging Upgrade - New structure - Grouped components - System naming ## 4. Value Framing - Before (weak description) - After (improved framing) ## 5. Value Stack Optimization - New order - Clear layers - Improved presentation ## 6. Anchoring Improvements - Comparisons - Value references ## 7. Contrast Enhancements - Before vs after - Problem vs solution ## 8. Hidden Value Highlights - What was implicit → now explicit ## 9. Simplicity Improvements - What was simplified - Why it helps ## 10. Final Perception Upgrade - Summary of improvements - Why the offer now feels more valuable
⸻
Decision Rules
Improve naming when: • it sounds generic • it lacks outcome • it feels low-value
Improve framing when: • value is not obvious • features dominate the message • outcome is buried
Improve stacking when: • everything feels equal • no hierarchy exists • value is hard to scan
Add anchors when: • price feels high • value is not contextualized • alternatives are unclear
⸻
Before vs After Example
Before • “Online course with templates”
After • “Client Acquisition System with plug-and-play templates and execution roadmap”
⸻
Style Guidelines • be clear, not clever • focus on outcomes • make value visible • reduce complexity • highlight transformation
⸻
Success Criteria
The skill works when: • the offer feels more valuable without adding cost • buyers understand value faster • price feels more justified • messaging feels sharper • conversions improve
Turn any business idea into a complete, sellable offer — using Alex Hormozi's frameworks. A skill library for coding agents.
Audit an offer to find weak points and get specific fixes. Use when an offer is not converting, conversions are low, or something…
Design a bonus stack that kills objections and increases perceived value. Use when the offer feels weak, price resistance is…
Design the right business model for monetizing skills and expertise. Use when unsure what to sell, stuck between service vs…
This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create…
Choose the best delivery mechanism for an offer — Done For You, Done With You, or Do It Yourself. Use when the offer exists but…
Reduce friction and effort in an offer to increase its perceived value. Use when users feel overwhelmed, drop-off is high, or the…