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

landing-page-copy-pro着陆页复制专业版

Agent Skill

landing-page-copy-pro 用于辅助测试设计、自动化测试和回归验证,适合在 OpenClaw 中需要补充测试、分析失败日志或验证功能改动时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

1,435

周安装

61

GitHub Stars

公开资料未说明

下载量

503
OpenClaw

安装说明

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

GitHub

来源数

2

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install landing-page-copy-pro

简介

使用经过验证的框架和变体选项来进行有效的 A/B 测试,生成根据您的产品定制的完整的、经过转化优化的登陆页面副本。

SKILL.md

Landing Page Conversion Copy Pro

Purpose

This skill generates complete, conversion-optimized landing page copy using established copywriting frameworks. It structures copy from hero headline to final CTA — value proposition, feature-to-benefit bridge, social proof, risk reversal, pricing clarity, FAQ, and CTA cascade. "Pro" means built-in conversion frameworks (AIDA, PAS, StoryBrand) and variant generation for A/B testing. Best used when you need a landing page that turns traffic into signups, leads, or sales, with every section engineered for persuasion and clarity.

Triggers

  • "write landing page copy"
  • "landing page copywriter"
  • "落地页文案"
  • "conversion copy"
  • "hero section"
  • "landing page CTA"
  • "sales page copy"
  • "landing page writer"
  • "转化文案"
  • "高转化落地页"

Workflow

  1. Receive product/offer details from user: product name, core value proposition, target audience, page goal (lead gen, purchase, app download, webinar signup, waitlist), and any existing copy or brand voice preferences.
  2. Select the optimal landing page structure based on page goal:

- Lead Gen: Hero → Value Prop → Benefits → Social Proof → Form CTA - Purchase: Hero → Problem → Solution → Features → Benefits → Pricing → Guarantee → CTA - App Download: Hero → Hook → Feature Highlights → Social Proof → Store Buttons - Webinar: Hero → Topic → Speaker Credibility → Agenda → Registration CTA

  1. Generate hero headline + subheadline variants (3–5 options) using proven formulas: outcome-focused, curiosity-driven, pain-agitate-solution, or social proof-led.
  2. Translate feature lists into benefit-focused copy with emotional hooks — not what the product does, but what the user gains.
  3. Format social proof section: testimonial selection, credibility stats, trust badges, and logo bars — with guidance on what makes proof believable.
  4. Build FAQ section addressing the 3–5 most common objections for this offer type.
  5. Create CTA hierarchy: primary CTA (immediate action), secondary CTA (lower commitment), fallback CTA (retention move like newsletter signup).
  6. Review against conversion best practices and safety rules — no dark patterns, no false urgency.

Prompt Templates

1. Full Landing Page (full_landing_page)

Purpose: Generate a complete landing page section-by-section from product/offer details.

Input:

  • ${product_name} — Product or offer name
  • ${core_value_prop} — One-sentence value proposition
  • ${target_audience} — Who this is for (demographics + psychographics)
  • ${page_goal} — Conversion goal (lead gen, purchase, app download, webinar, waitlist)
  • ${key_features} — 3–5 core features
  • ${price_point} — (Optional) Price or pricing model
  • ${existing_copy} — (Optional) Any current copy to improve

Output: Complete landing page copy organized by section:

  • Hero (headline + subheadline + hero CTA)
  • Value Proposition (2–3 sentence expansion)
  • Feature-Benefit Bridge (feature → benefit → emotional hook per item)
  • Social Proof (testimonial format + stats + trust signals)
  • Pricing/Offer (if applicable)
  • FAQ (3–5 objections + responses)
  • CTA Cascade (primary, secondary, fallback)

2. Hero Section Optimizer (hero_section_optimizer)

Purpose: Generate 5 headline + subheadline variants for the hero section.

Input:

  • ${product_name} — Product/offer name
  • ${core_value_prop} — Core value proposition
  • ${target_audience} — Audience descriptor
  • ${hero_formula} — (Optional) Preferred formula (outcome, curiosity, PAS, social proof)

Output: 5 hero variants, each with:

  • Headline (10 words or fewer)
  • Subheadline (1–2 sentences expanding the promise)
  • CTA button text
  • Why it works (formula rationale)
  • Best fit scenario

3. Feature-to-Benefit Translator (feature_to_benefit_translator)

Purpose: Convert technical features into emotionally resonant benefits.

Input:

  • ${feature_list} — List of product features
  • ${target_audience} — Audience pain points and desires
  • ${emotional_tone} — Desired emotional angle (relief, aspiration, confidence, belonging)

Output: Translated list where each item follows:

  • Feature (what it is)
  • Benefit (what it does for the user)
  • Emotional Hook (how it makes the user feel)
  • Suggested copy line for landing page

4. Social Proof Formatter (social_proof_formatter)

Purpose: Turn raw testimonials and stats into polished, credible social proof sections.

Input:

  • ${testimonials} — Raw customer quotes (2–5)
  • ${stats} — Key numbers (users, results, satisfaction rate)
  • ${credibility_markers} — Logos, awards, media mentions
  • ${audience_skepticism} — What prospects typically doubt

