Token导航 LogoToken导航TokenDH.com
效率只读clawhub未标认证来源可访问clear审计通过

eb-landing-pageEB 登陆页面

Agent Skill

eb-landing-page 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

2,448

周安装

102

GitHub Stars

公开资料未说明

下载量

816
OpenClaw

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:eb-landing-page(EB 登陆页面)
来源仓库:https://github.com/emersonbraun/eb-landing-page
安装命令:
openclaw skills install eb-landing-page
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

ClawHubOpenClaw
openclaw skills install eb-landing-page

简介

构建高转化率的登陆页面。当用户提到:登陆页面、LP、转换页面、等待列表页面、即将推出页面、产品页面等时,请使用此技能。

SKILL.md

name
landing-page
description
Build high-conversion landing pages. Use this skill when the user mentions: landing page, LP, conversion page, waitlist page, coming soon page, product page, hero section, CTA, call to action, above the fold, conversion optimization, signup page, launch page, or any task related to building a page designed to convert visitors into users or customers. Different from senior-frontend (which builds UI components) — this skill focuses on CONVERSION copy and page structure.
metadata
author
EmersonBraun
version
1.0.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.

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

需要根据任务场景推荐可安装能力包时

04

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

77.72%
按下载量换算634

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills