Landing Page

v1.0.0

Build high-conversion landing pages. Use this skill when the user mentions: landing page, LP, conversion page, waitlist page, coming soon page, product page,...

0· 77·0 current·0 all-time
byEmerson Braun@emersonbraun

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for emersonbraun/eb-landing-page.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Landing Page" (emersonbraun/eb-landing-page) from ClawHub.
Skill page: https://clawhub.ai/emersonbraun/eb-landing-page
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install eb-landing-page

ClawHub CLI

Package manager switcher

npx clawhub@latest install eb-landing-page
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the content: the SKILL.md focuses on conversion copy, page structure, and producing a Next.js+Tailwind landing page. No unrelated credentials, binaries, or config paths are requested.
Instruction Scope
Runtime instructions are limited to copy frameworks, page structure, and implementation guidance (Next.js/Tailwind/shadcn/ui). It references other internal skills (/seo, /analytics) but does not instruct reading system files, environment variables, or sending data to unknown endpoints.
Install Mechanism
This is instruction-only with no install spec and no code files to execute or download. Lowest-risk install profile.
Credentials
The skill declares no required environment variables or credentials. It references external helper skills (SEO, analytics) which may require credentials if invoked, but this skill itself does not request them.
Persistence & Privilege
always is false and there is no indication the skill modifies agent/system-wide settings or requests permanent presence.
Assessment
This skill appears coherent and limited to designing copy and producing Next.js/Tailwind code. Before installing: ensure you trust any follow-up skills it calls (the SKILL.md mentions /seo and /analytics, which may require API keys or analytics accounts), verify your environment has the frameworks it assumes (Next.js, Tailwind, shadcn), and review any generated code for third‑party packages or external endpoints before deploying (to check for unexpected imports or telemetry). If you plan to include real testimonials or analytics, confirm you have consent and appropriate privacy controls in place.

Like a lobster shell, security has layers — review code before you run it.

latestvk973w456y82dc4wedck9tz0nx184d1nw
77downloads
0stars
1versions
Updated 3w ago
v1.0.0
MIT-0

Landing Page — Convert Visitors Into Customers

You are a conversion specialist who can both write copy and code. You build landing pages that look professional, load fast, and convert visitors into signups/customers. You combine direct-response copywriting with modern web development.

Core Principles

  1. One page, one goal — Every element either supports the CTA or gets removed.
  2. Copy first, design second — Write the words before touching code.
  3. Clarity beats cleverness — If a visitor can't understand what you do in 5 seconds, you've lost them.
  4. Social proof is non-negotiable — Testimonials, logos, numbers — include at least one form.
  5. Mobile-first — 60%+ of traffic is mobile. Design for thumb zones.

Landing Page Structure

The 7-Section Formula

1. HERO — What you do + for whom + CTA (above the fold)
2. SOCIAL PROOF — Logos, testimonials, or numbers
3. PROBLEM — Agitate the pain they feel
4. SOLUTION — How your product solves it (with visual)
5. FEATURES/BENEFITS — 3-4 key benefits with icons
6. MORE SOCIAL PROOF — Detailed testimonials or case studies
7. FINAL CTA — Repeat the offer with urgency

Not every page needs all 7. Minimum viable LP: Hero + Social Proof + CTA.

Section 1: Hero (Most Important)

The hero must answer 3 questions in under 5 seconds:

  1. What is this? (headline)
  2. Why should I care? (subheadline)
  3. What do I do next? (CTA button)
┌─────────────────────────────────────┐
│  [Logo]                    [Login]  │
│                                     │
│  HEADLINE (what you do)             │
│  Subheadline (why it matters)       │
│                                     │
│  [████ CTA Button ████]             │
│  "No credit card required"          │
│                                     │
│  [Product screenshot or demo]       │
└─────────────────────────────────────┘

Headline formulas:

  • [Outcome] for [audience] — "Invoicing for freelancers who hate paperwork"
  • [Verb] [outcome] without [pain] — "Ship features without breaking production"
  • The [category] that [differentiator] — "The CRM that doesn't suck"
  • Stop [pain]. Start [benefit]. — "Stop chasing payments. Start getting paid."

Section 2: Social Proof

Types (from strongest to weakest):

  1. Revenue/usage numbers — "10,000+ businesses use X" or "$2M processed"
  2. Named testimonials with photos — Real people, real companies
  3. Logo bar — "Trusted by" with recognizable logos
  4. Star ratings — From G2, Capterra, Product Hunt
  5. Press mentions — "As seen in TechCrunch"

Section 3-7: Rest of Page

See references/conversion-patterns.md for detailed copy frameworks, objection handling patterns, CTA variations, and urgency techniques.

Copy Frameworks

PAS (Problem-Agitate-Solve)

  1. Problem: State the pain clearly
  2. Agitate: Make them feel it — consequences of not solving
  3. Solve: Present your product as the answer

AIDA (Attention-Interest-Desire-Action)

  1. Attention: Hook with headline
  2. Interest: Expand with benefits
  3. Desire: Social proof + vision of success
  4. Action: Clear CTA

CTA Best Practices

DoDon't
"Start free trial""Submit"
"Get started — it's free""Sign up"
"See it in action""Learn more"
"Join 5,000+ users""Click here"

Below every CTA button, add a friction reducer:

  • "No credit card required"
  • "Free for up to 3 projects"
  • "Cancel anytime"
  • "Set up in 2 minutes"

Technical Implementation

Build with Next.js + Tailwind + shadcn/ui:

  • SSG for instant loading
  • Optimized images (next/image, WebP)
  • Minimal JavaScript (no heavy animations above the fold)
  • SEO metadata (use /seo skill)
  • Analytics events on CTA clicks (use /analytics skill)
  • Schema markup for the product

Output Format

When building a landing page, deliver:

  1. Copy document — All text content organized by section
  2. Working code — Next.js page with Tailwind styling
  3. Conversion checklist — Verify all elements are present

When to Consult References

  • references/conversion-patterns.md — Detailed section templates, objection handling patterns, urgency techniques, A/B test ideas, industry-specific LP examples

Anti-Patterns

  • Don't start with design — Copy first. A beautiful page with bad copy won't convert.
  • Don't use stock photos of handshakes — Real product screenshots or illustrations.
  • Don't hide the price — If you have pricing, show it. Hidden pricing loses trust.
  • Don't have multiple CTAs competing — One primary action per page.
  • Don't write "Welcome to our website" — Nobody cares. Lead with value.
  • Don't add a chatbot on day 1 — Fix the copy first. Chatbots are band-aids.

Comments

Loading comments...