Onboarding CRO
Unverified●25/40Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add onboardingWho is stuck, and on what
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checkl
The whole source
Frontmatter — 3 properties
| name | onboarding |
|---|---|
| description | When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails. |
| metadata | version: 2.0.1 |
| 1 | --- |
| 2 | name: onboarding |
| 3 | description: When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.B1 — Line is 637 characters — unreadable by eye |
| 4 | metadata: |
| 5 | version: 2.0.1 |
| 6 | ---A5 — No allowed-tools declared — no way to tell what this skill may touch |
| 7 | |
| 8 | # Onboarding CRO |
| 9 | |
| 10 | 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. |
| 11 | |
| 12 | ## Initial Assessment |
| 13 | |
| 14 | **Check for product marketing context first:** |
| 15 | 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. |
| 16 | |
| 17 | Before providing recommendations, understand: |
| 18 | |
| 19 | 1. **Product Context** - What type of product? B2B or B2C? Core value proposition? |
| 20 | 2. **Activation Definition** - What's the "aha moment"? What action indicates a user "gets it"? |
| 21 | 3. **Current State** - What happens after signup? Where do users drop off? |
| 22 | |
| 23 | --- |
| 24 | |
| 25 | ## Core Principles |
| 26 | |
| 27 | ### 1. Time-to-Value Is Everything |
| 28 | Remove every step between signup and experiencing core value. Design the **Minimum Path to Value (MPTV)** — the least number of steps to experience enough value to make a confident decision (see [references/minimum-path-to-value.md](references/minimum-path-to-value.md)). |
| 29 | |
| 30 | ### 2. One Goal Per Session |
| 31 | Focus first session on one successful outcome. Save advanced features for later. |
| 32 | |
| 33 | ### 3. Do, Don't Show |
| 34 | Interactive > Tutorial. Doing the thing > Learning about the thing. |
| 35 | |
| 36 | ### 4. Progress Creates Motivation |
| 37 | Show advancement. Celebrate completions. Make the path visible. (See onboarding psychology below for the mechanisms.) |
| 38 | |
| 39 | --- |
| 40 | |
| 41 | ## Onboarding Psychology |
| 42 | |
| 43 | The principles that make progress mechanics, checklists, and prompts actually work: |
| 44 | |
| 45 | - **Endowed Progress Effect** — people finish faster when progress is already started for them. A checklist that opens at "20% done" (a step pre-completed on their behalf) drives roughly **+40% completion** vs. starting at 0%. Give users a head start, don't make them start from nothing. |
| 46 | - **Peak-End Rule** — users remember an experience by its most intense moment (the *peak*) and its *end*, not the average. Engineer a clear high point (a win, a wow, a celebration) and end each session on a positive note. |
| 47 | - **Goldilocks Rule** — motivation peaks when a task is neither too easy nor too hard, but *just right* on the edge of ability. Tune early steps so they're achievable but not trivial. |
| 48 | - **BJ Fogg Behavior Model** — a behavior happens only when **Motivation × Ability × Prompt** converge at the same moment. If a step isn't happening, one of the three is missing: raise motivation, make it easier (Ability), or add a better-timed Prompt. |
| 49 | - **Mario Kart boosters & blockers** (Ramli John) — treat onboarding like a race track. Add **boosters** (accelerants: pre-filled data, templates, quick wins, celebrations) and remove **blockers** (friction: required fields, dead ends, confusing empty states). Speed users toward value and clear obstacles from the lane. |
| 50 | |
| 51 | ## Onboarding Toolkit (10 Components) |
| 52 | |
| 53 | The components you assemble an onboarding experience from. Use the fewest that reach value: |
| 54 | |
| 55 | | Component | Purpose | |
| 56 | |-----------|---------| |
| 57 | | Welcome forms | Capture role/goal to personalize the path (keep short — Hick's Law) | |
| 58 | | Initial screens | First-run screens that orient and point to one clear action | |
| 59 | | Drip emails | Multi-touch nurture — **one concept per email**, don't overload | |
| 60 | | Skippable tutorials | Optional guidance users can bypass — never trap them | |
| 61 | | Videos | Show complex workflows visually | |
| 62 | | Docs / help center | Self-serve reference for when users get stuck | |
| 63 | | Onboarding calls | Human touch for complex or high-value accounts | |
| 64 | | Data inputs | Getting the user's real data in so value feels "real" | |
| 65 | | Checklists | Ordered, value-first steps with visible progress (see below) | |
| 66 | | Empty states | Guided first-action opportunities, not dead ends (see below) | |
| 67 | |
| 68 | --- |
| 69 | |
| 70 | ## Defining Activation |
| 71 | |
| 72 | **Judge activation by lead→customer conversion + 90-day retention, not lead volume.** More signups mean nothing if they don't convert and stick. |
| 73 | |
| 74 | Choose an **activation model** (freemium, free trial, paid trial, money-back, consultation) before designing the flow — the model shapes the whole onboarding path. See [references/activation-models.md](references/activation-models.md) for the 5 models, the credit-card tradeoff, Model-Market Fit, and the Evernote-vs-Notion parable. |
| 75 | |
| 76 | ### Find Your Aha Moment |
| 77 | |
| 78 | The action that correlates most strongly with retention: |
| 79 | - What do retained users do that churned users don't? |
| 80 | - What's the earliest indicator of future engagement? |
| 81 | |
| 82 | **Examples by product type:** |
| 83 | - Project management: Create first project + add team member |
| 84 | - Analytics: Install tracking + see first report |
| 85 | - Design tool: Create first design + export/share |
| 86 | - Marketplace: Complete first transaction |
| 87 | |
| 88 | ### Activation Metrics |
| 89 | - % of signups who reach activation |
| 90 | - Time to activation |
| 91 | - Steps to activation |
| 92 | - Activation by cohort/source |
| 93 | |
| 94 | --- |
| 95 | |
| 96 | ## Onboarding Flow Design |
| 97 | |
| 98 | ### Immediate Post-Signup (First 30 Seconds) |
| 99 | |
| 100 | | Approach | Best For | Risk | |
| 101 | |----------|----------|------| |
| 102 | | Product-first | Simple products, B2C, mobile | Blank slate overwhelm | |
| 103 | | Guided setup | Products needing personalization | Adds friction before value | |
| 104 | | Value-first | Products with demo data | May not feel "real" | |
| 105 | |
| 106 | **Whatever you choose:** |
| 107 | - Clear single next action |
| 108 | - No dead ends |
| 109 | - Progress indication if multi-step |
| 110 | |
| 111 | ### Onboarding Checklist Pattern |
| 112 | |
| 113 | **When to use:** |
| 114 | - Multiple setup steps required |
| 115 | - Product has several features to discover |
| 116 | - Self-serve B2B products |
| 117 | |
| 118 | **Best practices:** |
| 119 | - 3-7 items (not overwhelming) |
| 120 | - Order by value (most impactful first) |
| 121 | - Start with quick wins |
| 122 | - Progress bar/completion % |
| 123 | - Celebration on completion |
| 124 | - Dismiss option (don't trap users) |
| 125 | |
| 126 | ### Empty States |
| 127 | |
| 128 | Empty states are onboarding opportunities, not dead ends. |
| 129 | |
| 130 | **Good empty state:** |
| 131 | - Explains what this area is for |
| 132 | - Shows what it looks like with data |
| 133 | - Clear primary action to add first item |
| 134 | - Optional: Pre-populate with example data |
| 135 | |
| 136 | ### Tooltips and Guided Tours |
| 137 | |
| 138 | **When to use:** Complex UI, features that aren't self-evident, power features users might miss |
| 139 | |
| 140 | **Best practices:** |
| 141 | - Max 3-5 steps per tour |
| 142 | - Dismissable at any time |
| 143 | - Don't repeat for returning users |
| 144 | |
| 145 | --- |
| 146 | |
| 147 | ## Multi-Channel Onboarding |
| 148 | |
| 149 | ### Email + In-App Coordination |
| 150 | |
| 151 | **Trigger-based emails:** |
| 152 | - Welcome email (immediate) |
| 153 | - Incomplete onboarding (24h, 72h) |
| 154 | - Activation achieved (celebration + next step) |
| 155 | - Feature discovery (days 3, 7, 14) |
| 156 | |
| 157 | **Email should:** |
| 158 | - Reinforce in-app actions, not duplicate them |
| 159 | - Drive back to product with specific CTA |
| 160 | - Be personalized based on actions taken |
| 161 | |
| 162 | --- |
| 163 | |
| 164 | ## Handling Stalled Users |
| 165 | |
| 166 | ### Detection |
| 167 | Define "stalled" criteria (X days inactive, incomplete setup) |
| 168 | |
| 169 | ### Re-engagement Tactics |
| 170 | |
| 171 | 1. **Email sequence** - Reminder of value, address blockers, offer help |
| 172 | 2. **In-app recovery** - Welcome back, pick up where left off |
| 173 | 3. **Human touch** - For high-value accounts, personal outreach |
| 174 | |
| 175 | --- |
| 176 | |
| 177 | ## Measurement |
| 178 | |
| 179 | ### Key Metrics |
| 180 | |
| 181 | | Metric | Description | |
| 182 | |--------|-------------| |
| 183 | | Activation rate | % reaching activation event | |
| 184 | | Time to activation | How long to first value | |
| 185 | | Onboarding completion | % completing setup | |
| 186 | | Day 1/7/30 retention | Return rate by timeframe | |
| 187 | |
| 188 | ### Funnel Analysis |
| 189 | |
| 190 | Track drop-off at each step: |
| 191 | ``` |
| 192 | Signup → Step 1 → Step 2 → Activation → Retention |
| 193 | 100% 80% 60% 40% 25% |
| 194 | ``` |
| 195 | |
| 196 | Identify biggest drops and focus there. |
| 197 | |
| 198 | --- |
| 199 | |
| 200 | ## Output Format |
| 201 | |
| 202 | ### Onboarding Audit |
| 203 | For each issue: Finding → Impact → Recommendation → Priority |
| 204 | |
| 205 | ### Onboarding Flow Design |
| 206 | - Activation goal |
| 207 | - Step-by-step flow |
| 208 | - Checklist items (if applicable) |
| 209 | - Empty state copy |
| 210 | - Email sequence triggers |
| 211 | - Metrics plan |
| 212 | |
| 213 | --- |
| 214 | |
| 215 | ## Common Patterns by Product Type |
| 216 | |
| 217 | | Product Type | Key Steps | |
| 218 | |--------------|-----------| |
| 219 | | B2B SaaS | Setup wizard → First value action → Team invite → Deep setup | |
| 220 | | Marketplace | Complete profile → Browse → First transaction → Repeat loop | |
| 221 | | Mobile App | Permissions → Quick win → Push setup → Habit loop | |
| 222 | | Content Platform | Follow/customize → Consume → Create → Engage | |
| 223 | |
| 224 | --- |
| 225 | |
| 226 | ## Experiment Ideas |
| 227 | |
| 228 | When recommending experiments, consider tests for: |
| 229 | - Flow simplification (step count, ordering) |
| 230 | - Progress and motivation mechanics |
| 231 | - Personalization by role or goal |
| 232 | - Support and help availability |
| 233 | |
| 234 | **For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md) |
| 235 | |
| 236 | --- |
| 237 | |
| 238 | ## References |
| 239 | |
| 240 | - **[references/minimum-path-to-value.md](references/minimum-path-to-value.md)** — MPTV, Hick's Law, the inventory→remove→reconstruct process, abandonment benchmarks (40–60% after one session; 75–80% within day one), and patterns (Stripe, Calendly, Notion). |
| 241 | - **[references/activation-models.md](references/activation-models.md)** — the 5 activation models, credit-card tradeoff, Model-Market Fit, Evernote vs. Notion. |
| 242 | - **[references/experiments.md](references/experiments.md)** — comprehensive A/B test and experiment ideas. |
| 243 | |
| 244 | --- |
| 245 | |
| 246 | ## Task-Specific Questions |
| 247 | |
| 248 | 1. What action most correlates with retention? |
| 249 | 2. What happens immediately after signup? |
| 250 | 3. Where do users currently drop off? |
| 251 | 4. What's your activation rate target? |
| 252 | 5. Do you have cohort analysis on successful vs. churned users? |
| 253 | |
| 254 | --- |
| 255 | |
| 256 | ## Related Skills |
| 257 | |
| 258 | - **signup**: For optimizing the signup before onboarding |
| 259 | - **emails**: For onboarding email series |
| 260 | - **paywalls**: For converting to paid during/after onboarding |
| 261 | - **ab-testing**: For testing onboarding changes |
| 262 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Subagent Driven DevelopmentUse when executing implementation plans with independent tasks in the current session◐◐◐◐◐●36/40Python Code Style & DocumentationPython code style, linting, formatting, naming conventions, and documentation standards. Use when writing new code, reviewing style, configuring linters, writing docstrings, or establishing project standards.◐····●35/40Competitor Price Analysis 💲Competitor pricing strategy analysis and market positioning. Price mapping, pricing gaps identification, elasticity signals evaluation, and strategic pricing optimization. Use when the user asks about competitor pricing, price analysis, pricing strategy, or co◐····●34/40Competitor Price Tracker 📊Set up competitor price tracking and monitoring workflows. Track price changes, detect promotions, analyze pricing patterns, and get alerts for competitive price movements.◐····●34/40