Onboarding
Design post-signup flows, activation checkpoints, and empty states so new users reach an aha moment faster.
Overview
Onboarding is an agent skill most often used in Grow (also Validate scope) that optimizes post-signup activation, first-run UX, and time-to-value for solo-built products.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill onboardingWhat is this skill?
- Defines activation and aha moment before recommending flow changes
- Optimizes first-run experience, checklists, and empty states for time-to-value
- Loads product-marketing context from `.agents/product-marketing.md` when present
- Explicitly defers signup CRO to signup and drip sequences to emails skills
Adoption & trust: 14.8k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Users complete signup but never reach the action that proves they understand your product’s value.
Who is it for?
SaaS and app founders measuring activation who can define a concrete first-success action.
Skip if: Checkout-only ecommerce with no recurring product surface, or signup-page-only CRO without in-app first-run changes.
When should I use this skill?
User wants to optimize post-signup onboarding, activation, first-run experience, empty states, or time-to-value.
What do I get? / Deliverables
You get activation-focused onboarding recommendations aligned to your aha moment; use signup or emails skills for registration or nurture gaps.
- Onboarding flow recommendations and checklist ideas
- Empty-state and first-session UX guidance
- Activation metric framing tied to product type
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Onboarding CRO sits on Grow/lifecycle because it optimizes retention after signup, though it informs Validate prototypes. Lifecycle covers activation rate, first-session experience, and habits—not top-of-funnel signup forms alone.
Where it fits
Redesign a post-signup checklist when completion rate drops below 30%.
Shape a minimal first-run for a prototype before committing to full build.
Align onboarding steps with activation events you already track in analytics.
Translate activation definition into in-app milestones for the MVP backlog.
How it compares
Lifecycle onboarding CRO skill—not the signup registration skill or a generic email-copy generator.
Common Questions / FAQ
Who is onboarding for?
Solo builders and small teams with a live signup funnel who need structured advice on activation, empty states, and first-session experience.
When should I use onboarding?
Use it in Grow when fixing activation and retention, in Validate when scoping a prototype’s first-run, and when you mention onboarding flow, aha moment, or low activation rate.
Is onboarding safe to install?
Review Prism Security Audits for the package; the skill advises on UX copy and flows—apply recommendations through your normal product and analytics review.
SKILL.md
READMESKILL.md - Onboarding
# Onboarding CRO You are an expert in user onboarding and activation. Your goal is to help users reach their "aha moment" as quickly as possible and establish habits that lead to long-term retention. ## 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. **Product Context** - What type of product? B2B or B2C? Core value proposition? 2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"? 3. **Current State** - What happens after signup? Where do users drop off? --- ## Core Principles ### 1. Time-to-Value Is Everything Remove every step between signup and experiencing core value. ### 2. One Goal Per Session Focus first session on one successful outcome. Save advanced features for later. ### 3. Do, Don't Show Interactive > Tutorial. Doing the thing > Learning about the thing. ### 4. Progress Creates Motivation Show advancement. Celebrate completions. Make the path visible. --- ## Defining Activation ### Find Your Aha Moment The action that correlates most strongly with retention: - What do retained users do that churned users don't? - What's the earliest indicator of future engagement? **Examples by product type:** - Project management: Create first project + add team member - Analytics: Install tracking + see first report - Design tool: Create first design + export/share - Marketplace: Complete first transaction ### Activation Metrics - % of signups who reach activation - Time to activation - Steps to activation - Activation by cohort/source --- ## Onboarding Flow Design ### Immediate Post-Signup (First 30 Seconds) | Approach | Best For | Risk | |----------|----------|------| | Product-first | Simple products, B2C, mobile | Blank slate overwhelm | | Guided setup | Products needing personalization | Adds friction before value | | Value-first | Products with demo data | May not feel "real" | **Whatever you choose:** - Clear single next action - No dead ends - Progress indication if multi-step ### Onboarding Checklist Pattern **When to use:** - Multiple setup steps required - Product has several features to discover - Self-serve B2B products **Best practices:** - 3-7 items (not overwhelming) - Order by value (most impactful first) - Start with quick wins - Progress bar/completion % - Celebration on completion - Dismiss option (don't trap users) ### Empty States Empty states are onboarding opportunities, not dead ends. **Good empty state:** - Explains what this area is for - Shows what it looks like with data - Clear primary action to add first item - Optional: Pre-populate with example data ### Tooltips and Guided Tours **When to use:** Complex UI, features that aren't self-evident, power features users might miss **Best practices:** - Max 3-5 steps per tour - Dismissable at any time - Don't repeat for returning users --- ## Multi-Channel Onboarding ### Email + In-App Coordination **Trigger-based emails:** - Welcome email (immediate) - Incomplete o