agentleFS
aziznizomofficialaziznizomofficial/hormozi-brain/skills/hormozi-offer/SKILL.md

hormozi-offer

Skill2 starsChanged 49 days agoMITView on GitHub

Build a Grand Slam Offer with Alex Hormozi's $100M Offers method — dream outcome, problems → solutions, delivery vehicles, value stack, pricing, guarantee, scarcity/urgency, bonuses, naming — grounded in the book with page refs. Use for /hormozi-offer or "make my offer irresistible".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. alexsmedile/hormozi-skills★ 208same name

    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 repository4 other files it gives its agents.

The file

Files
SKILL.md

Grand Slam Offer builder

Uses the same map and voice as the hormozi skill: read ../hormozi/SKILL.md and ../hormozi/references/voice.md (relative to this skill's folder) first. CLI: h() { python3 "<this skill folder>/../hormozi/scripts/hormozi.py" "$@"; } (the hormozi skill sits next to this one). Before each step, read the matching framework card (h frameworks <slug>) and cite its pages.

Steps — show your work at each, and ask the user to confirm or correct before moving on when their input changes the result:

  1. Market check — is the market starving (pain, purchasing power, easy to target, growing)? Pick the niche.
  2. Dream outcome — in the buyer's words, with a number and a timeframe.
  3. Problems list — every obstacle before, during and after, including the fears.
  4. Solutions — flip each problem into a "how to…" solution.
  5. Delivery vehicles — for each solution, cost-to-deliver vs value; trim and stack.
  6. Value equation check — raise dream outcome and likelihood, cut time delay and effort. Score each 1–10.
  7. Pricing — price on value, not cost; show the price vs value gap.
  8. Enhancers — scarcity, urgency, bonuses (each with its own value), guarantee type, name (use his naming formula).
  9. Output — one-page offer: headline name, who it's for, what they get (stack with values), price, guarantee, urgency, plus a 30-second verbal pitch. Save to ~/Documents/Hormozi Reports/offer-<name>-<date>.md.

Answer in the user's language; keep framework names in English. Always run h search in English, whatever language the user writes in.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.