agentleFS
alexsmedilealexsmedile/hormozi-skills/skills/audit-offer/SKILL.md

audit-offer

Skill208 starsChanged 3 months agoMITView on GitHub

Audit an offer to find weak points and get specific fixes. Use when an offer is not converting, conversions are low, or something feels off. Analyzes dream outcome, perceived likelihood, time delay, effort, market fit, value stack, pricing, messaging, and objections using the Hormozi Value Equation framework.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    when the first win occurs

    line 115

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Offer Audit (Weak Point Detector)

Purpose

Analyze any offer and identify what is stopping it from converting.

This skill:

  • finds weak points
  • diagnoses why the offer underperforms
  • suggests clear, practical fixes

Goal: turn a weak or average offer into a strong, obvious buy.


When to Use

Activate this skill when:

  • an offer is not selling
  • conversions are low
  • feedback is unclear or vague
  • something feels “off” but you don’t know what
  • you want to improve an existing offer

Inputs

This skill works with:

  • an OFFER.md
  • a sales page
  • a pitch
  • a product or service description
  • pricing and value stack
  • audience description

Core Outcome

The assistant produces:

  • a full diagnosis of the offer
  • a list of weak points
  • severity level for each issue
  • specific fixes
  • prioritized action plan

Audit Framework (Hormozi-Based)

The audit is based on:

  • Dream Outcome
  • Perceived Likelihood
  • Time Delay
  • Effort & Sacrifice

Plus:

  • market clarity
  • offer clarity
  • delivery model
  • value stack
  • pricing
  • messaging

Assistant Behavior

1. Extract the offer

Identify:

  • who it’s for
  • what it promises
  • how it works
  • price
  • format

Summarize:

This offer helps X achieve Y using Z.


2. Evaluate Dream Outcome

Check:

  • is the result clear?
  • is it specific?
  • is it desirable?
  • is it urgent?

Weak signs:

  • vague outcomes (“grow”, “improve”)
  • no measurable result

3. Evaluate Perceived Likelihood

Check:

  • is there proof?
  • is the path clear?
  • is it believable?

Weak signs:

  • no testimonials
  • unclear process
  • big promises without support

4. Evaluate Time Delay

Check:

  • how fast results happen
  • when the first win occurs

Weak signs:

  • long delay before results
  • no quick wins

5. Evaluate Effort & Sacrifice

Check:

  • how hard it feels
  • how many steps are required
  • how much discipline is needed

Weak signs:

  • too many steps
  • unclear instructions
  • heavy effort

6. Evaluate Market Fit

Check:

  • is the audience specific?
  • is the pain urgent?
  • can they pay?

Weak signs:

  • “everyone” target
  • low urgency problems

7. Evaluate Offer Structure

Check:

  • is the offer easy to understand?
  • is the structure clear?
  • does it feel complete?

Weak signs:

  • messy structure
  • unclear components
  • missing elements

8. Evaluate Value Stack

Check:

  • is value clearly shown?
  • are bonuses meaningful?
  • is there a gap between value and price?

Weak signs:

  • weak bonuses
  • no stacking
  • unclear value

9. Evaluate Pricing

Check:

  • does price match value?
  • is it justified?
  • does it feel cheap or expensive?

Weak signs:

  • random pricing
  • no anchoring
  • mismatch with outcome

10. Evaluate Messaging

Check:

  • is it clear?
  • is it specific?
  • is it outcome-focused?

Weak signs:

  • generic language
  • unclear benefits
  • no strong hooks

11. Evaluate Objections

Check:

  • are objections handled?
  • is risk reduced?
  • is trust built?

Weak signs:

  • no guarantee
  • no objection handling
  • unanswered doubts

Output Format

# OFFER_AUDIT.md

## 1. Offer Summary
- Who it’s for
- What it promises
- How it works
- Price

---

## 2. Overall Diagnosis
- Strengths
- Weaknesses

---

## 3. Value Equation Analysis

### Dream Outcome
- Score:
- Issues:
- Fixes:

### Perceived Likelihood
- Score:
- Issues:
- Fixes:

### Time Delay
- Score:
- Issues:
- Fixes:

### Effort & Sacrifice
- Score:
- Issues:
- Fixes:

---

## 4. Market Fit
- Issues:
- Fixes:

---

## 5. Offer Structure
- Issues:
- Fixes:

---

## 6. Value Stack
- Issues:
- Fixes:

---

## 7. Pricing
- Issues:
- Fixes:

---

## 8. Messaging
- Issues:
- Fixes:

---

## 9. Objections & Trust
- Issues:
- Fixes:

---

## 10. Top Priority Fixes
1. Fix
2. Fix
3. Fix

---

## 11. Quick Wins
- Fast improvements to implement immediately


⸻

Scoring System (Optional)

Each category scored 1–10:
	•	1–3 = critical issue
	•	4–6 = needs improvement
	•	7–8 = solid
	•	9–10 = strong

⸻

Decision Rules

Fix outcome first when:
	•	it’s unclear
	•	it’s not compelling

Add proof when:
	•	trust is low
	•	claims feel weak

Reduce effort when:
	•	execution feels heavy
	•	drop-off is high

Reduce time when:
	•	results feel far away
	•	motivation is low

Improve messaging when:
	•	people don’t understand quickly
	•	hooks feel weak

⸻

Before vs After Example

Before
	•	unclear offer
	•	weak value
	•	low conversions

After
	•	clear outcome
	•	strong value stack
	•	better positioning
	•	higher conversions

⸻

Style Guidelines
	•	direct and honest
	•	no fluff
	•	clear problems and fixes
	•	actionable insights

⸻

Success Criteria

The skill works when:
	•	weak points are obvious
	•	fixes are clear and actionable
	•	the offer becomes stronger
	•	conversions improve

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.