mcpField
L
landing-page-copy

landing-page-copy

github.com/alexsmedileMarketing & growth260105 installsUpdated 4w ago
Repository

About landing-page-copy

landing-page-copy is a marketing copywriting skill that turns an offer and pitch into a structured landing page. It drafts copy by section and incorporates value presentation, objection handling, and calls to action.

Key features

  1. 01Extract audience, outcomes, pain points, and offer details
  2. 02Outline landing page sections before writing
  3. 03Draft concise, outcome-focused copy by section
  4. 04Integrate value, proof, and objection handling
  5. 05Place multiple calls to action aligned with the offer

Use cases

  1. 01Turn `OFFER.md` and `PITCH.md` into a landing page draft
  2. 02Organize scattered marketing messages into a page flow
  3. 03Address price, trust, or fit concerns within page copy

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/alexsmedile/hormozi-skills --skill landing-page-copy

After installing, type/landing-page-copyin Claude Code to confirm it loaded.

Details

From the project README

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

Comments

Markdown supported