marketing-skill/skills/onboarding-cro/SKILL.md
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," or "new user experience." For signup/registration optimization, see signup-flow-cro. For ongoing email sequences, see email-sequence.
npx skillsauth add alirezarezvani/claude-skills onboarding-croInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Check for product marketing context first:
If .claude/product-marketing-context.md exists, 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:
Remove every step between signup and experiencing core value.
Focus first session on one successful outcome. Save advanced features for later.
Interactive > Tutorial. Doing the thing > Learning about the thing.
Show advancement. Celebrate completions. Make the path visible.
The action that correlates most strongly with retention:
Examples by product type:
| 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:
When to use:
Best practices:
Empty states are onboarding opportunities, not dead ends.
Good empty state:
When to use: Complex UI, features that aren't self-evident, power features users might miss
Best practices:
Trigger-based emails:
Email should:
Define "stalled" criteria (X days inactive, incomplete setup)
| 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 |
Track drop-off at each step:
Signup → Step 1 → Step 2 → Activation → Retention
100% 80% 60% 40% 25%
Run the bundled analyzer on your step counts instead of eyeballing:
python3 scripts/activation_funnel_analyzer.py funnel.json --json # no arg = embedded demo
It computes per-step drop-off, an activation score 0-100, and names the biggest-loss step. That step is where the audit focuses first.
Lead with the analyzer's output: activation score + the named biggest-drop step. Then, for each issue: Finding → Impact → Recommendation → Priority
| 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 |
When recommending experiments, consider tests for:
Deliver recommendations following the output quality standard: lead with the highest-leverage finding, provide a clear activation definition, then prioritize experiments by expected impact. Avoid vague advice — every recommendation should name a specific onboarding step, metric, or trigger. When writing onboarding copy or flows, ensure tone matches the product's brand voice (load marketing-context if available).
| Artifact | Description | |----------|-------------| | Activation Definition Doc | Clearly defined aha moment, correlated action, and success metric | | Onboarding Flow Diagram | Step-by-step post-signup flow with drop-off points and decision branches | | Checklist Copy | 3–7 onboarding checklist items ordered by value, with completion messaging | | Email Trigger Map | Trigger conditions, timing, and goals for each onboarding email in the sequence | | Experiment Backlog | Prioritized A/B test ideas for onboarding steps, sorted by expected impact |
development
Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says "/cs:weekly-review". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.
development
Use when someone wants to decide whether a meeting is worth calling, price a meeting in dollars, build a timeboxed agenda with desired outcomes, or turn messy meeting notes into owned action items — or says "should this be a meeting", "/cs:meeting-prep", or "/cs:meeting-actions". Runs a cost gate (ASYNC / NOT-READY / MEET), builds a decision-first agenda, and extracts an owner + due-date checklist that flags every orphan.
development
Convert a rambling description of a desired outcome into one polished, autonomous /goal prompt ready to paste into a fresh session. Use when the user says "/fable-goal", "turn this into a goal prompt", "write me a fable prompt", "write the prompt that builds X", or rambles about something they want made and asks for the prompt that makes it happen. The output is a single copy-paste prompt, never the build itself. Do NOT use when the user wants the thing built right now in this session — only when they want the PROMPT that will make it happen in a fresh session.
development
Use when someone wants to plan a deep work day, time-block their calendar or task list, budget or cut shallow work, protect focus hours, track deep-work sessions and streaks, run an end-of-day shutdown ritual, or says "/deep-work" or "/time-block". Classifies tasks deep vs shallow, builds an energy-first time-blocked schedule that refuses deep demand past the 4-hour ceiling, batches shallow work into at most two windows, and logs focus sessions against a weekly target.