Skill Tracer
Skills › Marketing Skills › signup

signup

skill · 363 lines · MIT · skills/signup/SKILL.md

The facts

Its description

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent picks this skill when someone wants to improve or fix a signup, registration, account-creation, or free-trial activation flow, especially when people are dropping off or not completing it.

Things a person might say (the model's guesses)

  • “Our free trial signup form has a 40% drop-off — how do we fix it?”
  • “People keep abandoning the registration page. Can you help simplify it?”
  • “How do we reduce friction in our account creation flow?”

A model's summary of when it is used.

A model's reading

What it leads to

Other skills this one hands off to, calls, requires or offers instead, as a model read them.

A model's reading

What leads to it

Other skills that hand off to this one, call it, require it or offer it instead, as a model read them.

A model's reading

Licence

MIT, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

Other settings

metadata: version: 2.0.1

More settings at the top of the file, shown as written.

From its settingsline 4
Other files in this skill (1) Close

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: signup
3description: When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.
4metadata:
5 version: 2.0.1
6---
7
8# Signup Flow CRO
9
10You 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.

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.

Raw lines 1 to 11
Names a skill onboarding :3
12## Initial Assessment
14**Check for product marketing context first:**
15If `.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.
17Before providing recommendations, understand:
191. **Flow Type**
20 - Free trial signup
21 - Freemium account creation
22 - Paid account creation
23 - Waitlist/early access signup
24 - B2B vs B2C
262. **Current State**
27 - How many steps/screens?
28 - What fields are required?
29 - What's the current completion rate?
30 - Where do users drop off?
323. **Business Constraints**
33 - What data is genuinely needed at signup?
34 - Are there compliance requirements?
35 - What happens immediately after signup?
37---

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
  2. Free trial signup
  3. Freemium account creation
  4. Paid account creation
  5. Waitlist/early access signup
  6. B2B vs B2C
  1. Current State
  2. How many steps/screens?
  3. What fields are required?
  4. What's the current completion rate?
  5. Where do users drop off?
  1. Business Constraints
  2. What data is genuinely needed at signup?
  3. Are there compliance requirements?
  4. What happens immediately after signup?
Raw lines 12 to 38
39## Core Principles

Core Principles

Raw lines 39 to 40
41### 1. Minimize Required Fields
42Every field reduces conversion. For each field, ask:
43- Do we absolutely need this before they can use the product?
44- Can we collect this later through progressive profiling?
45- Can we infer this from other data?
47**Typical field priority:**
48- Essential: Email (or phone), Password
49- Often needed: Name
50- Usually deferrable: Company, Role, Team size, Phone, Address

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
Raw lines 41 to 51
52### 2. Show Value Before Asking for Commitment
53- What can you show/give before requiring signup?
54- Can they experience the product before creating an account?
55- Reverse the order: value first, signup second

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
Raw lines 52 to 56
57### 3. Reduce Perceived Effort
58- Show progress if multi-step
59- Group related fields
60- Use smart defaults
61- Pre-fill when possible

3. Reduce Perceived Effort

  • Show progress if multi-step
  • Group related fields
  • Use smart defaults
  • Pre-fill when possible
Raw lines 57 to 62
63### 4. Remove Uncertainty
64- Clear expectations ("Takes 30 seconds")
65- Show what happens after signup
66- No surprises (hidden requirements, unexpected steps)
68---

4. Remove Uncertainty

  • Clear expectations ("Takes 30 seconds")
  • Show what happens after signup
  • No surprises (hidden requirements, unexpected steps)
Raw lines 63 to 69
70## Field-by-Field Optimization

Field-by-Field Optimization

Raw lines 70 to 71
72### Email Field
73- Single field (no email confirmation field)
74- Inline validation for format
75- Check for common typos (gmial.com → gmail.com)
76- Clear error messages

Email Field

  • Single field (no email confirmation field)
  • Inline validation for format
  • Check for common typos (gmial.com → gmail.com)
  • Clear error messages
Raw lines 72 to 77
78### Password Field
79- Show password toggle (eye icon)
80- Show requirements upfront, not after failure
81- Consider passphrase hints for strength
82- Update requirement indicators in real-time
84**Better password UX:**
85- Allow paste (don't disable)
86- Show strength meter instead of rigid rules
87- Consider passwordless options

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
Raw lines 78 to 88
89### Name Field
90- Single "Full name" field vs. First/Last split (test this)
91- Only require if immediately used (personalization)
92- Consider making optional

Name Field

  • Single "Full name" field vs. First/Last split (test this)
  • Only require if immediately used (personalization)
  • Consider making optional
Raw lines 89 to 93
94### Social Auth Options
95- Place prominently (often higher conversion than email)
96- Show most relevant options for your audience
97 - B2C: Google, Apple, Facebook
98 - B2B: Google, Microsoft, SSO
99- Clear visual separation from email signup
100- Consider "Sign up with Google" as primary

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
Raw lines 94 to 101
102### Phone Number
103- Defer unless essential (SMS verification, calling leads)
104- If required, explain why
105- Use proper input type with country code handling
106- Format as they type

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
Raw lines 102 to 107
108### Company/Organization
109- Defer if possible
110- Auto-suggest as they type
111- Infer from email domain when possible

Company/Organization

  • Defer if possible
  • Auto-suggest as they type
  • Infer from email domain when possible
Raw lines 108 to 112
113### Use Case / Role Questions
114- Defer to onboarding if possible
115- If needed at signup, keep to one question
116- Use progressive disclosure (don't show all options at once)
118---

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)
Raw lines 113 to 119
120## Single-Step vs. Multi-Step

Single-Step vs. Multi-Step

Raw lines 120 to 121
122### Single-Step Works When:
123- 3 or fewer fields
124- Simple B2C products
125- High-intent visitors (from ads, waitlist)

Single-Step Works When:

  • 3 or fewer fields
  • Simple B2C products
  • High-intent visitors (from ads, waitlist)
Raw lines 122 to 126
127### Multi-Step Works When:
128- More than 3-4 fields needed
129- Complex B2B products needing segmentation
130- You need to collect different types of info

Multi-Step Works When:

  • More than 3-4 fields needed
  • Complex B2B products needing segmentation
  • You need to collect different types of info
Raw lines 127 to 131
132### Multi-Step Best Practices
133- Show progress indicator
134- Lead with easy questions (name, email)
135- Put harder questions later (after psychological commitment)
136- Each step should feel completable in seconds
137- Allow back navigation
138- Save progress (don't lose data on refresh)
140**Progressive commitment pattern:**
1411. Email only (lowest barrier)
1422. Password + name
1433. Customization questions (optional)
145---

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. Customization questions (optional)
Raw lines 132 to 146
147## Trust and Friction Reduction

Trust and Friction Reduction

Raw lines 147 to 148
149### At the Form Level
150- "No credit card required" (if true)
151- "Free forever" or "14-day free trial"
152- Privacy note: "We'll never share your email"
153- Security badges if relevant
154- Testimonial near signup form

At the Form Level

  • "No credit card required" (if true)
  • "Free forever" or "14-day free trial"
  • Privacy note: "We'll never share your email"
  • Security badges if relevant
  • Testimonial near signup form
Raw lines 149 to 155
156### Error Handling
157- Inline validation (not just on submit)
158- Specific error messages ("Email already registered" + recovery path)
159- Don't clear the form on error
160- Focus on the problem field

Error Handling

  • Inline validation (not just on submit)
  • Specific error messages ("Email already registered" + recovery path)
  • Don't clear the form on error
  • Focus on the problem field
Raw lines 156 to 161
162### Microcopy
163- Placeholder text: Use for examples, not labels
164- Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
165- Help text: Only when needed, placed close to field
167---

Microcopy

  • Placeholder text: Use for examples, not labels
  • Labels: Keep visible (not just placeholders) — placeholders disappear when typing, leaving users unsure what they're filling in
  • Help text: Only when needed, placed close to field
Raw lines 162 to 168
169## Mobile Signup Optimization
171- Larger touch targets (44px+ height)
172- Appropriate keyboard types (email, tel, etc.)
173- Autofill support
174- Reduce typing (social auth, pre-fill)
175- Single column layout
176- Sticky CTA button
177- Test with actual devices
179---

Mobile Signup Optimization

  • Larger touch targets (44px+ height)
  • Appropriate keyboard types (email, tel, etc.)
  • Autofill support
  • Reduce typing (social auth, pre-fill)
  • Single column layout
  • Sticky CTA button
  • Test with actual devices
Raw lines 169 to 180
181## Post-Submit Experience

Post-Submit Experience

Raw lines 181 to 182
183### Success State
184- Clear confirmation
185- Immediate next step
186- If email verification required:
187 - Explain what to do
188 - Easy resend option
189 - Check spam reminder
190 - Option to change email if wrong

Success State

  • Clear confirmation
  • Immediate next step
  • If email verification required:
  • Explain what to do
  • Easy resend option
  • Check spam reminder
  • Option to change email if wrong
Raw lines 183 to 191
192### Verification Flows
193- Consider delaying verification until necessary
194- Magic link as alternative to password
195- Let users explore while awaiting verification
196- Clear re-engagement if verification stalls
198---

Verification Flows

  • Consider delaying verification until necessary
  • Magic link as alternative to password
  • Let users explore while awaiting verification
  • Clear re-engagement if verification stalls
Raw lines 192 to 199
200## Measurement

Measurement

Raw lines 200 to 201
202### Key Metrics
203- Form start rate (landed → started filling)
204- Form completion rate (started → submitted)
205- Field-level drop-off (which fields lose people)
206- Time to complete
207- Error rate by field
208- Mobile vs. desktop completion

Key Metrics

  • Form start rate (landed → started filling)
  • Form completion rate (started → submitted)
  • Field-level drop-off (which fields lose people)
  • Time to complete
  • Error rate by field
  • Mobile vs. desktop completion
Raw lines 202 to 209
210### What to Track
211- Each field interaction (focus, blur, error)
212- Step progression in multi-step
213- Social auth vs. email signup ratio
214- Time between steps
216---

What to Track

  • Each field interaction (focus, blur, error)
  • Step progression in multi-step
  • Social auth vs. email signup ratio
  • Time between steps
Raw lines 210 to 217
218## Output Format

Output Format

Raw lines 218 to 219
220### Audit Findings
221For each issue found:
222- **Issue**: What's wrong
223- **Impact**: Why it matters (with estimated impact if possible)
224- **Fix**: Specific recommendation
225- **Priority**: High/Medium/Low

Audit Findings

For each issue found:

  • Issue: What's wrong
  • Impact: Why it matters (with estimated impact if possible)
  • Fix: Specific recommendation
  • Priority: High/Medium/Low
Raw lines 220 to 226
227### Recommended Changes
228Organized by:
2291. Quick wins (same-day fixes)
2302. High-impact changes (week-level effort)
2313. Test hypotheses (things to A/B test)

Recommended Changes

Organized by:

  1. Quick wins (same-day fixes)
  2. High-impact changes (week-level effort)
  3. Test hypotheses (things to A/B test)
Raw lines 227 to 232
233### Form Redesign (if requested)
234- Recommended field set with rationale
235- Field order
236- Copy for labels, placeholders, buttons, errors
237- Visual layout suggestions
239---

Form Redesign (if requested)

  • Recommended field set with rationale
  • Field order
  • Copy for labels, placeholders, buttons, errors
  • Visual layout suggestions
Raw lines 233 to 240
241## Common Signup Flow Patterns

Common Signup Flow Patterns

Raw lines 241 to 242
243### B2B SaaS Trial
2441. Email + Password (or Google auth)
2452. Name + Company (optional: role)
2463. → Onboarding flow

B2B SaaS Trial

  1. Email + Password (or Google auth)
  2. Name + Company (optional: role)
  3. → Onboarding flow
Raw lines 243 to 247
248### B2C App
2491. Google/Apple auth OR Email
2502. → Product experience
2513. Profile completion later

B2C App

  1. Google/Apple auth OR Email
  2. → Product experience
  3. Profile completion later
Raw lines 248 to 252
253### Waitlist/Early Access
2541. Email only
2552. Optional: Role/use case question
2563. → Waitlist confirmation

Waitlist/Early Access

  1. Email only
  2. Optional: Role/use case question
  3. → Waitlist confirmation
Raw lines 253 to 257
258### E-commerce Account
2591. Guest checkout as default
2602. Account creation optional post-purchase
2613. OR Social auth with single click
263---

E-commerce Account

  1. Guest checkout as default
  2. Account creation optional post-purchase
  3. OR Social auth with single click
Raw lines 258 to 264
265## Experiment Ideas

Experiment Ideas

Raw lines 265 to 266
267### Form Design Experiments
269**Layout & Structure**
270- Single-step vs. multi-step signup flow
271- Multi-step with progress bar vs. without
272- 1-column vs. 2-column field layout
273- Form embedded on page vs. separate signup page
274- Horizontal vs. vertical field alignment
276**Field Optimization**
277- Reduce to minimum fields (email + password only)
278- Add or remove phone number field
279- Single "Name" field vs. "First/Last" split
280- Add or remove company/organization field
281- Test required vs. optional field balance
283**Authentication Options**
284- Add SSO options (Google, Microsoft, GitHub, LinkedIn)
285- SSO prominent vs. email form prominent
286- Test which SSO options resonate (varies by audience)
287- SSO-only vs. SSO + email option
289**Visual Design**
290- Test button colors and sizes for CTA prominence
291- Plain background vs. product-related visuals
292- Test form container styling (card vs. minimal)
293- Mobile-optimized layout testing
295---

Form Design Experiments

Layout & Structure

  • Single-step vs. multi-step signup flow
  • Multi-step with progress bar vs. without
  • 1-column vs. 2-column field layout
  • Form embedded on page vs. separate signup page
  • Horizontal vs. vertical field alignment

Field Optimization

  • Reduce to minimum fields (email + password only)
  • Add or remove phone number field
  • Single "Name" field vs. "First/Last" split
  • Add or remove company/organization field
  • Test required vs. optional field balance

Authentication Options

  • Add SSO options (Google, Microsoft, GitHub, LinkedIn)
  • SSO prominent vs. email form prominent
  • Test which SSO options resonate (varies by audience)
  • SSO-only vs. SSO + email option

Visual Design

  • Test button colors and sizes for CTA prominence
  • Plain background vs. product-related visuals
  • Test form container styling (card vs. minimal)
  • Mobile-optimized layout testing
Raw lines 267 to 296
297### Copy & Messaging Experiments
299**Headlines & CTAs**
300- Test headline variations above signup form
301- CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
302- Add clarity around trial length in CTA
303- Test value proposition emphasis in form header
305**Microcopy**
306- Field labels: minimal vs. descriptive
307- Placeholder text optimization
308- Error message clarity and tone
309- Password requirement display (upfront vs. on error)
311**Trust Elements**
312- Add social proof next to signup form
313- Test trust badges near form (security, compliance)
314- Add "No credit card required" messaging
315- Include privacy assurance copy
317---

Copy & Messaging Experiments

Headlines & CTAs

  • Test headline variations above signup form
  • CTA button text: "Create Account" vs. "Start Free Trial" vs. "Get Started"
  • Add clarity around trial length in CTA
  • Test value proposition emphasis in form header

Microcopy

  • Field labels: minimal vs. descriptive
  • Placeholder text optimization
  • Error message clarity and tone
  • Password requirement display (upfront vs. on error)

Trust Elements

  • Add social proof next to signup form
  • Test trust badges near form (security, compliance)
  • Add "No credit card required" messaging
  • Include privacy assurance copy
Raw lines 297 to 318
319### Trial & Commitment Experiments
321**Free Trial Variations**
322- Credit card required vs. not required for trial
323- Test trial length impact (7 vs. 14 vs. 30 days)
324- Freemium vs. free trial model
325- Trial with limited features vs. full access
327**Friction Points**
328- Email verification required vs. delayed vs. removed
329- Test CAPTCHA impact on completion
330- Terms acceptance checkbox vs. implicit acceptance
331- Phone verification for high-value accounts
333---

Trial & Commitment Experiments

Free Trial Variations

  • Credit card required vs. not required for trial
  • Test trial length impact (7 vs. 14 vs. 30 days)
  • Freemium vs. free trial model
  • Trial with limited features vs. full access

Friction Points

  • Email verification required vs. delayed vs. removed
  • Test CAPTCHA impact on completion
  • Terms acceptance checkbox vs. implicit acceptance
  • Phone verification for high-value accounts
Raw lines 319 to 334
335### Post-Submit Experiments
337- Clear next steps messaging after signup
338- Instant product access vs. email confirmation first
339- Personalized welcome message based on signup data
340- Auto-login after signup vs. require login
342---

Post-Submit Experiments

  • Clear next steps messaging after signup
  • Instant product access vs. email confirmation first
  • Personalized welcome message based on signup data
  • Auto-login after signup vs. require login
Raw lines 335 to 343
344## Task-Specific Questions
3461. What's your current signup completion rate?
3472. Do you have field-level analytics on drop-off?
3483. What data is absolutely required before they can use the product?
3494. Are there compliance or verification requirements?
3505. What happens immediately after signup?
352---

Task-Specific Questions

  1. What's your current signup completion rate?
  2. Do you have field-level analytics on drop-off?
  3. What data is absolutely required before they can use the product?
  4. Are there compliance or verification requirements?
  5. What happens immediately after signup?
Raw lines 344 to 353
354## Enrichment and Sales-Assisted Routing
356If a signup needs enriched company data for a sales-assist handoff, use the [revops inbound-routing playbook](https://github.com/coreyhaines31/marketingskills/blob/main/skills/revops/references/inbound-routing.md). Keep account creation separate from enrichment availability; a timeout or ambiguous company match must not become an implicit signup rejection.

Enrichment and Sales-Assisted Routing

If a signup needs enriched company data for a sales-assist handoff, use the revops inbound-routing playbook. Keep account creation separate from enrichment availability; a timeout or ambiguous company match must not become an implicit signup rejection.

Raw lines 354 to 357
Names a skill revops :356
358## Related Skills
360- **onboarding**: For optimizing what happens after signup
361- **cro**: For non-signup forms (lead capture, contact)
362- **cro**: For the landing page leading to signup
363- **ab-testing**: For testing signup flow changes

Related Skills

  • onboarding: For optimizing what happens after signup
  • cro: For non-signup forms (lead capture, contact)
  • cro: For the landing page leading to signup
  • ab-testing: For testing signup flow changes
Raw lines 358 to 363
Names a skill cro :361
Names a skill ab-testing :363

From coreyhaines31/marketingskills at 88c79f6, 2026-10-30. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.