Token导航 LogoToken导航

Agent Skill · 研究检索

sales-page-copywriting(销售页面文案)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

sales-page-copywriting 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 17,138。

总安装 6,774周安装 288GitHub Stars 8下载 2,373核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:sales-page-copywriting(销售页面文案)
来源仓库:https://github.com/yashaiguy-dev/sales-page-copywriting-skill
仓库路径:skills/sales-page-copywriting
安装命令:
npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --skill sales-page-copywriting
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --skill sales-page-copywriting

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助销售页面文案的撰写与优化,适合在 Codex、Claude、Cursor、Gemini CLI 中提升内容表达效果。可提炼卖点结构、优化标题和正文、统一品牌语气,并检查文案逻辑与合规边界。通过 GitHub 安装后,结合具体任务调用,保留项目事实,避免过度营销或夸大承诺。

使用时需确认数据来源,涉及对外发布时注意语气克制,不虚构功能或效果。建议先验证仓库维护状态,避免依赖已弃用的接口或失效链接。

来源仓库内路径:skills/sales-page-copywriting

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --s…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

sales-page-copywriting 怎么安装?

在终端执行 npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --skill sales…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

sales-page-copywriting 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

sales-page-copywriting 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --skill sales-page-copywriting 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

sales-page-copywriting 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

sales-page-copywriting 用的人多吗?

公开数据是累计安装 6,774 次,近一周安装 288 次,下载 2,373 次,GitHub 8 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

sales-page-copywriting 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
sales-page-copywriting

销售页面文案 · 本页

6,7748执行命令未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

SALES PAGE COPYWRITING - HOSTILE VALIDATION SYSTEM

CRITICAL OUTPUT INSTRUCTION

YOU MUST OUTPUT ONLY THE FINAL POLISHED WEBSITE COPY TO THE USER.

  • Do NOT show the user your internal validation process
  • Do NOT show hostile reviewer feedback to the user
  • Do NOT show the before/after revision process
  • Do ALL validation work internally
  • ONLY output the final polished website copy document

PHASE 1: INPUT CAPTURE & STRATEGIC FOUNDATION

When user provides a product idea or business concept, silently extract and document internally:

CORE PRODUCT DNA:

  • What it is (in one sentence a 10-year-old would understand)
  • What problem it solves (the specific pain, not the generic category)
  • Who it's for (psychographic more than demographic)
  • What makes it different (the actual differentiator, not marketing fluff)
  • What you want visitors to do (the primary conversion goal)

MARKET CONTEXT:

  • Top 3 competitors and their messaging approach
  • Common objections in this product category
  • Typical buyer journey complexity (impulse vs. considered purchase)
  • Primary traffic source assumptions (cold traffic, warm referrals, paid ads, etc.)

If information is missing, ask the user clarifying questions to complete this foundation.


PHASE 2: INTERNAL COPY GENERATION

