signup-flow-cro

Name: signup-flow-cro
Author: davidpc007

140stars1.3kforks

How to install signup-flow-cro?

davidpc007/openclaw-marketing-skills/signup-flow-cro

$npx -y skills add davidpc007/openclaw-marketing-skills --skill signup-flow-cro

Installs into the current project.

Summary

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," "pe

Files · 1

View on GitHub

SKILL.md

1	# Signup Flow CRO
2
3	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.
4
5	## Initial Assessment
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Before providing recommendations, understand:
11
12	1. Flow Type
13	- Free trial signup
14	- Freemium account creation
15	- Paid account creation
16	- Waitlist/early access signup
17	- B2B vs B2C
18
19	2. Current State
20	- How many steps/screens?
21	- What fields are required?
22	- What's the current completion rate?
23	- Where do users drop off?
24
25	3. Business Constraints
26	- What data is genuinely needed at signup?
27	- Are there compliance requirements?
28	- What happens immediately after signup?
29
30	---
31
32	## Core Principles
33
34	### 1. Minimize Required Fields
35	Every field reduces conversion. For each field, ask:
36	- Do we absolutely need this before they can use the product?
37	- Can we collect this later through progressive profiling?
38	- Can we infer this from other data?
39
40	Typical field priority:
41	- Essential: Email (or phone), Password
42	- Often needed: Name
43	- Usually deferrable: Company, Role, Team size, Phone, Address
44
45	### 2. Show Value Before Asking for Commitment
46	- What can you show/give before requiring signup?
47	- Can they experience the product before creating an account?
48	- Reverse the order: value first, signup second
49
50	### 3. Reduce Perceived Effort
51	- Show progress if multi-step
52	- Group related fields
53	- Use smart defaults
54	- Pre-fill when possible
55
56	### 4. Remove Uncertainty
57	- Clear expectations ("Takes 30 seconds")
58	- Show what happens after signup
59	- No surprises (hidden requirements, unexpected steps)
60
61	---
62
63	## Field-by-Field Optimization
64
65	### Email Field
66	- Single field (no email confirmation field)
67	- Inline validation for format
68	- Check for common typos (gmial.com → gmail.com)
69	- Clear error messages
70
71	### Password Field
72	- Show password toggle (eye icon)
73	- Show requirements upfront, not after failure
74	- Consider passphrase hints for strength
75	- Update requirement indicators in real-time
76
77	Better password UX:
78	- Allow paste (don't disable)
79	- Show strength meter instead of rigid rules
80	- Consider passwordless options
81
82	### Name Field
83	- Single "Full name" field vs. First/Last split (test this)
84	- Only require if immediately used (personalization)
85	- Consider making optional
86
87	### Social Auth Options
88	- Place prominently (often higher conversion than email)
89	- Show most relevant options for your audience
90	- B2C: Google, Apple, Facebook
91	- B2B: Google, Microsoft, SSO
92	- Clear visual separation from email signup
93	- Consider "Sign up with Google" as primary
94
95	### Phone Number
96	- Defer unless essential (SMS verification, calling leads)
97	- If required, explain why
98	- Use proper input type with country code handling
99	- Format as they type
100
101	### Company/Organization
102	- Defer if possible
103	- Auto-suggest as they type
104	- Infer from email domain when possible
105
106	### Use Case / Role Questions
107	- Defer to onboarding if possible
108	- If needed at signup, keep to one question
109	- Use progressive disclosure (don't show all options at once)
110
111	---
112
113	## Single-Step vs. Multi-Step
114
115	### Single-Step Works When:
116	- 3 or fewer fields
117	- Simple B2C products
118	- High-intent visitors (from ads, waitlist)
119
120	### Multi-Step Works When:
121	- More than 3-4 fields needed
122	- Complex B2B products needing segmentation
123	- You need to collect different types of info
124
125	### Multi-Step Best Practices
126	- Show progress indicator
127	- Lead with easy questions (name, email)
128	- Put harder questions later (after psychological commitment)
129	- Each step should feel completable in seconds
130	- Allow back navigation
131	- Save progress (don't lose data on refresh)
132
133	Progressive commitment pattern:
134	1. Email only (lowest barrier)
135	2. Password + name
136	3. Customization questions (optional)
137
138	---
139
140	## Trust and Friction Reduction
141
142	### At the Form Level
143	- "No credit card required" (if true)
144	- "Free forever" or "14-day free trial"
145	- Privacy note: "We'll never share your email"
146	- Security badges if relevant
147	- Testimonial near signup form
148
149	### Error Handling
150	- Inline validati

People who liked this also viewed

6 picks

Type

signup-flow-cro

140stars1.3kforks

View on GitHub

How to install signup-flow-cro?

davidpc007/openclaw-marketing-skills/signup-flow-cro

$npx -y skills add davidpc007/openclaw-marketing-skills --skill signup-flow-cro

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Signup Flow CRO
2
3	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.
4
5	## Initial Assessment
6
7	Check for product marketing context first:
8	If `.agents/product-marketing-context.md` exists (or `.agents/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
9
10	Before providing recommendations, understand:
11
12	1. Flow Type
13	- Free trial signup
14	- Freemium account creation
15	- Paid account creation
16	- Waitlist/early access signup
17	- B2B vs B2C
18
19	2. Current State
20	- How many steps/screens?
21	- What fields are required?
22	- What's the current completion rate?
23	- Where do users drop off?
24
25	3. Business Constraints
26	- What data is genuinely needed at signup?
27	- Are there compliance requirements?
28	- What happens immediately after signup?
29
30	---
31
32	## Core Principles
33
34	### 1. Minimize Required Fields
35	Every field reduces conversion. For each field, ask:
36	- Do we absolutely need this before they can use the product?
37	- Can we collect this later through progressive profiling?
38	- Can we infer this from other data?
39
40	Typical field priority:
41	- Essential: Email (or phone), Password
42	- Often needed: Name
43	- Usually deferrable: Company, Role, Team size, Phone, Address
44
45	### 2. Show Value Before Asking for Commitment
46	- What can you show/give before requiring signup?
47	- Can they experience the product before creating an account?
48	- Reverse the order: value first, signup second
49
50	### 3. Reduce Perceived Effort
51	- Show progress if multi-step
52	- Group related fields
53	- Use smart defaults
54	- Pre-fill when possible
55
56	### 4. Remove Uncertainty
57	- Clear expectations ("Takes 30 seconds")
58	- Show what happens after signup
59	- No surprises (hidden requirements, unexpected steps)
60
61	---
62
63	## Field-by-Field Optimization
64
65	### Email Field
66	- Single field (no email confirmation field)
67	- Inline validation for format
68	- Check for common typos (gmial.com → gmail.com)
69	- Clear error messages
70
71	### Password Field
72	- Show password toggle (eye icon)
73	- Show requirements upfront, not after failure
74	- Consider passphrase hints for strength
75	- Update requirement indicators in real-time
76
77	Better password UX:
78	- Allow paste (don't disable)
79	- Show strength meter instead of rigid rules
80	- Consider passwordless options
81
82	### Name Field
83	- Single "Full name" field vs. First/Last split (test this)
84	- Only require if immediately used (personalization)
85	- Consider making optional
86
87	### Social Auth Options
88	- Place prominently (often higher conversion than email)
89	- Show most relevant options for your audience
90	- B2C: Google, Apple, Facebook
91	- B2B: Google, Microsoft, SSO
92	- Clear visual separation from email signup
93	- Consider "Sign up with Google" as primary
94
95	### Phone Number
96	- Defer unless essential (SMS verification, calling leads)
97	- If required, explain why
98	- Use proper input type with country code handling
99	- Format as they type
100
101	### Company/Organization
102	- Defer if possible
103	- Auto-suggest as they type
104	- Infer from email domain when possible
105
106	### Use Case / Role Questions
107	- Defer to onboarding if possible
108	- If needed at signup, keep to one question
109	- Use progressive disclosure (don't show all options at once)
110
111	---
112
113	## Single-Step vs. Multi-Step
114
115	### Single-Step Works When:
116	- 3 or fewer fields
117	- Simple B2C products
118	- High-intent visitors (from ads, waitlist)
119
120	### Multi-Step Works When:
121	- More than 3-4 fields needed
122	- Complex B2B products needing segmentation
123	- You need to collect different types of info
124
125	### Multi-Step Best Practices
126	- Show progress indicator
127	- Lead with easy questions (name, email)
128	- Put harder questions later (after psychological commitment)
129	- Each step should feel completable in seconds
130	- Allow back navigation
131	- Save progress (don't lose data on refresh)
132
133	Progressive commitment pattern:
134	1. Email only (lowest barrier)
135	2. Password + name
136	3. Customization questions (optional)
137
138	---
139
140	## Trust and Friction Reduction
141
142	### At the Form Level
143	- "No credit card required" (if true)
144	- "Free forever" or "14-day free trial"
145	- Privacy note: "We'll never share your email"
146	- Security badges if relevant
147	- Testimonial near signup form
148
149	### Error Handling
150	- Inline validati

People who liked this also viewed

6 picks

Type