Output: Formatted social proof section with:

  • Testimonial selection and ordering (most relatable first)
  • Stats formatted for scannability
  • Trust badge placement guidance
  • Notes on avoiding over-polished or fake-sounding testimonials

5. CTA Hierarchy (cta_hierarchy)

Purpose: Build a strategic CTA cascade for a landing page based on conversion goal.

Input:

  • ${page_goal} — Conversion goal
  • ${offer_urgency} — (Optional) Time-bound or quantity-bound urgency
  • ${audience_commitment_level} — Cold, warm, or hot traffic

Output: CTA hierarchy:

  • Primary CTA (direct action, above the fold)
  • Secondary CTA (lower commitment, mid-page)
  • Fallback CTA (minimum commitment, bottom of page)
  • Button copy variants for each
  • Placement recommendations
  • Notes on avoiding dark patterns and deceptive urgency

Output Format

All landing page outputs follow a structured pro format:

# Landing Page: [Product/Offer Name]
**Goal:** [Goal] | **Audience:** [Audience]

## Hero Section
- **Headline:** [Headline]
- **Subheadline:** [Subheadline]
- **CTA:** [Button text]

## Value Proposition
[2–3 sentences]

## Feature → Benefit Bridge
1. **[Feature]** → [Benefit] → [Emotional hook]
   *Copy line:* [Suggested copy]

## Social Proof
[Testimonial block]
[Stats block]
[Trust signals]

## FAQ
Q: [Objection]
A: [Response]

## CTA Cascade
- **Primary:** [CTA]
- **Secondary:** [CTA]
- **Fallback:** [CTA]

Additional outputs:

  • Hero variants: Numbered list with formula labels
  • Feature-benefit table: Feature | Benefit | Emotion | Copy Line
  • Social proof notes: Credibility best practices and red flags
  • CTA notes: Commitment ladder logic and dark pattern warnings

Safety Rules

  • NEVER make false or misleading claims about product capabilities, results, or performance
  • NEVER fabricate testimonials, statistics, or customer data
  • NEVER use dark patterns in CTA language (e.g., fake countdowns, hidden opt-outs, manipulative guilt framing)
  • NEVER create unsubstantiated urgency ("only 2 left" unless true)
  • ALWAYS present pricing and terms clearly — no hidden conditions buried in copy
  • ALWAYS recommend A/B testing before full launch; no single version is guaranteed to win
  • ALWAYS include appropriate risk reversal (guarantee, trial, refund policy) when applicable
  • ALWAYS remind the user to review and fact-check all claims before publishing

Examples

Example 1: Full Landing Page (SaaS Product, Lead Gen)

Input: Product="TeamFlow 项目管理工具", Value Prop="让远程团队协作像面对面一样顺畅", Audience="50-200人远程团队的负责人", Goal="lead gen", Features=[实时同步看板, 自动化周报, 集成Slack/Zoom, 权限管理]

Output:

  • Hero: "远程团队不同步?TeamFlow让你像在同一间办公室" + "实时看板、自动周报、无缝集成 — 专为远程团队设计" + CTA "免费试用14天"
  • Value Prop: 3 sentences on async transparency and time saved
  • Feature-Benefit: 实时同步看板 → 每个人随时知道进度 → 不再被"进度怎么样了"打断 → "打开看板,状态一目了然"
  • Social Proof: "300+远程团队已迁移到TeamFlow" + testimonial format
  • FAQ: Address security, onboarding time, and free trial limits
  • CTA Cascade: Primary="开始免费试用" / Secondary="预约演示" / Fallback="下载产品手册"

Example 2: Hero Section Optimizer (Same Product)

Input: Product="TeamFlow", Value Prop="远程协作零摩擦", Audience="远程团队负责人"

Output: 5 hero variants using different formulas:

  1. Outcome: "你的远程团队,终于可以同步了"
  2. Curiosity: "为什么顶尖远程团队不再开早会了?"
  3. PAS: "远程团队每天浪费2小时对齐进度。TeamFlow把它变成2分钟。"
  4. Social Proof: "300+远程团队选择的协作方式"
  5. Direct: "TeamFlow — 远程团队项目管理,像面对面一样顺畅"

Example 3: Feature-to-Benefit Translator (E-Commerce)

Input: Features=["真丝面料", "可机洗", "7天无理由退换"], Audience="25-40岁职场女性", Emotional Tone="confidence"

Output:

  • 真丝面料 → 透气亲肤,整天舒适 → 从容应对重要场合 → "真丝触感,让重要的一天从舒适开始"
  • 可机洗 → 省去干洗麻烦 → 省下的时间属于自己 → "可机洗的真丝,省心不省质感"
  • 7天无理由退换 → 零风险尝试 → 买得放心 → "不喜欢?7天内无理由退换,零风险体验"

Related Skills

适合场景

01

OpenClaw 用户查找和安装 Skill 时

02

用户想查找某类 Agent Skill 时

03

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

04

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

能力 5

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

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

平台分布

OpenClaw

86.1%
按下载量换算433

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

来源信息

继续浏览同类 Skills