Signup
Tune trial, freemium, and paid registration flows so more visitors finish account creation.
Overview
Signup is an agent skill for the Validate phase that diagnoses and improves registration, trial, and account-creation flows for solo builders.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill signupWhat is this skill?
- Classifies flow type: free trial, freemium, paid, waitlist, B2B vs B2C
- Audits steps, required fields, and friction before recommending changes
- Reads `.agents/product-marketing.md` (or legacy paths) to skip redundant questions
- Separates signup CRO from post-signup onboarding and non-account lead forms
- Triggered by signup abandonment, trial conversion, and "too many steps to sign up" language
- Initial assessment covers 2 dimensions: flow type and current state (steps/fields)
Adoption & trust: 14.5k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Visitors hit your signup or trial flow but abandon before they finish creating an account.
Who is it for?
Founders shipping SaaS or freemium products who can describe their current signup screens and required fields.
Skip if: Post-signup product tours and checklists (use onboarding) or ebook-style lead magnets without account creation (use cro or lead-magnets).
When should I use this skill?
User mentions signup conversions, registration friction, free trial signup, reduce signup dropoff, account creation flow, signup abandonment, or simplify our signup.
What do I get? / Deliverables
You get flow-type-specific CRO guidance on steps, fields, and friction so more people complete registration; for activation after signup, use the onboarding skill next.
- Signup flow CRO recommendations
- Friction and field-level improvement guidance
Recommended Skills
Journey fit
Signup CRO is where solo builders prove the landing-to-account step converts before scaling build and growth spend. Landing and trial entry pages are the usual surface where registration friction and dropoff show up first.
How it compares
Account-creation CRO only—not a full-funnel cro playbook or onboarding sequence designer.
Common Questions / FAQ
Who is signup for?
Solo and indie builders optimizing free-trial, freemium, paid, or waitlist registration flows when completion rates are weak.
When should I use signup?
During Validate when you are testing landing-to-account conversion, simplifying trial signup, or responding to dropoff between pricing and account creation.
Is signup safe to install?
Review the Security Audits panel on this Prism page and inspect the skill source in your repo before letting an agent act on production analytics or customer data.
Workflow Chain
Then invoke: onboarding
SKILL.md
READMESKILL.md - Signup
# 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 **Check for product marketing context first:** If `.agents/product-marketing.md` exists (or `.claude/product-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. 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 questi