When the user wants to optimize signup, registration, account creation, or trial activation flows.

MITAuto-check passedMarketing & SEO

Install Signup

skills CLI
$ npx skills add coreyhaines31/marketingskills --skill signup -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install coreyhaines31/marketingskills signup --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/coreyhaines31/marketingskills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/signup .claude/skills/signup && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
signup
GitHub stars
54k
Used in
1 other repo
Token cost
~2.6k tokens
SKILL.md length
1,265 words
Files
2
Skills in repo
21
Repo updated
First seen
Licence
MIT

At a glance

When the user wants to optimize signup, registration, account creation, or trial activation flows.

  • Works in 4 steps: Minimize Required Fields → Show Value Before Asking for Commitment → Reduce Perceived Effort → …
  • Wants to optimize signup
  • SKILL.md covers Initial Assessment, Core Principles, Field-by-Field Optimization and Single-Step vs. Multi-Step, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Signup is an agent skill from coreyhaines31/marketingskills. 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…

Its SKILL.md is about 2.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `evals/evals.json`).

It sits in Marketing & SEO, covering Conversion rate optimization and Lead generation. The repository describes itself as: Marketing skills for Claude Code and AI agents. CRO, copywriting, SEO, analytics, and growth engineering. The licence is MIT.

When your agent uses it

  • Wants to optimize signup
  • Account creation
  • Trial activation flows
  • The user mentions signup conversions

Example prompts

  • “signup conversions,”
  • “registration friction,”
  • “signup form optimization,”
  • “/signup”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Minimize Required Fields
  2. Show Value Before Asking for Commitment
  3. Reduce Perceived Effort
  4. Remove Uncertainty

What it can do on your machine

Read from SKILL.md and the folder at commit b9ba399. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Signup loads about 2.6k tokens when it runs. Until then it costs about 158 tokens; SKILL.md has 1,265 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~158
When it runs · the whole SKILL.md, loaded when a task matches
~2.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from coreyhaines31/marketingskills at commit b9ba399, republished under its MIT licence (© coreyhaines31). 1,265 words, ~2,592 tokens.

Download SKILL.mdSave it as .claude/skills/signup/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
signup
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.
metadata.version
2.0.0

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 question
  • Use progressive disclosure (don't show all options at once)

Single-Step vs. Multi-Step

Single-Step Works When:
  • 3 or fewer fields
  • Simple B2C products
  • High-intent visitors (from ads, waitlist)
Multi-Step Works When:
  • More than 3-4 fields needed
  • Complex B2B products needing segmentation
  • You need to collect different types of info
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)

Trust and Friction Reduction

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
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
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

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

Post-Submit Experience

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
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

Measurement

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
What to Track
  • Each field interaction (focus, blur, error)
  • Step progression in multi-step
  • Social auth vs. email signup ratio
  • Time between steps

Show full SKILL.md (499 more words)Show less

Output Format

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

Organized by:

  1. Quick wins (same-day fixes)
  2. High-impact changes (week-level effort)
  3. Test hypotheses (things to A/B test)
Form Redesign (if requested)
  • Recommended field set with rationale
  • Field order
  • Copy for labels, placeholders, buttons, errors
  • Visual layout suggestions

Common Signup Flow Patterns

B2B SaaS Trial
  1. Email + Password (or Google auth)
  2. Name + Company (optional: role)
  3. → Onboarding flow
B2C App
  1. Google/Apple auth OR Email
  2. → Product experience
  3. Profile completion later
Waitlist/Early Access
  1. Email only
  2. Optional: Role/use case question
  3. → Waitlist confirmation
E-commerce Account
  1. Guest checkout as default
  2. Account creation optional post-purchase
  3. OR Social auth with single click

Experiment Ideas

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

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

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

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

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?

  • 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

© coreyhaines31, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in skills/signup of coreyhaines31/marketingskills.

  • SKILL.md
  • evals/evals.json

Open the folder on GitHubat commit b9ba399

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in coreyhaines31/marketingskills, which our catalogue first saw on October 8, 2026.

Compare with similar skills

Signup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Signup compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Signup this skillcoreyhaines31/marketingskills54k1 repos~2.6kAutomated safety check: PassMIT
Meta Ads for B2Bivangfalco/ads-skills278—~2.4kAutomated safety check: PassCustom licence
Form Crofreekmurze/dotfiles1k11 repos~2.7kAutomated safety check: PassNone
Crosickn33/agentic-awesome-skills47k1 repos~1.6kAutomated safety check: PassMIT
Form Croaiskillstore/marketplace4304 repos~2kAutomated safety check: PassNone
Conversion Rate Optimizationmanojbajaj95/claude-gtm-plugin105—~1.2kAutomated safety check: PassMIT

