agentleFS
alexsmedilealexsmedile/hormozi-skills/skills/landing-page-copy/SKILL.md

landing-page-copy

Skill208 starsChanged 3 months agoMITView on GitHub

Build a high-converting Hormozi-style landing page from an offer or pitch. Use when you need a sales page, conversions are low, or messaging feels scattered. Structures hero, problem, outcome, solution, mechanism, value stack, proof, objection handling, guarantee, CTA, and FAQ sections — outputs LANDING_PAGE.md.

14 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use direct-response-copy.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MoizIbnYousafSkill

    direct-response-copy

    Write copy that converts. Use when writing landing pages, emails, sales copy, headlines, CTAs, social posts, cold emails, or any persuasive text. Triggers on 'copy', 'copywriting', 'sales copy', 'landing page copy', 'cold email', 'headlines', 'write me a page', 'make this convert', 'rewrite this copy', or any request involving persuasive writing. Three modes: Generate (write from scratch), Edit (improve existing copy with Seven Sweeps), Cold Email (outbound sequences). If someone has text that needs to sell harder, this is the skill.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 14 edited versions we read keep these.

  • 4

    Distinctive

    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:

    remove objections before CTA

    line 60
  2. Distinctive:

    use logic or demonstration

    line 171
  3. Distinctive:

    Do not isolate them only in one section.

    line 273
  4. Distinctive:

    Before vs After Example

    line 406

“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “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: Landing Page Builder (Hormozi-Style)

Purpose

Turn an offer and pitch into a high-converting landing page.

This skill:

  • structures the page logically
  • writes clear, outcome-driven copy
  • removes friction and objections
  • guides the reader to take action

Goal: make the page easy to scan, easy to trust, easy to buy.


When to Use

Activate this skill when:

  • you have an offer or pitch ready
  • you need a sales page or landing page
  • conversions are low
  • messaging feels scattered
  • you want a clear structure to follow

Inputs

This skill works with:

  • OFFER.md
  • PITCH.md
  • hooks
  • value stack
  • objections
  • target audience

Core Outcome

The assistant produces:

  • a full landing page structure
  • clear section breakdown
  • copy for each section
  • strong CTA placement
  • objection handling integrated
  • a page ready to build or publish

Core Principles (Hormozi Style)

  • clarity > cleverness
  • outcome first
  • reduce friction early
  • show value before price
  • stack value visually
  • remove objections before CTA
  • make scanning easy
  • short sections, clear flow

Landing Page Structure


1. Hero Section (Above the Fold)

Goal: grab attention and make the reader stay

Include:

  • hook
  • clear outcome
  • audience callout
  • speed/ease
  • primary CTA

Format:

  • headline
  • subheadline
  • CTA button

2. Problem Section

Goal: make the reader feel understood

Include:

  • current struggles
  • frustrations
  • failed attempts
  • emotional pain

Make it specific and relatable.


3. Outcome Section

Goal: show the desired future

Include:

  • clear result
  • transformation
  • what life looks like after

Make it visual and concrete.


4. Solution Section

Goal: introduce the offer

Include:

  • what the product/service is
  • how it works (simple)
  • why it works

Avoid complexity.


5. Mechanism Section

Goal: increase belief

Explain:

  • system, method, or framework
  • why it is different
  • why it works better

6. Value Stack Section

Goal: increase perceived value

List:

  • core offer
  • components
  • bonuses

For each:

  • name
  • what it does
  • outcome
  • value

End with:

  • total value
  • price reveal

7. Proof Section

Goal: increase trust

Include:

  • testimonials
  • case studies
  • results
  • examples

If none available:

  • use logic or demonstration

8. Objection Handling Section

Goal: remove doubts

Address:

  • time
  • effort
  • price
  • trust
  • fit

Use:

  • clear answers
  • short paragraphs

9. Guarantee Section

Goal: reduce risk

Include:

  • guarantee type
  • what it covers
  • how it works

Make it simple and clear.


10. CTA Section

Goal: drive action

Include:

  • strong CTA
  • restated outcome
  • urgency if needed

11. FAQ Section (Optional)

Answer:

  • remaining objections
  • edge cases
  • common questions

Assistant Behavior

1. Extract key elements

Identify:

  • audience
  • result
  • pain
  • offer structure
  • proof
  • objections

2. Build structure first

Outline all sections before writing copy.


3. Write section by section

Each section must:

  • be clear
  • be short
  • focus on one idea
  • flow logically

4. Use Hormozi-style copy

  • direct language
  • outcome-focused
  • specific
  • no fluff
  • no jargon

5. Emphasize value

  • stack value before price
  • show contrast (value vs price)
  • highlight benefits over features

6. Integrate objections naturally

Do not isolate them only in one section.

Include them throughout:

  • hero
  • solution
  • value stack
  • FAQ

7. Optimize for scanning

Use:

  • short paragraphs
  • bullet points
  • clear headings

8. Add multiple CTAs

Place CTAs:

  • after hero
  • after value stack
  • at the end

9. Align with offer

Ensure:

  • messaging matches offer
  • promise is consistent
  • no exaggeration

Output Format

# LANDING_PAGE.md

## 1. Hero Section
- Headline:
- Subheadline:
- CTA:

---

## 2. Problem Section
- Copy:

---

## 3. Outcome Section
- Copy:

---

## 4. Solution Section
- Copy:

---

## 5. Mechanism Section
- Copy:

---

## 6. Value Stack

### Core Offer
- Name:
- Description:
- Value:

### Bonuses
- Bonus:
- Description:
- Value:

### Total Value:
### Price:

---

## 7. Proof Section
- Testimonials:
- Case studies:

---

## 8. Objection Handling
- Objection → Response

---

## 9. Guarantee
- Description:

---

## 10. CTA Section
- Copy:

---

## 11. FAQ
- Question → Answer

⸻

Decision Rules

Improve clarity when: • sections feel vague • message is hard to understand

Add proof when: • trust is low • claims are strong

simplify when: • page feels long or heavy • too many ideas compete

emphasize value when: • price feels high • offer feels weak

⸻

Before vs After Example

Before • random sections • unclear message • weak CTA

After • structured flow • clear outcome • strong value stack • logical progression

⸻

Style Guidelines • simple language • direct tone • short sentences • outcome-focused • easy to scan

⸻

Success Criteria

The skill works when: • the page is easy to read • the value is clear • objections are handled • trust is built • action feels natural • conversions increase

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.