hormozi-diagnose
Skill2 starsChanged 49 days agoMITView on GitHub
Full Alex Hormozi-style business diagnosis — interview the owner, find the single constraint, and write a sourced action plan with the math. Use for /hormozi-diagnose, "audit my business like Hormozi", or when someone describes a stuck business and wants a full plan.
In this repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- hormozi-offerSkill
- hormozi-reviewSkill
- hormoziSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
If they point to a notes folder or file, read it instead of asking.
- Very specific: line 23
Place them on his scaling stages and the constraint for that stage (h search "scaling roadmap stage <n> constraint", and h frameworks for …
≈ “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
Hormozi diagnosis
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).
1. Intake — ask everything in one message, numbered, skip what is already known
- What do you sell, to whom, at what price? How is it delivered?
- Revenue per month and trend over the last 6 months. Gross margin %.
- New customers per month. Where do they come from (warm outreach, content, cold outreach, paid ads, referrals, affiliates)?
- Leads per month → booked → showed → closed (or site visits → purchases).
- CAC, average lifetime value / months retained, monthly churn.
- Team: who sells, who delivers, what the owner still does daily.
- The goal (number + date) and what they think is stuck.
If they point to a notes folder or file, read it instead of asking.
2. Analyse
- Compute: LTGP (lifetime gross profit) : CAC ratio, payback period, revenue ceiling = new customers per month ÷ churn rate, close rate.
- Place them on his scaling stages and the constraint for that stage (
h search "scaling roadmap stage <n> constraint", andh frameworksfor the stage cards). - Pick ONE constraint among: offer, price, leads (volume), conversion (sales), retention/churn, delivery capacity, team/owner time.
- Pull 8–14 searches across books, coaching calls and
--kind caseon that constraint and on businesses like theirs;getthe best hits.
3. Report (write to ~/Documents/Hormozi Reports/<business>-<YYYY-MM-DD>.md, and summarise in chat)
Sections: The verdict (one paragraph, blunt) · Your numbers (table) · The constraint and why · The plan (next 7 days, next 30, next 90 — concrete actions, owner and metric for each) · What NOT to do yet · The math (before/after) · Sources (book pages + timestamped videos).
Voice: his. Language: the user's. Always run h search in English, whatever language the user writes in.
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.

