onboarding-cro
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-flow-cro. For ongoing email sequences, see email-sequence.
What this skill does
# 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-context.md` exists (or `.claude/product-marketing-context.md` 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 onboarding (24h, 72h) - Activation achieved (celebration + next step) - Feature discovery (days 3, 7, 14) **Email should:** - Reinforce in-app actions, not duplicate them - Drive back to product with specific CTA - Be personalized based on actions taken --- ## Handling Stalled Users ### Detection Define "stalled" criteria (X days inactive, incomplete setup) ### Re-engagement Tactics 1. **Email sequence** - Reminder of value, address blockers, offer help 2. **In-app recovery** - Welcome back, pick up where left off 3. **Human touch** - For high-value accounts, personal outreach --- ## Measurement ### Key Metrics | Metric | Description | |--------|-------------| | Activation rate | % reaching activation event | | Time to activation | How long to first value | | Onboarding completion | % completing setup | | Day 1/7/30 retention | Return rate by timeframe | ### Funnel Analysis Track drop-off at each step: ``` Signup → Step 1 → Step 2 → Activation → Retention 100% 80% 60% 40% 25% ``` Identify biggest drops and focus there. --- ## Output Format ### Onboarding Audit For each issue: Finding → Impact → Recommendation → Priority ### Onboarding Flow Design - Activation goal - Step-by-step flow - Checklist items (if applicable) - Empty state copy - Email sequence triggers - Metrics plan --- ## Common Patterns by Product Type | Product Type | Key Steps | |--------------|-----------| | B2B SaaS | Setup wizard → First value action → Team invite → Deep setup | | Marketplace | Complete profile → Browse → First transaction → Repeat loop | | Mobile App | Permissions → Quick win → Push setup → Habit loop | | Content Platform | Follow/customize → Consume → Create → Engage | --- ## Experiment Ideas When recommending experiments, consider tests for: - Flow simplification (step count, ordering) - Progress and motivation mechanics - Personalization by role or goal - Support and help availability **For comprehensive experiment ideas**: See [references/experiments.md](references/experiments.md) --- ## Task-Specific Questions 1. What action most correlates with retention? 2. What happens immediately after signup? 3. Where do users currently drop off? 4. What's your activation rate target? 5. Do you have cohort analysis on successful vs. churned users? --- ## Related Skills - **signup-flow-cro**: For optimizing the signup before onboarding - **email-sequence**: For onboarding email series - **paywall-upgrade-cro**: For converting to paid during/after onboarding - **ab-test-setup**: For testing onboarding changes
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".