Generate complete copy for these 7 critical sections (WORK INTERNALLY, DON'T SHOW YET):

1. HERO SECTION

  • Headline: One clear statement of transformation or unique mechanism (not generic benefit)
  • Subheadline: Expands on headline with specificity or handles immediate objection
  • Primary CTA: Action-oriented button text (must be specific, not "Learn More")
  • Visual Direction: What the hero image/video should communicate

2. PROBLEM AGITATION

  • 3-4 pain points written from customer's internal voice with emoji bullets (😤, 😫, 🤯, 😰)
  • Must feel personally called out, not generic industry problems
  • Should trigger "how did they know?" reaction
  • Format: Emoji + "Quote from customer's head" followed by expansion paragraph

3. SOLUTION INTRODUCTION

  • How it works in 3-4 simple steps (maximum)
  • Focus on simplicity and speed, not technical features
  • Must create "is it really that easy?" curiosity

4. BENEFITS (not features)

  • 3 core benefits written as transformations
  • Each benefit must answer "so what?" test
  • Include micro-proof point for each (data point, testimonial snippet, example)

5. SOCIAL PROOF STACK

  • Positioning statement: Who uses this and why that matters
  • Testimonial selection criteria: What 3 testimonial types needed (skeptic converted, fast results, specific outcome)
  • Trust indicators: What logos, numbers, or credentials go here

6. OBJECTION HANDLING

  • Pre-emptive FAQ section addressing top 3-5 objections
  • Written conversationally, not corporate
  • Each answer must reduce friction, not create new questions

7. FINAL CTA SECTION

  • Urgency mechanism (not fake scarcity, actual reason to act)
  • Risk reversal (guarantee, trial, easy cancellation)
  • CTA button text (action-specific)
  • Below-CTA microcopy (final objection handled or social proof)

PHASE 3: HOSTILE VALIDATION (INTERNAL - DON'T SHOW USER)

Run your generated copy through this brutal review. DO THIS SILENTLY.

SPAWN 5 HOSTILE VISITOR PERSONAS

For each target customer, simulate these 5 distinct versions:

1. The 8-Second Scanner: Landed from an ad. Reading nothing. Scanning for patterns. Eyes hit hero → scroll → close tab.

  • What makes them NOT immediately understand what this is?
  • What looks like every other site they've seen today?

2. The Comparison Tab Hoarder: Has 7 competitor tabs open. Reading every word looking for elimination reasons.

  • What fails to differentiate you?
  • What makes this feel "same thing, different wrapper"?
  • What makes them pick competitor instead?

3. The Burned Cynic: Bought something similar before and got disappointed. Trust level = zero.

  • What triggers their BS detector?
  • What sounds "too good to be true"?
  • What feels like manipulation?

4. The Confused Bouncer: Genuinely interested but can't figure out: Is this for me? How does it work? What happens after I click?

  • What's unclear?
  • What assumptions does the copy make?
  • What questions go unanswered?

5. The Justified Procrastinator: Wants the solution but subconsciously looking for permission to "come back later."

  • What friction points let them delay?
  • What objection goes unaddressed?
  • What makes "not now" feel safer?

EACH REVIEWER ANALYZES THROUGH 5 LAYERS

LAYER 1: CLARITY FAILURE ANALYSIS "Within 5 seconds of landing, I can't tell ___"

LAYER 2: RELEVANCE REJECTION ANALYSIS "This copy doesn't speak to me because ___"

LAYER 3: CREDIBILITY COLLAPSE ANALYSIS "I don't believe this because ___"

LAYER 4: FRICTION DISCOVERY ANALYSIS "I wouldn't click the CTA because ___"

LAYER 5: COMPETITIVE DISADVANTAGE ANALYSIS "I'd choose a competitor instead because ___"

TALLY AND PRIORITIZE OBJECTIONS

Internally compile all objections:

  • CRITICAL FAILURE: Objection raised by 3+ reviewers — MUST fix
  • HIGH PRIORITY: Objection raised by 2 reviewers — SHOULD fix
  • WORTH ADDRESSING: Single mentions — fix if it doesn't compromise other elements

PHASE 4: REBUILD WITH OBJECTION IMMUNITY (INTERNAL)

Revise each section to neutralize every Critical and High Priority objection.

For each fix, track internally:

  1. The specific objection being addressed
  2. The exact copy change made (before → after)
  3. Why this change neutralizes the objection
  4. What tradeoff was made (if any)

PHASE 5: SECOND PASS VALIDATION (INTERNAL)

Run revised copy through all 5 hostile reviewers again using same 5-layer analysis.

APPROVAL CRITERIA:

  • Zero Critical Failures remaining
  • ≤2 High Priority objections remaining (with documented reasoning)
  • All sections pass "confused 8-second test"

If Critical Failures remain: Repeat revision until approval criteria met.


PHASE 6: FORMAT FOR DELIVERY

Once copy passes validation, format it as follows:

DOCUMENT STRUCTURE:

# [PRODUCT NAME] - WEBSITE COPY
## Complete Copy Generation & Validation Document

---

# PHASE 1: INPUT CAPTURE & STRATEGIC FOUNDATION

## CORE PRODUCT DNA

**What it is:**
[One clear sentence]

**What problem it solves:**
[Specific pain description]

**Who it's for:**
- [Psychographic 1]
- [Psychographic 2]
- [Psychographic 3]
- [Psychographic 4]

**What makes it different:**
[Actual differentiator]

**Primary conversion goal:**
[Specific action]

---

## MARKET CONTEXT

**Top 3 competitors and messaging:**
1. **[Competitor 1]** - [Their approach]
2. **[Competitor 2]** - [Their approach]
3. **[Competitor 3]** - [Their approach]

**Common objections:**
- "[Objection 1]"
- "[Objection 2]"
- "[Objection 3]"
- "[Objection 4]"

**Buyer journey complexity:**
[Assessment]

**Primary traffic source:**
- [Source 1]
- [Source 2]
- [Source 3]

---

# PHASE 2: FINAL WEBSITE COPY

## 1. HERO SECTION

**Headline:**
[Compelling transformation-focused headline]

**Subheadline:**
[Specific expansion that handles objection]

**Primary CTA:**
[Action-specific button text]

**Visual Direction:**
[Clear description of what hero visual should communicate]

---

## 2. PROBLEM AGITATION

**Customer pain points (in their voice):**

😤 **"[First person quote from customer's head]"**
[Expansion paragraph that agitates this pain point]

😫 **"[Second quote from customer's internal dialogue]"**
[Expansion paragraph]

🤯 **"[Third quote showing frustration]"**
[Expansion paragraph]

😰 **"[Fourth quote showing anxiety]"**
[Expansion paragraph]

---

## 3. SOLUTION INTRODUCTION

**How [Product Name] Works:**

**STEP 1: [Action Title]**
[Description of first simple step]

**STEP 2: [Action Title]**
[Description of second step]

**STEP 3: [Delivery Title]**
[Description of what they get]

---

## 4. BENEFITS (Not Features)

### BENEFIT 1: [Transformation Headline]
[Description of transformation and why it matters]

**Micro-proof:** [Specific example, data point, or testimonial snippet with concrete details]

### BENEFIT 2: [Transformation Headline]
[Description of transformation]

**Micro-proof:** [Specific proof point with attribution]

### BENEFIT 3: [Transformation Headline]
[Description of transformation]

**Micro-proof:** [Specific proof point]

---

## 5. SOCIAL PROOF STACK

**Positioning statement:**
[Who uses this and why that matters—specific psychographics]

**Testimonial selection criteria:**

**TYPE 1 - The Skeptic Converted:**
"[Quote showing initial skepticism overcome by results]"
— [Name], [Credible context]

**TYPE 2 - Fast Results:**
"[Quote emphasizing speed to value]"
— [Name], [Context]

**TYPE 3 - Specific Outcome:**
"[Quote with concrete outcome numbers or achievement]"
— [Name], [Context]

**Trust indicators:**
- "[Specific metric or social proof]"
- "[Usage statistics]"
- "[Authority mentions]"
- [Logos/badges as needed]

---

## 6. OBJECTION HANDLING (FAQ)

**Q: [First major objection as question]?**
[Conversational answer that reduces friction and builds confidence]

**Q: [Second objection]?**
[Answer]

**Q: [Third objection]?**
[Answer]

**Q: [Fourth objection]?**
[Answer]

**Q: [Fifth objection]?**
[Answer]

---

## 7. FINAL CTA SECTION

**Urgency mechanism:**
[Honest reason to act now—not fake scarcity]

**Risk reversal:**
[Clear guarantee, trial, or easy cancellation policy]

**CTA button text:**
[Action-specific button copy]

**Below-CTA microcopy:**
✓ [First reassurance]
✓ [Second reassurance]
✓ [Third reassurance/social proof]

---

# VALIDATION SUMMARY

## Objections Found in First Pass: [Number]

## Critical Failures Addressed:
1. ✅ **[Objection category]** - [How it was fixed]
2. ✅ **[Objection category]** - [How it was fixed]
3. ✅ **[Objection category]** - [How it was fixed]

## High-Priority Objections Addressed:
4. ✅ **[Objection]** - [Fix applied]
5. ✅ **[Objection]** - [Fix applied]

## Remaining Acceptable Objections:
- **[Persona]:** "[Objection]" → Acceptable because [reasoning]

## Approval Metrics:
✅ Zero Critical Failures remaining
✅ Zero High-Priority objections remaining
✅ [Number] minor objections remaining with documented reasoning
✅ All personas would click CTA or engage
✅ Confused 8-second test passed

**STATUS: APPROVED FOR IMPLEMENTATION**

---

# IMPLEMENTATION NOTES

## Suggested A/B Test Variations

**Hero Headline Test:**
- **Version A:** "[Current headline]"
- **Version B:** "[Alternative angle]"
- **Version C:** "[Another approach]"

**CTA Button Text Test:**
- **Version A:** "[Current CTA]"
- **Version B:** "[Alternative]"

**Social Proof Test:**
- **Version A:** [Current approach]
- **Version B:** [Alternative format]

## Copy Hierarchy (Mobile Optimization)

**MUST KEEP:**
- [Essential elements that must remain visible]

**CAN CONDENSE:**
- [Elements that can be shortened for mobile]

**CAN CUT (desktop-only):**
- [Optional elements for larger screens]

## Sections Needing Strongest Visual Support

**Priority 1:** [Section name and why it needs strong visuals]

**Priority 2:** [Next critical visual section]

**Priority 3:** [Third priority]

## Tone/Voice Guidelines

**Overall voice:** [Description of brand voice]

**Avoid:**
- [Things to avoid]

**Embrace:**
- [Things to emphasize]

---

# CHARACTER COUNTS

**Hero Headline:** [X] characters
**Hero Subheadline:** [X] characters
**Primary CTA Button:** [X] characters
**Problem Pain Point (avg):** [X] characters each
**Benefit Headlines (avg):** [X] characters

---

# APPROVED FINAL WEBSITE COPY READY FOR IMPLEMENTATION

This copy has survived hostile interrogation from 5 visitor personas across 25 validation angles (5 layers × 5 reviewers). All critical and high-priority objections have been addressed.

**Recommended next steps:**
1. [Specific implementation action]
2. [Next action]
3. [Visual priority]
4. [Testing setup]
5. [Analytics tracking]

**Conversion hypothesis:**
By eliminating [specific issues fixed], we expect:
- [Metric prediction with reasoning]
- [Another expected improvement]
- [Third expectation]

**Final note:**
This copy assumes the product delivers on its promise. If the actual product experience doesn't match these claims, no copy will save conversion rates.

EXECUTION CHECKLIST

When user invokes this skill:

  1. ✅ Ask clarifying questions to complete PHASE 1 foundation
  2. ✅ Generate initial copy for all 7 sections (internally)
  3. ✅ Run through hostile validation (5 personas × 5 layers = 25 angles) SILENTLY
  4. ✅ Tally objections and prioritize (internally)
  5. ✅ Rebuild copy to address Critical and High Priority objections SILENTLY
  6. ✅ Run second validation pass SILENTLY
  7. ✅ Repeat until approval criteria met SILENTLY
  8. ✅ Format final document using template above
  9. ✅ Output ONLY the final polished document to user

USER SEES: Only the beautifully formatted final website copy document

USER DOESN'T SEE: Any of the hostile reviewer process, objections, or iterations


FORMATTING RULES

  1. Use emojis in problem agitation section: 😤, 😫, 🤯, 😰
  2. Bold question quotes: Make customer voice quotes bold
  3. Use checkmarks for lists: ✅ for confirmed items, ✓ for microcopy
  4. Keep testimonials attributed: Always include — Name, Context
  5. Make CTAs action-specific: Never generic "Learn More" or "Click Here"
  6. Number all sections clearly: Use ## for major sections, ### for subsections
  7. Include horizontal rules: Use --- to separate major phases
  8. Show validation rigor: Always include the validation summary to prove the copy is battle-tested
  9. Be specific with numbers: "25 validation angles" not "thorough validation"
  10. End with implementation guidance: Always include next steps and success metrics

QUALITY STANDARDS

  • Clarity: 8-second test must pass (scanner understands immediately)
  • Specificity: No generic claims without proof points
  • Honesty: Acknowledge tradeoffs and limitations
  • Proof: Every major claim needs micro-proof or attribution
  • Differentiation: Must clearly separate from competitors
  • Action-oriented: Every section drives toward conversion goal

This skill produces website copy that has survived hostile scrutiny and is ready to convert skeptical visitors into customers.

平台分布

Codex

38.37%
按下载量换算911

Claude

32.39%
按下载量换算769

Cursor

16.9%
按下载量换算401

Gemini CLI

9.07%
按下载量换算215

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/yashaiguy-dev/sales-page-copywriting-skill --skill sales-page-copywriting 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills