agentleFS
OpenClaudiaOpenClaudia/openclaudia-skills/skills/signup-flow-cro/SKILL.md

signup-flow-cro

Skill731 starsChanged 5 months agoMITView on GitHub

Optimize signup and registration conversion funnels. Use when asked to improve signup rates, reduce form abandonment, audit registration flows, or optimize conversion funnels. Trigger phrases: "signup optimization", "registration flow", "form conversion", "signup CRO", "reduce abandonment", "signup funnel", "form optimization", "conversion rate optimization", "registration page".

48 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-marketing-context, aso-audit and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 20 projects that use this

  • ai-vitaSkill

    aso-audit

    When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

    Also in 5 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 18 projects that use this

  • VercelSkill

    site-architecture

    Use when planning or restructuring what pages a site has and how they connect: hierarchy, navigation, URL patterns, breadcrumbs, and internal linking. Not for XML sitemaps, which are in seo-audit.

    Also in 18 projects that use this

  • buildingwithaiSkill

    sales-enablement

    Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.

    Also in 18 projects that use this

  • ukunal91appSkill

    churn-prevention

    When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.

    Also in 17 projects that use this

  • +5 more from ukunal91app

The file

Show its rules and text

We split this skill into the rules it gives an agent

19 rules. 0 are common, 19 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 47 edited versions we read keep these.

  • 19

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When auditing a signup flow, evaluate each of these dimensions:

    line 19
  2. Distinctive:

    Rule of thumb: Every additional step loses 10-20% of users.

    line 30
  3. Distinctive:

    Do fields use appropriate input types (email, tel, etc.)?

    line 50
  4. Distinctive:

    Do social logins request minimal permissions?

    line 65
  5. Distinctive:

    Test: Replace "Create Account" button with "Get Started Free" or "Start in 30 seconds"

    line 137
  6. Distinctive:

    Test: Add "Join 10,000+ teams" or user count next to signup button

    line 141
  7. Distinctive:

    Test: Add screenshot or demo GIF above signup form

    line 145
  8. Distinctive:

    Test: Remove pricing tiers from signup page.

    line 149
  9. Distinctive:

    Test: Show "Continue with Google" as the primary/largest button, email form secondary

    line 155
  10. Distinctive:

    Test: Email-only signup (collect name later) vs email + name + password

    line 159
  11. Distinctive:

    Test: "Enter email, we'll send a login link" vs traditional password creation

    line 163
  12. Distinctive:

    Test: Add show/hide password toggle

    line 167
  13. Distinctive:

    Test: Add "Skip for now" option to profile step

    line 173
  14. Distinctive:

    Test: Add micro-copy explaining why each field is needed ("We use this to personalize your dashboard")

    line 177
  15. Distinctive:

    Test: Use icon/image cards for preference selection vs dropdown/text

    line 181
  16. Distinctive:

    Test: Let users access the product immediately, verify email later

    line 187
  17. Distinctive:

    Test: Offer phone verification as alternative to email

    line 191
  18. Distinctive:

    Test: Drop users into a pre-populated workspace vs empty state

    line 197
  19. Distinctive:

    When auditing a signup flow, produce this report:

    line 290

“Common” is measured: kept by at least 6 in 10 of the 47 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Signup Flow CRO

Audit and optimize signup conversion funnels to maximize registration completions.


1. Signup Flow Audit Framework

When auditing a signup flow, evaluate each of these dimensions:

Number of Steps

StepsBenchmark Completion RateNotes
1 (single page)65-80%Best for simple products
250-65%Good balance of data collection and UX
335-50%Acceptable for complex products
4+20-35%Only if justified by product complexity

Rule of thumb: Every additional step loses 10-20% of users.

Audit questions:

  • Can any steps be combined?
  • Can any steps be deferred to post-signup?
  • Is every step necessary for the user to start getting value?

Form Fields

FieldsImpact on Conversion
Email onlyHighest conversion (baseline)
Email + password-10-15% vs email only
Email + password + name-15-25% vs email only
5+ fields-30-50% vs email only

Audit questions:

  • Which fields are truly required at signup? (vs. collected later)
  • Can you use progressive profiling instead of upfront collection?
  • Are field labels clear and unambiguous?
  • Do fields use appropriate input types (email, tel, etc.)?
  • Are there unnecessary fields (phone, company size, "how did you hear about us")?

