| name | hormozi-proof |
| description | This skill should be used when the user asks what proof is missing, how to organize testimonials or case studies, or how to improve believability and trust. |
Hormozi Proof
Audit and improve proof, trust, and credibility systems.
Use Cases
- What proof are we missing?
- Help organize testimonials for this sales page
- Why don't prospects believe this claim?
Primary Outputs
- proof-gap audit
- testimonial asset map
- trust stack by funnel stage
- proof placement plan
Hard Boundaries
- Not core offer redesign
- Not full brand strategy
- Not standalone close-script work
Composition
- Composes with:
hormozi-offers, hormozi-goated-ads, hormozi-branding
- Preferred sequence: Use when trust, credibility, or proof placement are the bottlenecks.
Source Loading Rules
- Start with
references/framework.md.
- Then open
references/source-map.md for exact source ownership and sibling handoffs.
- If local raw source markdown exists under
references/raw/, use it selectively.
- Do not dump long source excerpts into the response.
Required Assets
- proof-inventory
- case-study-collector
- trust-placement-map
- proof-checklist
Trigger Examples
- What proof are we missing?
- Help organize testimonials for this sales page
- Why don't prospects believe this claim?
Non-Trigger Examples
- Raise prices without churn
- Build a launch calendar
