hormozi-pitch
Skill12 starsChanged 4 months agoMITView on GitHub
Turn an offer into a compelling Hormozi-style pitch ready for launch or sales. Use when creating a new pitch, improving a weak offer, or preparing for a launch. Builds value stack, guarantee options, scarcity and urgency elements, objection handling, offer name variations, and short/medium/long pitch versions - outputs PITCH.md.
1 other project uses a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- alexsmedile/hormozi-skillsedited, first seen Aug 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 1
- alexsmedile/hormozi-skills★ 208100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository110 other files it gives its agents.
- .github/copilot-instructions.mdCopilot instructions
- 30mpc-voiceSkill
- adam-robinson-voiceSkill
- ai-workflow-architectSkill
- alex-costa-grooming-advisorSkill
- alex-garcia-voiceSkill
- alex-hormozi-voiceSkill
- amanda-natividad-voiceSkill
- andrew-gazdecki-voiceSkill
- andrew-wilkinson-voiceSkill
- ann-handley-voiceSkill
- april-dunford-voiceSkill
- automation-pricing-and-closeSkill
- balaji-srinivasan-voiceSkill
- barbara-corcoran-voiceSkill
- bob-hoffman-voiceSkill
- byron-sharp-voiceSkill
- chamath-strategy-coachSkill
- chris-orlob-voiceSkill
- chris-walker-voiceSkill
- claude-code-build-auditorSkill
- claude-hopkins-voiceSkill
- codie-sanchez-voiceSkill
- daniel-priestley-voiceSkill
- dan-kennedy-voiceSkill
- dan-koe-voiceSkill
- dave-gerhardt-voiceSkill
- david-ogilvy-voiceSkill
- david-perell-voiceSkill
- dhh-voiceSkill
- first-client-90-day-planSkill
- first-client-offer-builderSkill
- first-meeting-30-day-sprintSkill
- fletch-pmm-voiceSkill
- founder-content-engineSkill
- gary-bencivenga-voiceSkill
- gary-halbert-voiceSkill
- gary-vaynerchuk-voiceSkill
- george-mack-voiceSkill
- grant-cardone-voiceSkill
- greg-isenberg-voiceSkill
- guillaume-moubeche-voiceSkill
- harry-dry-voiceSkill
- hormozi-hooksSkill
- hundred-million-offersSkill
- icp-validation-sprintSkill
- jack-butcher-voiceSkill
- jasmin-alic-voiceSkill
- jason-fried-voiceSkill
- jay-clouse-voiceSkill
- jen-allen-knuth-voiceSkill
- jesse-itzler-voiceSkill
- john-carlton-voiceSkill
- josh-braun-voiceSkill
- julian-shapiro-voiceSkill
- justin-welsh-voiceSkill
- katelyn-bourgoin-voiceSkill
- kellen-copy-coachSkill
- kevin-dorsey-voiceSkill
- kevin-oleary-voiceSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
create a new offer pitch
- Distinctive: line 82
Do you have results, testimonials, or case studies?
- Distinctive: line 97
Use Alex Hormozi’s Value Equation framework:
- Distinctive: line 182
Only if it fits.
- Distinctive: line 210
Use the MAGIC format:
- Distinctive: line 216
Add a container word
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill: Build a Hormozi-Style Pitch
Purpose
Turn an idea, product, service, or existing offer into a clear, compelling pitch that feels easy to say yes to.
This skill focuses on:
- sharpening the value proposition
- increasing perceived value
- reducing friction and risk
- structuring the offer so it feels obvious to buy
- producing a ready-to-use pitch
When to Use
Activate this skill when the user wants to:
- create a new offer pitch
- improve a weak or unclear offer
- increase conversions
- structure pricing and guarantees
- make an offer feel more valuable
- prepare for launch or sales
Inputs
The skill can start from:
- a raw idea
- a rough offer
- an existing product or service
- an
OFFER.mddocument - a sales page draft
- a short description like “I sell X to Y”
Core Outcome
The assistant produces:
- a strong offer name
- a clear value proposition
- a structured value stack
- pricing logic
- a guarantee
- urgency and scarcity elements
- objection handling
- a complete pitch (short + long version)
Assistant Behavior
1. Understand the offer first
Extract:
- who the offer is for
- what result it promises
- how it is delivered
- current price (if any)
- what feels weak, vague, or generic
Reflect back in simple terms.
Example:
You’re helping X get Y result through Z format. The outcome is still a bit broad, and the value isn’t fully clear yet.
2. Ask clarifying questions (only if needed)
Focus on gaps:
Customer & Outcome
- What result matters most to your customer?
- What makes them act now?
- What does success look like in real life?
Proof & Trust
- Do you have results, testimonials, or case studies?
- What makes you credible for this?
Offer Mechanics
- What exactly do they get?
- How fast can they see a result?
- What support do they receive?
Constraints
- Price range?
- Platform (Instagram, calls, email, landing page)?
3. Diagnose using the Value Equation
Use Alex Hormozi’s Value Equation framework:
Value = (Dream Outcome × Perceived Likelihood) / (Time Delay × Effort & Sacrifice)
Break the offer into 4 parts:
Dream Outcome
- Is it clear?
- Is it specific?
- Is it desirable?
Perceived Likelihood
- Why should they believe this will work?
- Is proof visible?
- Is the path clear?
Time Delay
- How fast do they get a win?
- Can this be shortened?
Effort & Sacrifice
- How hard does it feel?
- Can steps be removed, simplified, or done for them?
Then explain where the offer is weak and how to improve it.
4. Improve the offer before pitching
Suggest upgrades:
- make outcome more specific
- reduce time to first result
- add proof mechanisms
- simplify delivery
- remove friction
- increase perceived ease
If needed, propose:
- different format (DFY, DWY, DIY)
- different price positioning
- different scope
5. Build the Value Stack
List all components:
For each:
- name
- what it does
- why it matters
- perceived value
Then:
- separate core offer vs bonuses
- stack bonuses in logical order
- calculate total value
- compare with actual price
Goal: create a strong gap between value and price.
6. Design the Guarantee
Generate 3-4 options:
- unconditional (money-back)
- conditional (action-based)
- outcome-based (results-tied)
- anti-risk (you keep helping until result)
For each:
- give it a name
- write exact wording
- explain risk level
Then recommend the best one based on:
- price
- complexity
- trust level
7. Add Scarcity & Urgency
Only if it fits.
Options:
- limited spots
- limited time
- fast-action bonuses
- deadline pricing
- cohort start date
Explain why the constraint exists. Avoid fake scarcity.
8. Handle Objections
List main objections:
- “Will this work for me?”
- “Is it worth the price?”
- “Do I have time?”
- “What if it doesn’t work?”
Then write short responses that:
- reduce doubt
- increase clarity
- reinforce value
9. Create the Offer Name
Use the MAGIC format:
- Make it about them
- Announce the avatar
- Give a goal
- Indicate a time frame
- Add a container word
Generate 5-10 variations.
10. Write the Pitch
Short Version (for ads, bios, hooks)
- 1-2 lines
- clear outcome
- specific audience
- time or mechanism
Medium Version (for landing page)
- problem
- promise
- what they get
- why it works
- CTA
Long Version (full pitch)
- callout to audience
- pain amplification
- desired outcome
- solution explanation
- value stack
- price vs value contrast
- guarantee
- urgency
- CTA
Output Format
# PITCH.md
## 1. Offer Summary
- Who it’s for
- What it helps them achieve
- How it works
## 2. Value Equation Breakdown
- Dream Outcome
- Perceived Likelihood
- Time Delay
- Effort & Sacrifice
- Key improvements made
## 3. Offer Name Options
- Name 1
- Name 2
- Name 3
## 4. Core Offer
- What’s included
- Format
- Delivery
## 5. Bonus Stack
- Bonus
- Purpose
- Value
## 6. Value Stack
- Total value
- Price
- Price justification
## 7. Guarantee
- Option 1
- Option 2
- Option 3
- Recommended guarantee
## 8. Scarcity & Urgency
- Mechanism
- Reason
## 9. Objection Handling
- Objection → Response
## 10. Pitch
### Short Version
...
### Medium Version
...
### Long Version
...⸻
Decision Rules
Strengthen outcome when: • it sounds vague • it’s not measurable • it lacks urgency
Increase belief when: • there is no proof • the claim feels too big • the path is unclear
Reduce friction when: • the process feels complex • too much effort is required • the user must figure things out alone
Add value when: • price feels high vs clarity • offer feels empty • differentiation is weak
⸻
Style Guidelines • clear and direct • specific outcomes • simple language • no hype tone • no vague claims • always grounded in what the buyer wants
⸻
Success Criteria
The pitch works when: • the outcome is clear in seconds • the buyer feels understood • the value feels higher than the price • risk feels low • objections are already answered • the next step feels easy
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

