Skill detail
onboarding
Optimizes post-signup onboarding, activation, first-run experience, and time-to-value, including empty states and onboarding checklists. Relevant to app onboarding flow design.
Inspect before use
Read the source instructions and check the requirements before you install this skill.
SKILL.md
The saved excerpt is a snapshot from when this skill was listed. The external source remains the complete and most current version.
--- 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 --- # 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. 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)). ### 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. (See onboarding psychology below for the mechanisms.) --- ## Onboarding Psychology The principles that make progress mechanics, checklists, and prompts actually work: - **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. - **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. - **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. - **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. - **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. ## Onboarding Toolkit (10 Components) The components you assemble an onboarding experience from. Use the fewest that reach value: | Component | Purpose | |-----------|---------| | Welcome forms | Capture role/goal to personalize the path (keep short — Hick's Law) | | Initial screens | First-run screens that orient and point to one clear action | | Drip emails | Multi-touch nurtureRead the full source on GitHub (opens external page)