conversion-optimization
Guided journey from a leaking conversion flow - landing page, signup, checkout, or in-app onboarding - to a measured, tested funnel.
Install / Use
npx skills add wondelai/skills --skill conversion-optimizationInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
CommunicationSupported Platforms
Our assessment of conversion-optimization
conversion-optimization scores 87/100 on our quality scale, 258th of 394 Communication skills we index.
Its SKILL.md is 26 KB long, well organised into 16 sections and no code examples: a thorough specification that gives an agent plenty to work with.
With 2,248 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so conversion-optimization is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
conversion-optimization compared with similar skills
All 4 of these similar skills score higher than conversion-optimization; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| conversion-optimization (this skill)by wondelai | 87 | 2.2k | 2mo ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install conversion-optimization?
- Run
npx skills add wondelai/skills --skill conversion-optimization. The install tabs above show the steps for each supported agent. - Which AI agents does conversion-optimization work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is conversion-optimization safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is conversion-optimization still maintained?
- The repository was last updated about 2 months ago, so conversion-optimization is actively maintained.
Skill content
View source on GitHubname: 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
| Phase | Skill | Question it answers | Artifact | |---|---|---|---| | 1 | lean-analytics | Where does the flow actually leak, and what is the one metric? | Extends docs/METRICS.md — GATE | | 2 | cro-methodology | Why do people drop at the leak — which objections and friction? | Creates docs/FUNNEL.md; extends docs/EXPERIMENTS.md — GATE | | 3 | storybrand-messaging | Does the leaking step promise the visitor's own desired outcome in five seconds? | Extends docs/POSITIONING.md + docs/FUNNEL.md + docs/EXPERIMENTS.md | | 4 | hundred-million-offers | Is the offer at the conversion point worth acting on now? | Extends docs/OFFER.md + docs/EXPERIMENTS.md | | 5 | influence-psychology | Is there honest proof at every point of doubt? | Extends docs/FUNNEL.md + docs/EXPERIMENTS.md | | 6 | design-everyday-things | Can a visitor who decided to act complete the flow without stumbling? | Extends docs/FUNNEL.md + docs/DESIGN.md + docs/EXPERIMENTS.md | | 7 | cro-methodology | Will we know the fix worked — pre-committed metric, sample size, no peeking? | Extends docs/EXPERIMENTS.md + docs/METRICS.md |
Operating Rules
- Resume first. Before anything else, read
docs/CONVERSION-OPTIMIZATION-PLAN.mdand 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. - Intake on first run only. No tracker: run the Intake below, then create
docs/CONVERSION-OPTIMIZATION-PLAN.mdwith every phase statusedpending | in-progress | awaiting-evidence | done | deferred: reason | skipped: reason. Done when the tracker exists and the user has confirmed the phase plan. - 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-progresson proceed. Done when the user chose. - 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. - 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.
- 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. - 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. - 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:
- Which flow are we optimizing, and what is the ONE action at its end? (Scopes every phase — a flow with three competing CTAs has no goal.)
- Where do the numbers say people drop — analytics, funnel steps, cohort data? Paste what you have. (Feeds the Phase 1 leak diagnosis; no instrumentation means Phase 1 starts by adding it.)
- Roughly how much traffic or volume enters the flow per week? (Gates Phase 7 — decides whether A/B tests can reach significance or the journey leans on qualitative evidence and before/after windows.)
- What voice-of-customer sources exist or can be gotten — exit surveys, session recordings, support tickets, sales calls, reviews — and can you paste or export the raw text of the best one? (Phase 2 objections must quote the customer's own words, so the phase needs the content, not just the source name.)
- What is the current offer at the conversion point — price, guarantee, bonuses — and can it change? (Gates Phase 4; a contractually fixed offer narrows it to presentation.)
- Do docs/POSITIONING.md or docs/OFFER.md already exist from another journey? (Phases 3-4 build on them rather than restarting.)
- How much of the journey do you want now? (Phases 1-2 are the mandatory diagnosis; 3-6 are the fix passes aimed by it; 7 turns fixes into proof.)
Skip heuristics: skip Phase 3 when messaging was already validated (e.g. an improve-website journey completed its message phases); skip Phase 4 when the offer is fixed by contract — record skipped: reason. Phase 7 may be deferred: reason at very low traffic in favor of before/after evidence with an explicit revert trigger, never silently skipped. Never skip Phases 1-2 — an unfound leak and an unresearched reason turn every later phase into guessing.
Then create docs/CONVERSION-OPTIMIZATION-PLAN.md from the template and confirm the plan. Done when the tracker exists with every phase statused and the user has confirmed the plan.
Phases
Phases run in the listed order — each assumes the previous phase's artifact exists. Any phase can be entered, skipped, or deferred per the Operating Rules, but Phases 1-2 gate them all: nothing downstream fixes a problem that isn't a measured leak with a researched reason. When running any phase from its Brief (constituent skill not installed), read references/methods.md first — it carries each phase's full method, checklists, formulas, and benchmarks; the Brief is only the summary.
Phase 1 — Find the leak (lean-analytics) — GATE
Purpose: Locate where the flow actually loses people and pick the one metric this journey moves — before any opinion about why.
Brief (fallback): A good metric is a comparative ratio that changes what you do next; totals and cumulative charts are vanity. Express each step of the flow as a conversion rate, compare against your own history and published benchmarks (e-commerce converts ~1-3% of visitors; landing pages on paid traffic low single digits), and find the biggest absolute drop on the highest-value path. Pick the One Metric That Matters for this journey, pair it with a counter-metric so it can't be gamed (signup rate × 30-day retention), and draw a line in the sand: target, date, pre-committed miss response. Cohort and segment (channel, device, plan) — one collapsing segment hides inside a flat average.
Invoke: Use the lean-analytics skill with the flow steps and analytics from intake. Ask for a step-by-step funnel table with baselines and benchmarks, the OMTM plus counter-metric for this journey, and the biggest leak ranked by absolute lost value.
Decide with the user: (1) Confirm the OMTM and its counter-metric. (2) Which leak to attack first — biggest absolute loss on the money path, not the easiest percentage. (3) If instrumentation is missing, which minimal events to add first — the phase stays awaiting-evidence until the numbers exist.
Artifact: Extend docs/METRICS.md ## Funnel (stage | conversion | benchmark | bottleneck?), ## Stage & One Metric That Matters, and ## Baselines & Targets. Update the tracker.
Done when: the funnel is measured at the coarsest granularity that still localizes the leak to a single step, the OMTM and counter-metric are recorded with a line in the sand, and the leak is named — only then are Phases 2-7 unlocked. Finer sub-steps awaiting instrumentation stay awaiting-evidence in Next Actions and do not block the journey, provided the named leak does not depend on them.
Phase 2 — Research why they leave (cro-methodology) — GATE
Purpose: Replace guesses about the leak with evidence from real visitors. Phases 3-6 may only fix problems traceable to a finding here.
Brief (fallback): Don't guess — discover. Mine primary sources (a one-question exit survey: "What's preventing you from [action] today?"; post-conversion: "What almost stopped you?"; chat logs, tickets, sales calls) and secondary sources (reviews, competitors) for the customer's own words. Sort objections into the Big 5 — Trust, Price, Fit, Timing, Effort — and build the O/CO table: every objection gets an evidence-backed counter placed at the exact step the doubt arises, never in an FAQ. Diagnose each step with the LIFT lenses (value proposition ± clarity, relevance, urgency, minus anxiety and distraction — Goward) and the MECLABS heuristic (conversion rises with motivation and value clarity, falls with friction and anxiety). Rank fix hypotheses by ICE and apply the 10x screen: if a change couldn't plausibly double the step, don't queue it.
Invoke: Use the cro-methodology skill with the Phase 1 leak, the flow, and the voice-of-customer sources from intake. Ask for the researched objection list in customer words, the O/CO table with placements, missing persuasion assets, and an ICE-ranked hypothesis backlog.
Decide with the user: (1) Which researched objection is the primary leak driver. (2) Low traffic: accept qualitative plus heuristic evidence — explicitly. (3) Which implicit objections
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
x402
121.0kSet up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
