audit-offer
Audit an offer to find weak points and get specific fixes. Use when an offer is not converting, conversions are low, or something…
Find the right market, extract real customer pain, and validate demand before building an offer. Use when you have an idea but no market, the niche feels too broad, or the offer is not converting. Generates micro-niches, scores them, extracts pain language, and creates a
$ npx -y skills add alexsmedile/hormozi-skills --skill market-research --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/market-researchContext preview
The summary Claude sees to decide when to auto-load this skill.
Find the right market, extract real customer pain, and validate demand before building an offer. Use when you have an idea but no market, the niche feels too broad, or the offer is not converting. Generates micro-niches, scores them, extracts pain language, and creates a
name: market-research description: Find the right market, extract real customer pain, and validate demand before building an offer. Use when you have an idea but no market, the niche feels too broad, or the offer is not converting. Generates micro-niches, scores them, extracts pain language, and creates a validation test plan — outputs MARKET_RESEARCH.md.
Find the right market, extract real pain, and validate demand before building an offer.
This skill prevents:
Goal: identify a **starving crowd with real pain and buying intent**.
---
Activate this skill when:
---
This skill works with:
---
The assistant produces:
---
Find a group of people who:
---
Extract:
---
Break broad markets into smaller groups:
Example:
---
Check:
---
Score 1–10:
---
Choose:
---
# MARKET_SELECTION.md ## 1. Idea - Description ## 2. Micro-Niches - Niche 1 - Niche 2 - Niche 3 ## 3. Niche Scoring - Pain: - Money: - Reach: - Growth: ## 4. Selected Niche - Final choice - Reasoning
⸻
PART 2: Pain Extraction Skill
Purpose
Understand what the customer actually feels.
⸻
Assistant Behavior
1. Identify core problems
List: • main frustrations • repeated struggles • emotional pain
⸻
2. Extract real language
Simulate or gather: • how customers describe the problem • informal phrasing • emotional expressions
⸻
3. Create pain bullets
Types:
Surface Pain • obvious problems
Deeper Pain • emotional impact
Hidden Pain • fears, doubts, frustrations
⸻
4. Generate “midnight thoughts”
What they think when: • stressed • frustrated • alone
⸻
Output Format
# CUSTOMER_PAIN.md ## 1. Core Problems - Problem 1 - Problem 2 ## 2. Raw Language - Phrases customers use ## 3. Pain Bullets - Surface pain - Deeper pain - Hidden pain ## 4. Emotional Triggers - Fear - Frustration - Desire ## 5. Midnight Thoughts - Thoughts they have at night
⸻
PART 3: Demand Validation Skill
Purpose
Confirm if the idea is worth building.
⸻
Assistant Behavior
1. Identify demand signals
Look for: • people asking questions • existing competitors • paid solutions already in market • repeated complaints
⸻
2. Classify audience
Split:
Buyers • already spend money • actively search for solutions
Browsers • interested but not paying
⸻
3. Evaluate demand strength
Score: • urgency • willingness to pay • competition level
⸻
4. Suggest validation tests
⸻
Pre-Sell Test • offer before building • gauge interest
⸻
Fake Door Test • landing page + CTA • measure clicks
⸻
Content Test • post hooks • track engagement
⸻
5. Create validation plan
Define: • what to test • how to test • success criteria
⸻
Output Format
# DEMAND_VALIDATION.md ## 1. Demand Signals - Evidence found ## 2. Buyer vs Browser - Buyers: - Browsers: ## 3. Demand Score - Urgency: - Willingness to pay: - Competition: ## 4. Validation Tests ### Test 1: Pre-Sell - Plan: ### Test 2: Fake Door - Plan: ### Test 3: Content - Plan: ## 5. Validation Criteria - What defines success
⸻
Combined Output
# MARKET_RESEARCH.md ## 1. Selected Market - Niche - Reasoning ## 2. Customer Pain - Pain bullets - Emotional triggers - Midnight thoughts ## 3. Demand Validation - Signals - Buyer vs browser - Test plan
⸻
Decision Rules
Choose a niche when: • pain is frequent • emotion is strong • money is available
Avoid markets when: • pain is weak • no urgency • no proof of spending
Trust demand when: • people pay already • solutions exist • complaints are frequent
⸻
Style Guidelines • be specific • use real language • focus on pain • avoid assumptions • prioritize clarity
⸻
Success Criteria
The skill works when: • a clear niche is selected • pain is deeply understood • demand is validated • idea feels worth pursuing
Turn any business idea into a complete, sellable offer — using Alex Hormozi's frameworks. A skill library for coding agents.
Audit an offer to find weak points and get specific fixes. Use when an offer is not converting, conversions are low, or something…
Design a bonus stack that kills objections and increases perceived value. Use when the offer feels weak, price resistance is…
Design the right business model for monetizing skills and expertise. Use when unsure what to sell, stuck between service vs…
This skill should be used when the user asks to "create a plugin", "make a GitHub plugin", "turn my repo into a plugin", "create…
Choose the best delivery mechanism for an offer — Done For You, Done With You, or Do It Yourself. Use when the offer exists but…
Reduce friction and effort in an offer to increase its perceived value. Use when users feel overwhelmed, drop-off is high, or the…