Similar skills

  • Meta Ads for B2B

    ivangfalco/ads-skills

    Guides B2B campaigns on Meta (Facebook and Instagram): audience data, campaign structure, creative testing, lead forms and account audits for SaaS lead generation.

    278 GitHub stars~2.4k tokensUpdated 2 mo ago
    Marketing & SEOAuto-check passed
  • Form Cro

    freekmurze/dotfiles

    When the user wants to optimize any form that is NOT signup/registration — including lead capture forms, contact forms, demo request forms, application forms, survey forms, or checkout forms.

    1k GitHub starsUsed in 11 repos~2.7k tokens
    Marketing & SEOAuto-check passed
  • Cro

    sickn33/agentic-awesome-skills

    When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms.

    47k GitHub starsUsed in 1 repo~1.6k tokens
    Marketing & SEOAuto-check passed
  • Form Cro

    aiskillstore/marketplace

    Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.

    430 GitHub starsUsed in 4 repos~2k tokens
    Marketing & SEOAuto-check passed
  • Conversion Rate Optimization

    manojbajaj95/claude-gtm-plugin

    Conversion rate optimization for marketing pages and lead-capture forms.

    105 GitHub stars~1.2k tokensUpdated 20 days ago
    Marketing & SEOAuto-check passed
  • Form Cro

    borghei/Claude-Skills

    Form optimization for lead capture, contact, demo request, application, and checkout forms.

    881 GitHub stars~5.6k tokensUpdated today
    Marketing & SEOAuto-check passed

More from coreyhaines31/marketingskills

All 21 skills in this repo
  • Social

    coreyhaines31/marketingskills

    When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, or Facebook, or wants to do social listening and engagement triage.

    54k GitHub starsUsed in 4 repos~4.5k tokens
    Auto-check passed
  • Ab Testing

    coreyhaines31/marketingskills

    When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program.

    54k GitHub starsUsed in 3 repos~2.8k tokens
    Auto-check passed
  • Referrals

    coreyhaines31/marketingskills

    When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy.

    54k GitHub starsUsed in 2 repos~2.4k tokens
    Auto-check passed
  • Aso

    coreyhaines31/marketingskills

    When the user wants to audit or optimize an App Store or Google Play listing.

    54k GitHub starsUsed in 1 repo~3.9k tokens
    Auto-check passed
  • Emails

    coreyhaines31/marketingskills

    When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.

    54k GitHub starsUsed in 1 repo~2.6k tokens
    Auto-check passed
  • Paywalls

    coreyhaines31/marketingskills

    When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates.

    54k GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed

Categories

Questions about Signup

What does Signup do?

When the user wants to optimize signup, registration, account creation, or trial activation flows. Signup is an agent skill from coreyhaines31/marketingskills. When the user wants to optimize signup, registration, account creation, or trial activation flows.

When should I use Signup?

Signup fits situations like: wants to optimize signup; account creation; trial activation flows; the user mentions signup conversions.

How do I install Signup in Claude Code?

Run `npx skills add coreyhaines31/marketingskills --skill signup -a claude-code`. Or copy the skill folder (skills/signup in coreyhaines31/marketingskills) into .claude/skills/signup in your project. Claude Code loads it when a task matches its description.

How do I install Signup in Codex?

Run `npx skills add coreyhaines31/marketingskills --skill signup -a codex`. Or copy the skill folder (skills/signup in coreyhaines31/marketingskills) into .agents/skills/signup in your project. Codex loads it when a task matches its description.

Can I use Signup in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add coreyhaines31/marketingskills --skill signup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/signup, .gemini/skills/signup, .github/skills/signup and .opencode/skills/signup in your project.

What does Signup need to run?

SKILL.md names no scripts, command-line tools or credentials: Signup is instructions for the agent only.

Does Signup access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Signup safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Signup use?

Signup is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Signup use?

About 2.6k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Signup?

Skills that share tags, products or a category with Signup: Meta Ads for B2B (ivangfalco/ads-skills, 278 stars), Form Cro (freekmurze/dotfiles, 1k stars), Cro (sickn33/agentic-awesome-skills, 47k stars) and Form Cro (aiskillstore/marketplace, 430 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Signup?

coreyhaines31 (a GitHub user) maintains it in coreyhaines31/marketingskills, which has 53,618 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: coreyhaines31/marketingskills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.