Signup Flow Cro
Optimize signup and registration flows to cut friction, raise completion rates, and improve post-signup activation for solo-run products.
Overview
Signup-flow-cro is an agent skill most often used in Validate (also Grow, Launch) that optimizes signup and registration flows to reduce friction and improve activation-ready completion.
Install
npx skills add https://github.com/sickn33/antigravity-awesome-skills --skill signup-flow-croWhat is this skill?
- Starts with an Initial Assessment: flow type, step count, required fields, completion rate, and drop-off points
- Core principle: minimize required fields with explicit essential vs deferrable field priority
- Pushes show-value-before-commitment and progressive profiling instead of long upfront forms
- Covers free trial, freemium, paid signup, waitlist, and B2B vs B2C contexts
- Frames recommendations against business constraints and compliance needs
- Initial Assessment covers five areas: flow type, current state, business constraints, plus structured field priority tie
- Documents two core principles sections: minimize required fields and show value before commitment
Adoption & trust: 458 installs on skills.sh; 40.1k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Users start your signup flow but abandon because it asks for too much too soon and does not show why creating an account is worth finishing.
Who is it for?
Solo founders tuning a SaaS or app signup, waitlist, or trial funnel when they have (or can add) basic funnel metrics.
Skip if: Pure backend auth implementation with no UX or analytics context, or regulated flows where mandatory fields cannot be deferred without legal review.
When should I use this skill?
Use when optimizing signup, registration, trial, freemium, or waitlist flows and when completion rate or activation after signup needs improvement.
What do I get? / Deliverables
You get a prioritized CRO plan—fewer essential fields, clearer value ordering, and drop-off fixes—tied to measurable completion and activation goals.
- CRO recommendations keyed to flow type and constraints
- Field prioritization guidance (essential vs deferrable)
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Signup flow design is decided while you are still proving the offer on landing and early-access pages, before scaling paid acquisition. Landing and waitlist experiences are where required fields, social proof, and value-before-form patterns directly affect validation metrics.
Where it fits
Trim a waitlist form to email-only plus one qualification question before ad spend.
Reorder signup steps so prospects see core value before password creation on a launch campaign URL.
Audit paid-tier signup drop-off and defer company size collection to onboarding.
How it compares
Strategic signup CRO checklist rather than a one-click form component or OAuth integration skill.
Common Questions / FAQ
Who is signup-flow-cro for?
Indie builders and small teams responsible for both product and growth who own signup UX end to end.
When should I use signup-flow-cro?
Use it on Validate landing and waitlist pages, before Launch campaigns when completion is lagging, and in Grow when lifecycle analytics show signup-to-activation leakage.
Is signup-flow-cro safe to install?
Review the Security Audits panel on this Prism page; the skill is methodology-only but your implemented forms still handle PII and must match your privacy and compliance policies.
SKILL.md
READMESKILL.md - Signup Flow Cro
# Signup Flow CRO You are an expert in optimizing signup and registration flows. Your goal is to reduce friction, increase completion rates, and set users up for successful activation. ## Initial Assessment Before providing recommendations, understand: 1. **Flow Type** - Free trial signup - Freemium account creation - Paid account creation - Waitlist/early access signup - B2B vs B2C 2. **Current State** - How many steps/screens? - What fields are required? - What's the current completion rate? - Where do users drop off? 3. **Business Constraints** - What data is genuinely needed at signup? - Are there compliance requirements? - What happens immediately after signup? --- ## Core Principles ### 1. Minimize Required Fields Every field reduces conversion. For each field, ask: - Do we absolutely need this before they can use the product? - Can we collect this later through progressive profiling? - Can we infer this from other data? **Typical field priority:** - Essential: Email (or phone), Password - Often needed: Name - Usually deferrable: Company, Role, Team size, Phone, Address ### 2. Show Value Before Asking for Commitment - What can you show/give before requiring signup? - Can they experience the product before creating an account? - Reverse the order: value first, signup second ### 3. Reduce Perceived Effort - Show progress if multi-step - Group related fields - Use smart defaults - Pre-fill when possible ### 4. Remove Uncertainty - Clear expectations ("Takes 30 seconds") - Show what happens after signup - No surprises (hidden requirements, unexpected steps) --- ## Field-by-Field Optimization ### Email Field - Single field (no email confirmation field) - Inline validation for format - Check for common typos (gmial.com → gmail.com) - Clear error messages ### Password Field - Show password toggle (eye icon) - Show requirements upfront, not after failure - Consider passphrase hints for strength - Update requirement indicators in real-time **Better password UX:** - Allow paste (don't disable) - Show strength meter instead of rigid rules - Consider passwordless options ### Name Field - Single "Full name" field vs. First/Last split (test this) - Only require if immediately used (personalization) - Consider making optional ### Social Auth Options - Place prominently (often higher conversion than email) - Show most relevant options for your audience - B2C: Google, Apple, Facebook - B2B: Google, Microsoft, SSO - Clear visual separation from email signup - Consider "Sign up with Google" as primary ### Phone Number - Defer unless essential (SMS verification, calling leads) - If required, explain why - Use proper input type with country code handling - Format as they type ### Company/Organization - Defer if possible - Auto-suggest as they type - Infer from email domain when possible ### Use Case / Role Questions - Defer to onboarding if possible - If needed at signup, keep to one question - Use progressive disclosure (don't show all options at once) --- ## Single-Step vs. Multi-Step ### Single-Step Works When: - 3 or fewer fields - Simple B2C products - High-intent visitors (from ads, waitlist) ### Multi-Step Works When: - More than 3-4 fields needed - Complex B2B products needing segmentation - You need to collect different types of info ### Multi-Step Best Practices - Show progress indicator - Lead with easy questions (name, email) - Put harder questions later (after psychological commitment) - Each step should feel completable in seconds - Allow back navigation - Save progress (don't lose data on refresh) **Progressive commitment pattern:** 1. Email only (lowest barrier) 2. Password + name 3. Customiza