
Value Perception
- 28 installs
- 97 repo stars
- Updated July 8, 2026
- alexsmedile/hormozi-skills
Value Perception is a Claude skill that raises how valuable an offer feels without adding cost by upgrading naming, packaging, framing, value stacking, and anchoring.
About
This skill increases how valuable an offer feels without increasing its cost. It upgrades naming, packaging, framing, value stacking, anchoring, and contrast, and exposes hidden value. A developer uses it when an offer is good but not converting, the price feels high, or users do not grasp the value instantly. It outputs a VALUE_PERCEPTION.md file.
- Increases perceived value without adding cost via naming, packaging, and framing
- Improves value stacking, anchoring, and before/after contrast
- Exposes hidden value and reduces cognitive load, outputting VALUE_PERCEPTION.md
Value Perception by the numbers
- 28 all-time installs (skills.sh)
- Ranked #617 of 853 Sales & Marketing skills by installs in the Skillselion catalog
- Data as of Aug 5, 2026 (Skillselion catalog sync)
value-perception capabilities & compatibility
- Capabilities
- pricing strategy · offer angles · objection destroyer · landing page copy
- Use cases
- copywriting · marketing
What value-perception says it does
Increase how valuable the offer *feels* without increasing cost.
Same offer → better perception → higher conversions
npx skills add https://github.com/alexsmedile/hormozi-skills --skill value-perceptionAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 28 |
|---|---|
| repo stars | ★ 97 |
| Last updated | July 8, 2026 |
| Repository | alexsmedile/hormozi-skills ↗ |
What it does
Raise an offer's perceived value through naming, packaging, framing, and anchoring.
Who is it for?
Making an offer feel more valuable through packaging and framing
When should I use this skill?
The offer is good but not converting, price feels high, or value is not understood instantly
What you get
Upgraded naming, packaging, framing, and anchoring in VALUE_PERCEPTION.md
- VALUE_PERCEPTION.md
By the numbers
- 5-10 improved names for offer, modules, and bonuses
Files
Skill: Value Perception Booster (Psychology Layer)
Purpose
Increase how valuable the offer feels without increasing cost.
This skill focuses on perception, not creation.
Same offer → better perception → higher conversions
It improves:
- willingness to pay
- clarity of value
- emotional impact
- decision speed
---
When to Use
Activate this skill when:
- the offer is good but not converting
- price feels “too high” for buyers
- the offer feels flat or generic
- users don’t “get it” instantly
- you want to increase perceived value without adding more
---
Inputs
This skill works with:
- an
OFFER.md - a value stack
- a pitch or sales page
- a product or service description
---
Core Outcome
The assistant produces:
- stronger naming
- clearer packaging
- better framing of value
- improved value stacking
- upgraded perception without extra cost
---
Assistant Behavior
1. Identify current perception gaps
Analyze:
- does the offer feel generic?
- is the value easy to understand?
- is the outcome visible?
- does it feel premium or basic?
Then summarize:
The value exists, but it is not clearly communicated or felt.
---
Core Levers
---
2. Naming Optimization
Names shape perception.
Weak names feel cheap. Strong names feel valuable.
Upgrade:
- generic → specific
- vague → outcome-based
- technical → benefit-driven
Bad:
- “Course”
- “Program”
- “Template pack”
Better:
- “30-Day Client Acquisition System”
- “Plug-and-Play Growth Engine”
- “First Sale Starter Kit”
Output:
- 5–10 improved names for:
- offer
- modules
- bonuses
---
3. Packaging Upgrade
Same content, better structure.
Improve:
- how components are grouped
- how they are presented
- how they are introduced
Shift from:
- list of items
To:
- structured system
Example:
- instead of “videos + templates”
→ “3-Step Growth System”
Output:
- renamed sections
- grouped components
- clearer structure
---
4. Framing the Value
How you describe the offer changes how it feels.
Reframe:
- features → outcomes
- content → results
- effort → ease
- time → speed
Example:
- “10 video lessons”
→ “Step-by-step system to get your first client”
Output:
- rewritten descriptions
- outcome-focused explanations
---
5. Value Stacking
Stack value visually and logically.
Instead of:
- flat list
Use:
- layered structure
- increasing importance
- clear progression
Example: 1. Core system 2. Execution tools 3. Support layer 4. bonuses
Output:
- improved value stack order
- clearer separation of components
---
6. Anchoring Techniques
Increase perceived value through comparison.
Methods:
- show total value first
- compare to alternatives
- show cost of inaction
- highlight time saved
Example:
- “Hiring someone would cost $2,000+”
- “This replaces months of trial and error”
---
7. Contrast & Clarity
Value feels higher when contrast is clear.
Improve:
- before vs after
- problem vs solution
- slow vs fast
- hard vs easy
Output:
- simple contrasts that highlight transformation
---
8. Reduce Cognitive Load
Confusion lowers perceived value.
Simplify:
- fewer words
- clearer structure
- visible steps
- obvious outcome
---
9. Highlight “Hidden Value”
Expose what users don’t notice.
Examples:
- time saved
- mistakes avoided
- shortcuts included
- experience embedded
Output:
- list of hidden value points made explicit
---
10. Upgrade Presentation
Even text structure matters.
Improve:
- spacing
- hierarchy
- order of information
- emphasis on key points
---
Output Format
# 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
Related skills
FAQ
What does value-perception change?
It changes perception, not the product: naming, packaging, framing, value stacking, anchoring, and contrast, output in VALUE_PERCEPTION.md.
When should I use it?
When the offer is good but not converting, the price feels too high, or buyers do not grasp the value instantly.