signup-flow-cro
Signup and registration flow optimization covering SSO strategy, progressive profiling, field reduction, multi-step flow design, authentication UX, post-submit experience, and mobile registration patterns.
Install / Use
npx skills add borghei/Claude-Skills --skill signup-flow-croInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of signup-flow-cro
signup-flow-cro scores 92/100 on our quality scale, 943rd of 4,702 Development & Engineering skills we index (top 21%).
Its SKILL.md is 23 KB long, well organised into 53 sections with 8 code examples: a thorough specification that gives an agent plenty to work with.
It has 817 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so signup-flow-cro is actively maintained.
- Our last check on 2026-10-28 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. 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-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
signup-flow-cro compared with similar skills
All 4 of these similar skills score higher than signup-flow-cro; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| signup-flow-cro (this skill)by borghei | 92 | 817 | 57d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 117.6k | 9d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.3k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 3d ago | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.9k | 8d ago | CLAUDE.md |
Frequently asked questions
- How do I install signup-flow-cro?
- Run
npx skills add borghei/Claude-Skills --skill signup-flow-cro. The install tabs above show the steps for each supported agent. - Which AI agents does signup-flow-cro 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 signup-flow-cro 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 declares no license and scores 88/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 signup-flow-cro still maintained?
- The repository was last updated about 2 months ago, so signup-flow-cro is actively maintained.
Skill content
View source on GitHubname: signup-flow-cro description: > Signup and registration flow optimization covering SSO strategy, progressive profiling, field reduction, multi-step flow design, authentication UX, post-submit experience, and mobile registration patterns. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: [cro, signup, registration, authentication, conversion-optimization]
Signup Flow CRO
Production-grade signup and registration optimization framework covering authentication strategy, field reduction methodology, multi-step flow architecture, SSO implementation, progressive profiling, credit card requirement analysis, post-submit experience design, and mobile-specific registration patterns. For post-signup onboarding, use onboarding-cro. For lead capture forms (not account creation), use form-cro.
Table of Contents
- Initial Assessment
- Authentication Strategy
- Field Reduction Methodology
- Multi-Step Flow Architecture
- Credit Card Requirement Analysis
- Post-Submit Experience
- Mobile Signup Optimization
- Signup Flow Patterns by Product Type
- Progressive Profiling
- Error and Edge Case Handling
- A/B Test Framework
- Metrics and Benchmarks
- Output Artifacts
- Related Skills
Clarify First
Before optimizing the signup flow, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Flow type — free trial, freemium, paid, or waitlist (determines friction tolerance and minimum field set)
- [ ] B2B or B2C — B2B tolerates more fields; B2C needs minimal friction (sets SSO priority and field count)
- [ ] Current fields + completion rate + drop-off — baseline and the friction point to cut (each removed field ~+10%)
- [ ] Data truly needed before first product use — separates must-have fields from those to defer or enrich (the "Before First Use" test)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the audit.
Initial Assessment
Required Context
| Question | Why It Matters | |----------|---------------| | Flow type? (free trial, freemium, paid, waitlist) | Determines friction tolerance | | B2B or B2C? | B2B tolerates more fields, B2C needs minimal friction | | How many steps/screens currently? | Baseline for optimization | | What fields are required? | Identifies reduction opportunities | | Current completion rate? | Benchmark for improvement | | Where do users drop off? (field-level data) | Pinpoints specific friction | | What data is needed before first product use? | Separates must-have from nice-to-have | | What compliance requirements exist? | Constrains what can be deferred |
Authentication Strategy
Authentication Methods Ranked by Friction
| Method | Friction Level | Best For | Conversion Impact | |--------|---------------|----------|------------------| | Google SSO (one-click) | Very low | B2B SaaS, productivity tools | +15-30% vs email+password | | Apple Sign In | Very low | iOS/Mac-heavy audience | +10-20% on Apple devices | | Microsoft SSO | Low | Enterprise B2B | +10-15% for enterprise | | GitHub SSO | Low | Developer tools | +15-25% for dev audience | | Magic link (email) | Low | Security-conscious, B2B | +5-10% vs password | | Email + password | Medium | Universal fallback | Baseline | | Phone + OTP | Medium | Mobile-first, B2C | Varies by market | | Email + password + verification | High | When verification is required | -10-20% vs no verification |
SSO Strategy Decision
| Your Audience | Primary SSO | Secondary SSO | Keep Email+Password? | |--------------|-------------|---------------|---------------------| | B2B SaaS (general) | Google Workspace | Microsoft | Yes | | Developer tools | GitHub | Google | Yes | | Enterprise | Microsoft/Okta | Google | Yes (for personal evals) | | B2C consumer | Google | Apple | Yes | | Mobile-first | Apple / Google | Phone OTP | Optional | | Privacy-focused | Magic link | Email+password | Yes |
SSO Placement
┌──────────────────────────────────┐
│ Create your account │
│ │
│ [Continue with Google] │ ← SSO options first
│ [Continue with Microsoft] │
│ │
│ ──── or ──── │ ← Visual separator
│ │
│ Email: [_______________] │ ← Email+password as alternative
│ Password: [_______________] │
│ │
│ [Create Account] │
└──────────────────────────────────┘
Rules:
- SSO buttons above the email form (not below)
- Use branded button styles (Google's official button, etc.)
- "or" divider between SSO and email options
- SSO reduces fields to zero (name and email come from the provider)
Field Reduction Methodology
The "Before First Use" Test
For every field, ask: Does the product literally not function without this data?
| Field | Passes Test? | Action | |-------|-------------|--------| | Email | Yes (account identity) | Keep | | Password | Yes (account security) | Keep (or use SSO/magic link) | | First name | Usually no | Defer to onboarding or profile | | Last name | No | Defer or drop entirely | | Company name | Usually no | Enrich from email domain | | Phone number | Rarely | Defer unless SMS verification required | | Job title | No | Defer to onboarding or enrich | | Team size | No | Defer to onboarding | | How did you hear about us? | Never | Post-signup survey or attribution | | Industry | No | Enrich from company data |
Enrichment Sources
| Field | Enrichment Method | Timing | |-------|-------------------|--------| | Company name | Email domain lookup (Clearbit, Apollo) | Immediately post-signup | | Company size | Company data API | Immediately post-signup | | Industry | Company data API | Immediately post-signup | | Job title | LinkedIn API or manual CSM research | Before first sales contact | | Location | IP geolocation | On signup |
Minimum Viable Field Sets
| Signup Type | Minimum Fields | Additional (if needed) | |------------|----------------|----------------------| | Freemium | Email only (or SSO) | -- | | Free trial (product-led) | Email + Password (or SSO) | -- | | Free trial (sales-assisted) | Email + Password + Company | + Role (for routing) | | Paid signup | Email + Password + Payment | -- | | Waitlist | Email | + One qualifying question | | Enterprise trial | Email + Company + Role | + Team size (for provisioning) |
Multi-Step Flow Architecture
When to Use Multi-Step
| Condition | Single-Step | Multi-Step | |-----------|------------|------------| | Total fields | 1-4 | 5+ | | Need to qualify/route | No | Yes | | Product needs configuration | No | Yes | | B2B with team setup | No | Yes |
Step Design
Step 1: Account Creation (lowest friction)
- Email + Password (or SSO)
- NOTHING else on this step
- This is where 60%+ of abandonment happens if overloaded
Step 2: Personalization (if needed)
- Role / goal / use case selection
- This personalizes their product experience
- Skip button available ("Set up later")
Step 3: Configuration (if needed)
- Team invite, integration connect, data import
- Each sub-step is optional with "Skip for now"
- Show value of completing each ("Invite your team to collaborate")
Progress Design
- Show step count: "Step 1 of 3"
- Show progress bar
- Label each step descriptively: "Create Account", "Your Role", "Your Team"
- Allow back navigation (preserve entered data)
- Never reset the form on back navigation or browser back button
Credit Card Requirement Analysis
Decision Framework
| Factor | Require CC | Do Not Require CC | |--------|-----------|------------------| | Trial conversion goal | > 60% trial-to-paid | > 30% trial-to-paid with higher volume | | Product complexity | Simple, immediate value | Complex, needs exploration | | ACV | > $100/month | < $100/month | | Sales motion | Product-led | Sales-assisted | | Competitor practice | Competitors require CC | Competitors offer CC-free trial | | Target audience | Enterprise (committed buyers) | SMB/prosumer (browsers) |
Impact Analysis
| Approach | Signup Volume | Trial Quality | Trial-to-Paid | Net Revenue | |----------|-------------|---------------|---------------|-------------| | No CC required | Higher (+40-80%) | Lower (more tire-kickers) | Lower (2-15%) | Often higher net | | CC required | Lower | Higher (committed) | Higher (40-70%) | Depends on volume | | CC with "$0 charge" | Middle | Middle | Middle (20-40%) | Middle |
Recommendation Framework
Default to no CC required unless:
- Your product delivers immediate, obvious value (no learning curve)
- Your trial-to-paid with CC is > 50%
- You have a high-touch sales team to handle lower volume
- Support costs for free trials are unsustainable
If requiring CC: Display prominently:
- "You won't be charged until [date]"
- "Cancel anytime before [date]"
- "We'll email you 3 days before your trial ends"
Post-Submit Experience
Immediately After Signup
| Element | Implementation | |---------|---------------| | Auto-login | Log the user in immediately (never force a separate login) | | Welcome screen | Show a clear next step, not a blank dashboard | | Confirmation email | Send immediately, include: what to expect, key features, support contact | | Email verification | Defer if possible. If required, send inline and let them continue using the product before verifying |
Email Verification Strategy
| Approach | Impact on Activation | When to Use | |----------|---------------------|-------------| | No verification | Best activation rate | Low-risk products, freemium | | Verify to unlock specific feature | Good -- users activate first | B2B SaaS with free tier | | Verify within 24 hours | Moderate -- creates urgency | Products that send emails | | Verify before any use | Worst activation rate | Regulated industries, financial products |
Default recommendation: Let users use the product immediately. Verify within 24-48 hours. Gate only the features that require a verified email (e.g., sending emails, team invites).
Mobile Signup Optimization
Mobile-Specific Rules
| Rule | Implementation |
|------|---------------|
| SSO first | Google/Apple Sign In is one tap on mobile |
| One column | Never use side-by-side fields on mobile |
| Large inputs | Minimum 44px height for all touch targets |
| Appropriate keyboards | type="email", type="tel", type="password" |
| Auto-fill support | Use standard field names for browser auto-fill |
| Sticky CTA | Pin "Create Account" button to bottom of viewport |
| No CAPTCHA | Use invisible reCAPTCHA or alternatives |
| Password visibility | Toggle to show/hide password |
Mobile vs Desktop Signup Differences
| Aspect | Desktop | Mobile | |--------|---------|--------| | Primary auth | SSO or Email+Password | SSO preferred (one-tap) | | Fields per screen | Up to 5 | Max 3 | | Password rules | Show requirements upfront | Show on interaction | | CAPTCHA | Standard reCAPTCHA acceptable | Invisible or none | | Social proof | Sidebar or adjacent | Below form or above |
Signup Flow Patterns by Product Type
B2B SaaS Trial
[Google SSO] or [Email + Password]
→ Auto-login to product
→ Welcome screen: "What brings you here?" (3 options)
→ Guided first action based on selection
→ Team invite prompt (optional, day 2-3)
B2C Consume
Truncated for display — read the full file on GitHub.
Related Skills
taste-skill
117.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.3kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Claude-Code-Game-Studios
39.9kTurn Claude Code into a full game dev studio — 49 AI agents, 75 workflow skills, and a complete coordination system mirroring real studio hierarchy.
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.
