Signup Flow CRO
Optimize the signup and trial conversion flow for "$ARGUMENTS". Reduce friction, increase activation, and improve trial-to-paid conversion.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"marketing-signup-flow-cro","workflow":"marketing","phase":3,"project":"<project>","event":"skipped","artifact":"03-convert.md","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 3 (Convert) of the RACE Framework workflow (marketing); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or marketing when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"marketing-signup-flow-cro","workflow":"marketing","phase":3,"project":"<project>","event":"refused","artifact":"03-convert.md","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"marketing-signup-flow-cro","workflow":"marketing","phase":3,"project":"<project>","event":"started","artifact":"03-convert.md","note":""}.
Read .singularskills/marketing/<project>/00-strategy.md. If this file does not exist, tell the user:
Phase 0 (Strategy) has not been completed for "". Run
/marketing-customer-research <project>first, or use--skip-checksto bypass.
Process
Read context:
- Read
.singularskills/marketing/<project>/00-strategy.mdfor audience and pricing - Read
.singularskills/marketing/<project>/02-act.mdif it exists (for page and form CRO context)
- Read
Map the current flow (if URL provided):
- Use WebFetch to walk through the signup flow
- Document every step: pages, forms, emails, activation steps
- Identify drop-off points and friction
Signup page optimization:
- Value proposition clarity on signup page
- Social proof placement
- Form field minimization (name + email is ideal)
- SSO/social login options
- Mobile signup experience
Activation optimization:
- What is the "aha moment"? How quickly can users reach it?
- Onboarding checklist or wizard design
- Empty state design — what does the user see first?
- Time-to-value: how to reduce it
Trial-to-paid conversion:
- Trial length recommendation
- In-trial email nudges — hand off to
/marketing-email-sequence; keep the in-product prompts here. - Upgrade triggers: what behavior indicates readiness?
- Pricing page from within the product
- Payment friction reduction
Write the artifact — append to
.singularskills/marketing/<project>/03-convert.mdunder a## Signup Flow CROsection. Create the file with a# Convert — <project>heading if it does not exist; if a## Signup Flow CROsection already exists, replace only that section. The section contains:- Current Flow Map — step-by-step with friction points
- Signup Page Recommendations — optimization list
- Activation Strategy — path to aha moment
- Trial-to-Paid Plan — engagement and conversion tactics
- A/B Test Ideas — highest-impact tests
Output
Signup flow analysis appended to .singularskills/marketing/<project>/03-convert.md. Present a summary highlighting:
- Biggest friction point identified
- Recommended activation improvements
- Expected conversion lift
Record the run. After you have written your section, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"marketing-signup-flow-cro","workflow":"marketing","phase":3,"project":"<project>","event":"finished","artifact":"03-convert.md","note":""}.
This artifact is shared by every skill of phase 3 (Convert). The frontmatter is written once, by whoever creates the file: if you create it, open it with the block below (skill is the phase title, started the time of that first write; gate is passed when the gate ran clean and skipped under --skip-checks); if it already exists, leave the block alone except to update finished and to set gate to the worst value among the sections (skipped over passed).
---
skill: Convert
workflow: marketing
phase: 3
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
Open your ## Signup Flow CRO section with one italic line, *<skill name> · <ISO timestamp> · gate: <passed|skipped>* (your skill name is marketing-signup-flow-cro).
End your section with ### Decisions and ### Open questions (one level under your ## Signup Flow CRO heading, so the section stays one block), in this shape:
### Decisions
- <what was chosen> — <why> — <what was rejected>
### Open questions
- <what the next phase or a reviewer must settle>