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
SkillScore87Maintained
Automatic
◆Marketing & Content pack
Last verified 8/21/2026
What it changes
Passed 20 of 23 test cases with the skill, and 19 of 23 without it.
Without skill83%
With skill87%
Checks it passed that the model alone missed
Recommends using placeholder text solely for formatting examples.
Recommends making name entry optional during initial registration.
2 fixed18 passed either way2 still failing1 broke
Pass-rate lift
+4 pp
Tokens
+80%
Agent turns
0%
Response time
+4%
Model gemini-3.6-flashMeasured 8/21/2026v120 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 2
Prompt
We are setting up a B2C mobile app registration screen. Should we split user names into separate mandatory 'First Name' and 'Last Name' fields, and should name collection be mandatory before letting users explore?
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends using a single Full Name field instead of separate First Name and Last Name fields.
Passed
Passed
Recommends making name entry optional during initial registration.
Missed
Passed
case-07 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md290 linessingle file
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)
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.