Social Login Options

ProviderTypical LiftBest For
Google+15-25%B2B, SaaS, productivity tools
Apple+5-15%iOS-first products, privacy-conscious users
GitHub+10-20%Developer tools
Microsoft+5-15%Enterprise, Office-adjacent tools
Facebook+5-10%B2C, social products (declining trust)

Audit questions:

  • Are social login buttons prominent or buried?
  • Do social logins request minimal permissions?
  • Is there a fallback if social auth fails?

Progress Indicators

For multi-step flows, progress indicators reduce abandonment.

Types:

  • Step counter ("Step 2 of 3")
  • Progress bar (visual fill)
  • Checklist (shows completed and upcoming steps)
  • Breadcrumb ("Account > Profile > Preferences")

Best practice: Show remaining steps, not total steps. "Just 1 more step" is more motivating than "Step 3 of 4."

Error Handling

Audit checklist:

  • Inline validation (errors appear next to the field, not at top of form)
  • Real-time validation (check as user types, not on submit)
  • Clear error messages (say what's wrong AND how to fix it)
  • Password requirements shown upfront (not after failed attempt)
  • Email format validation with helpful suggestion ("Did you mean gmail.com?")
  • Preserve entered data on error (never clear the form)
  • Specific duplicate account messaging ("An account with this email exists. Log in?")

Mobile Optimization

Audit checklist:

  • Form fills the viewport without horizontal scroll
  • Input fields are at least 44px tap targets
  • Keyboard type matches input (email keyboard for email, number pad for phone)
  • Auto-focus on first field
  • Sticky CTA button visible without scrolling
  • No CAPTCHA that's hard to solve on mobile (use invisible reCAPTCHA)
  • Social login buttons work smoothly on mobile

2. Benchmark Conversion Rates by Industry

Visitor-to-Signup Rates

IndustryFree SignupFree TrialPaid Signup
SaaS (B2B)2-5%3-8%1-3%
SaaS (B2C)5-15%5-10%2-5%
E-commerce2-4%N/A2-4%
Media/Content5-10%N/A1-2%
FinTech1-3%N/A0.5-2%
EdTech3-8%5-12%1-3%
Health/Fitness5-10%8-15%2-5%
Developer Tools8-15%10-20%2-5%
Marketplace3-8%N/AN/A

Signup-to-Activation Rates

Product TypeBenchmark
Self-serve SaaS20-40%
Free trial (no CC)15-25%
Free trial (CC required)40-60%
Freemium10-20%
Mobile app15-30%

3. A/B Test Hypotheses by Step

Pre-Signup (Landing Page to Signup Start)

Hypothesis 1: Reducing perceived effort increases signup starts

  • Test: Replace "Create Account" button with "Get Started Free" or "Start in 30 seconds"
  • Expected lift: 5-15%

Hypothesis 2: Social proof near CTA increases conversion

  • Test: Add "Join 10,000+ teams" or user count next to signup button
  • Expected lift: 5-12%

Hypothesis 3: Showing the product increases intent

  • Test: Add screenshot or demo GIF above signup form
  • Expected lift: 10-20%

Hypothesis 4: Reducing options increases action

  • Test: Remove pricing tiers from signup page; show one clear CTA
  • Expected lift: 8-15%

Step 1: Account Creation

Hypothesis 5: Social login as primary option reduces friction

  • Test: Show "Continue with Google" as the primary/largest button, email form secondary
  • Expected lift: 15-25%

Hypothesis 6: Fewer fields increase completion

  • Test: Email-only signup (collect name later) vs email + name + password
  • Expected lift: 10-20%

Hypothesis 7: Magic link eliminates password friction

  • Test: "Enter email, we'll send a login link" vs traditional password creation
  • Expected lift: 5-15% (higher for mobile)

Hypothesis 8: Password visibility toggle reduces errors

  • Test: Add show/hide password toggle
  • Expected lift: 3-8%

Step 2: Profile / Preferences

Hypothesis 9: Making profile completion optional increases flow-through

  • Test: Add "Skip for now" option to profile step
  • Expected lift: 15-25%

Hypothesis 10: Explaining why increases willingness

  • Test: Add micro-copy explaining why each field is needed ("We use this to personalize your dashboard")
  • Expected lift: 5-10%

Hypothesis 11: Visual selection beats text input

  • Test: Use icon/image cards for preference selection vs dropdown/text
  • Expected lift: 8-15%

Step 3: Verification

Hypothesis 12: Delayed email verification increases activation

  • Test: Let users access the product immediately, verify email later
  • Expected lift: 20-40% on activation rate

Hypothesis 13: SMS verification is faster than email

  • Test: Offer phone verification as alternative to email
  • Expected lift: 5-10% on verification completion

Post-Signup

Hypothesis 14: Immediate value delivery reduces churn

  • Test: Drop users into a pre-populated workspace vs empty state
  • Expected lift: 15-30% on day-1 retention

4. Signup Page Templates

Minimal (Email-Only)

[Logo]

Get started with [Product]

[Email input field]
[Continue button: "Start Free"]

or continue with [Google] [Apple]

Already have an account? Log in

[Privacy note: "No credit card required. Free forever for individuals."]

Standard (Email + Password)

[Logo]

Create your [Product] account

[Continue with Google]
[Continue with Apple]

---- or ----

[Email input]
[Password input] [show/hide toggle]
[Continue button]

By signing up, you agree to our Terms and Privacy Policy.

Already have an account? Log in

Multi-Step

Step 1: Account
[Logo]
"Let's set up your account"
[Email] [Password] [Continue]

Step 2: About You (optional)
"Help us personalize your experience"
[Role dropdown] [Company size] [Use case cards]
[Continue] [Skip for now]

Step 3: Workspace
"Name your workspace"
[Workspace name input]
[Invite teammates (optional): email1, email2]
[Get Started]

5. Friction Reducers

Micro-Copy That Converts

LocationCopyPurpose
Below CTA"Free forever. No credit card."Remove risk
Below CTA"Setup takes 30 seconds"Set expectation
By email field"We'll never spam you"Build trust
By password field"8+ characters"Prevent errors
By social login"We only access your name and email"Privacy assurance
After form"Join 50,000+ users"Social proof

Trust Signals

  • Security badges (SSL, SOC2, GDPR)
  • Customer logos (if B2B)
  • Review scores (G2, Capterra, Trustpilot)
  • "As featured in" media logos
  • Number of users or companies
  • Data privacy statement

6. Signup Flow Audit Output Template

When auditing a signup flow, produce this report:

## Signup Flow Audit: [Product Name]
### Audit Date: [Date]

### Current Flow
- Steps: [X]
- Fields: [List all fields]
- Social login: [Yes/No, which providers]
- Mobile optimized: [Yes/Partial/No]
- Time to complete: ~[X] seconds

### Scores (1-10)
| Dimension | Score | Notes |
|-----------|-------|-------|
| Simplicity | X | [Why] |
| Mobile UX | X | [Why] |
| Error handling | X | [Why] |
| Trust signals | X | [Why] |
| Speed/friction | X | [Why] |
| **Overall** | **X** | |

### Issues Found
1. **[Critical]** [Issue description]
   - Impact: [Estimated conversion loss]
   - Fix: [Specific recommendation]

2. **[High]** [Issue description]
   - Impact: [Estimated conversion loss]
   - Fix: [Specific recommendation]

3. **[Medium]** [Issue description]
   ...

### Recommended A/B Tests (Priority Order)
1. [Test description] - Expected lift: X%
2. [Test description] - Expected lift: X%
3. [Test description] - Expected lift: X%

### Quick Wins (No A/B Test Needed)
- [ ] [Fix description] - implement immediately
- [ ] [Fix description] - implement immediately

7. Tools for Signup CRO

ToolUse CasePrice
Hotjar / Microsoft ClarityHeatmaps, session recordings, form analyticsFree tier available
Google Optimize (sunset) / VWOA/B testing$0-$199/mo
Amplitude / MixpanelFunnel analysis, drop-off trackingFree tier available
Crazy EggClick maps, scroll maps$29/mo+
FullStorySession replay, frustration detectionFree tier available
FormisimoForm field analyticsCustom pricing

Key Metrics to Track

MetricHow to Measure
Signup page visit rateGA4: page views on signup URL
Signup start rate% who interact with first field or click social login
Field-level drop-offForm analytics tool (which field causes abandonment)
Signup completion rateCompleted signups / signup page visits
Time to completeSession recording analysis
Error rate% of submissions with validation errors
Social vs email split% using each method

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.