pitch-landing
Use when asked to structure a landing page for positioning, plan a conversion-optimized page layout, or design a launch page. Examples: "landing page for product launch", "conversion-optimized layout for SaaS"
适合你，如果你需要为产品或活动设计高转化率的着陆页
npx oh-my-skill add tonone-ai/tonone/pitch-landingcurl -fsSL https://oh-my-skill.com/install.sh | bash -s -- tonone-ai/tonone/pitch-landingnpx oh-my-skill verify tonone-ai/tonone/pitch-landing怎么用
商店整理自技能原文 · 版本 d6b6925 · 表述以原文为准根据你的产品类型和定位，Claude 会生成一个着陆页结构大纲，以表格形式列出章节顺序、目的和 CTA 策略，并包含定位锚点、社会证明位置和异议处理方式。
当你要求设计产品定位、转化优化的着陆页或启动页时触发。例如，提到“产品发布着陆页”或“SaaS 的转化优化布局”等需求。
技能原文 SKILL.md
pitch-landing — Launch & Positioning Landing Page
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
When to use
User needs a landing page structured around product positioning, launch messaging, or conversion for a specific audience.
Workflow
- Identify product type and positioning anchor from user request or brief
- Search landing page patterns: ```bash python3 -m pitch_agent.uiux search --domain landing --query "{product_type}" --limit 3 ```
- Search product reasoning for audience + messaging context: ```bash python3 -m pitch_agent.uiux search --domain product --query "{product_type}" --limit 3 ```
- Layer in positioning: CTA strategy, social proof placement, objection handling
- Output section order with conversion and messaging optimization
Output format
┌─ Launch Landing Page — {product_type} ──────────────────────────────┐
│ # │ Section │ Purpose │ CTA? │
├────┼────────────────────┼────────────────────────────┼───────────────┤
│ 1 │ {section_name} │ {purpose} │ Primary CTA │
│ 2 │ {section_name} │ {purpose} │ — │
│ 3 │ {section_name} │ {purpose} │ Secondary CTA │
│ … │ … │ … │ … │
└────┴────────────────────┴────────────────────────────┴───────────────┘
CTA strategy: {cta_strategy}
Social proof: {social_proof_placement}
Objection handling: {objection_section}
Positioning anchor: {positioning_anchor}
Anti-patterns
- Never structure copy without a clear positioning anchor (who it's for + what makes it different)
- Never add sections that don't serve conversion or objection handling
- Never place social proof after the primary CTA — it should reinforce before the ask
- Never launch without a single, unambiguous primary CTA per viewport
Delivery
If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.