菜单
Improves landing page conversion rates through hypothesis-driven CRO — audit, prioritize, test, and iterate. Use before scaling paid spend, after a CVR drop, or during a growth sprint.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Drafts a margin-aware 3-email cart-recovery sequence that reminds, handles objections, then incentivizes only as a last touch. Use when a checkout is started but not completed and you need cart-recovery (abandoned-cart) emails, when wiring an abandoned-cart flow in Shopify, Klaviyo, or similar, or when asked to recover lost carts without overspending on discounts.
Writes an Amazon product title, five bullets, and backend search terms that obey Amazon's character, byte, and keyword rules while staying click-worthy in the search grid. Use when drafting or fixing a Seller Central listing, rewriting an Amazon title or bullet points, packing backend search terms, or recovering a listing flagged or suppressed for content. Do NOT use when writing on-site product-detail-page copy for your own storefront or marketing site — use product-description-writer instead.
Write the intro and lower-page copy for an ecommerce collection or category page so it ranks for a commercial query while pushing shoppers toward a product fast. Use when you have a collection/category page (e.g. "women's merino base layers", "standing desks") and need the above-grid intro blurb, the H1, and the supporting SEO content below the product grid. Do NOT use for standalone marketing or campaign landing pages — use landing-page-copy instead; do NOT use for a single product's description — use product-description-writer instead.
Builds an honest "X vs Y" or "best alternative to X" comparison page — scannable table plus use-case routing copy — for high-intent commercial searches. Use when the user wants to create a "vs" or "alternative-to" page, a competitor comparison table, or copy that names a rival and asks which product to choose.
Writes the single on-site PDP master copy — a benefit-led, scannable product detail page in the brand's voice — from a raw spec sheet or feature list. Use when you have a spec list, feature bullets, or a bare template description for one product and need conversion copy for its on-site product detail page. Do NOT use for Amazon or marketplace listings — use amazon-listing-optimizer instead; do NOT use to spin one master into many size/color variants — use variant-copy-scaler instead.
Mines customer reviews and Q&A into a pre-purchase PDP FAQ and objection-handling block that answers shopper hesitation before it forms. Use when you have a review or Q&A export and want to write or rebuild a product page FAQ, reduce returns from preventable surprises, or shoppers keep asking the same pre-purchase questions. Do NOT use when analyzing support tickets or CSAT/NPS verbatims to find quality root causes — use CSAT Root Cause Analysis instead.
| name | Landing Page CRO |
| description | Improves landing page conversion rates through hypothesis-driven CRO — audit, prioritize, test, and iterate. Use before scaling paid spend, after a CVR drop, or during a growth sprint. |
Conversion rate optimization is not about applying best practices — it is about forming specific hypotheses, testing them against real users, and iterating based on evidence. Generic fixes rarely move the needle; specific ones do.
Before writing a single hypothesis, collect: (1) quantitative data — heatmaps, scroll maps, click maps, session recordings, and funnel drop-off data; (2) qualitative data — user surveys, live chat transcripts, and sales call notes. The audit should answer: where are users leaving, what are they clicking that does not help them convert, and what objections appear repeatedly in their own words. Spend at least one hour in session recordings before forming opinions.
Every hypothesis follows this format: 'Because [observation from audit], changing [element] to [proposed change] will [expected outcome] for [audience].' A hypothesis without an observation is a guess. A hypothesis without a measurable expected outcome cannot be evaluated. Write hypotheses before mockups — the thinking matters more than the execution.
Score each hypothesis on Impact (how much will it move CVR if true), Confidence (how strong is the evidence), and Ease (how fast can it be built and tested). Multiply the three scores on a 1-10 scale. Run the top-scoring test first. Avoid running more than two tests simultaneously on the same page — it complicates interpretation.
In order of typical impact: (1) headline — must match the ad's promise and speak to a specific pain; (2) primary CTA — text, position, and contrast matter; (3) social proof — specificity beats volume, a named customer quote outperforms a star rating; (4) above-the-fold visual — must show the outcome, not the product; (5) form or checkout friction — every unnecessary field reduces conversion. Fix these before testing background colors or font sizes.
Do not call a winner until reaching 95% statistical significance with at least 100 conversions per variant. For low-traffic pages, use Bayesian testing and set a 90% probability-to-beat threshold. Never end a test early because one variant looks better — regression to the mean is real. Document every test outcome, including losses — a failed hypothesis is still a learning.
The single most common CRO failure is message mismatch: the ad makes a specific promise and the landing page delivers a generic brand statement. Every paid traffic source should land on a page where the headline directly echoes the ad's offer. If one page serves multiple campaigns, use dynamic text replacement or build dedicated landing pages per major campaign theme.
