跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
数据与分析

conversion-optimization

Guided journey from a leaking conversion flow - landing page, signup, checkout, or in-app onboarding - to a measured, tested funnel. Orchestrates six skills phase by phase - lean-analytics, cro-methodology, storybrand-messaging, hundred-million-offers, influence-psychology, design-everyday-things - each phase carries its full method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (FUNNEL.md, METRICS.md, EXPERIMENTS.md, CONVERSION-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to raise conversion on a specific flow, fix checkout or signup abandonment, diagnose onboarding drop-off, or says ''people start but never finish''. With no site yet, use create-website; for a whole-site look, message, and speed audit, improve-website; if the flow converts but needs traffic, grow-website; for in-product engagement and retention, improve-app. For one framework in isolation, invok

wondelai · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add wondelai/skills --skill conversion-optimization

技能说明


name: conversion-optimization description: 'Guided journey from a leaking conversion flow - landing page, signup, checkout, or in-app onboarding - to a measured, tested funnel. Orchestrates six skills phase by phase - lean-analytics, cro-methodology, storybrand-messaging, hundred-million-offers, influence-psychology, design-everyday-things - each phase carries its full method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (FUNNEL.md, METRICS.md, EXPERIMENTS.md, CONVERSION-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when the user wants to raise conversion on a specific flow, fix checkout or signup abandonment, diagnose onboarding drop-off, or says ''people start but never finish''. With no site yet, use create-website; for a whole-site look, message, and speed audit, improve-website; if the flow converts but needs traffic, grow-website; for in-product engagement and retention, improve-app. For one framework in isolation, invoke that skill directly.' license: MIT metadata: author: wondelai version: "1.0.0"

Conversion Optimization

Turn one leaking conversion flow — a landing page, a signup, a checkout, an in-app onboarding — into a measured, tested funnel. This is an interactive, resumable journey of seven phases: the agent asks before every decision and records the outcome in your project's docs/ folder, so you can stop after any phase and pick up later. It works on websites and inside products alike; the unit of work is the flow and its ONE action, not the whole site.

Core Principle

Find the leak with numbers, learn the reason from customers, fix message → offer → proof → friction in that order, and prove every fix with a pre-committed test. The order is causal: a number tells you where, only research tells you why, motivation must be raised before friction-cutting pays, and an untested fix is a guess that compounds. This skill sequences the phases, asks the decision questions, and records every choice in docs/. The constituent skills carry the method — invoke them rather than improvising their frameworks.

Journey Map

PhaseSkillQuestion it answersArtifact
1lean-analyticsWhere does the flow actually leak, and what is the one metric?Extends docs/METRICS.md — GATE
2cro-methodologyWhy do people drop at the leak — which objections and friction?Creates docs/FUNNEL.md; extends docs/EXPERIMENTS.md — GATE
3storybrand-messagingDoes the leaking step promise the visitor's own desired outcome in five seconds?Extends docs/POSITIONING.md + docs/FUNNEL.md + docs/EXPERIMENTS.md
4hundred-million-offersIs the offer at the conversion point worth acting on now?Extends docs/OFFER.md + docs/EXPERIMENTS.md
5influence-psychologyIs there honest proof at every point of doubt?Extends docs/FUNNEL.md + docs/EXPERIMENTS.md
6design-everyday-thingsCan a visitor who decided to act complete the flow without stumbling?Extends docs/FUNNEL.md + docs/DESIGN.md + docs/EXPERIMENTS.md
7cro-methodologyWill we know the fix worked — pre-committed metric, sample size, no peeking?Extends docs/EXPERIMENTS.md + docs/METRICS.md

Operating Rules

  1. Resume first. Before anything else, read docs/CONVERSION-OPTIMIZATION-PLAN.md and every artifact in the Journey Map. If the tracker exists, summarize the journey state in 3-5 lines and ask which phase to enter. Done when the user has confirmed an entry point. A journey with a tracker is resumed, never restarted.
  2. Intake on first run only. No tracker: run the Intake below, then create docs/CONVERSION-OPTIMIZATION-PLAN.md with every phase statused pending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan.
  3. Phase entry. Announce: what the phase does, the decision it forces, the artifact it produces, rough effort. Offer proceed / skip / defer — phases marked GATE may be deferred, never skipped. Mark the phase in-progress on proceed. Done when the user chose.
  4. Skill invocation and fallback. Load the phase's skill and use it: each phase's Invoke line names the skill by slug — use that skill to run the phase. If it is not available, offer: npx skills add wondelai/skills/<slug> --global. If the user declines, run the phase from its Brief — the minimum viable method. State which mode you are in.
  5. In-phase decisions. Ask every question under "Decide with the user" — with concrete options and your recommendation. Record the choice in the tracker's Key Decisions. A decision made silently is a defect.
  6. Phase exit. Present the draft artifact content for sign-off before writing. On approval: write or extend the docs/ files, update the tracker (status, Key Decisions, Next Actions). Done when the files are written and the phase row shows done.
  7. Artifact discipline. Read before writing; create a file only if missing, otherwise extend — add or update your sections, preserve everyone else's. Files are UPPERCASE in docs/. Every recommendation lands as a checkbox or a table row with owner and priority. See references/artifact-templates.md when creating a docs/ file for the first time — create it from the full skeleton (all section headings), then fill the sections your phase names.
  8. Measure, research, then change — and every change is a test. No fix ships without a Phase 1 leak and a Phase 2 researched reason behind it, and every shipped change lands in docs/EXPERIMENTS.md with a pre-committed primary metric and a guardrail. A fix with no research behind it goes back to Phase 2; a bold change with no test attached stays in the backlog until it has one.

Intake

Ask these before creating the tracker:

  1. **Which flow are we optimizing, and what is the ONE ac
阅读完整来源 ↗