agentleFS
darkweb19darkweb19/skills/onboarding-cro/SKILL.md

onboarding-cro

Skill0 starsChanged 28 days agoApache-2.0View on GitHub

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.

50 other projects use a version of this, 45 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use product-marketing-context, aso-audit and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • xfstudioSkill

    product-marketing-context

    When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' or wants to avoid repeating foundational information across marketing tasks. Creates `.claude/product-marketing-context.md` that other marketing skills reference.

    Also in 20 projects that use this

  • ai-vitaSkill

    aso-audit

    When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

    Also in 5 projects that use this

  • ukunal91appSkill

    revops

    When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see email-sequence. For pricing decisions, see pricing-strategy.

    Also in 18 projects that use this

  • buildingwithaiSkill

    sales-enablement

    Master world-class sales enablement from foundations to execution. Build comprehensive enablement programs, develop effective training and coaching systems, implement data-driven content strategies, leverage AI and modern technology stacks, establish cross-functional collaboration, measure ROI with precision, and drive revenue growth. Covers sales methodologies (MEDDIC, SPICED, BANT), maturity models (Forrester, Gartner), enablement frameworks, change management, remote enablement, market segment strategies (SMB, Mid-Market, Enterprise), and team building. Based on 2024-2025 industry research from Gartner, Forrester, Product Marketing Alliance, Sales Enablement Collective, and leading practitioners.

    Also in 18 projects that use this

  • ukunal91appSkill

    lead-magnets

    When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tool-strategy. For writing the actual content, see copywriting. For the email sequence after capture, see email-sequence.

    Also in 13 projects that use this

  • +2 more from ukunal91app

The file

We split this skill into the rules it gives an agent

8 rules. 6 are common, 1 is distinctive, and 1 is very specific to this project.

  • 6

    Common

    Most of the 48 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If .claude/product-marketing-context.md exists, read it before asking questions.

    line 19
  2. Common:

    Before providing recommendations, understand:

    line 21
  3. Common:

    Remove every step between signup and experiencing core value.

    line 32
  4. Common:

    Start with quick wins

    line 92
  5. Common:

    Don't repeat for returning users

    line 114
  6. Distinctive:

    Run the bundled analyzer on your step counts instead of eyeballing:

    line 167
  7. Common:

    When recommending experiments, consider tests for:

    line 205
  8. Common:

    Do you have cohort analysis on successful vs.

    line 219

“Common” is measured: kept by at least 6 in 10 of the 48 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 .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:

  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)

ApproachBest ForRisk
Product-firstSimple products, B2C, mobileBlank slate overwhelm
Guided setupProducts needing personalizationAdds friction before value
Value-firstProducts with demo dataMay 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

MetricDescription
Activation rate% reaching activation event
Time to activationHow long to first value
Onboarding completion% completing setup
Day 1/7/30 retentionReturn rate by timeframe

Funnel Analysis

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.


Output Format

Onboarding Audit

Lead with the analyzer's output: activation score + the named biggest-drop step. Then, 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 TypeKey Steps
B2B SaaSSetup wizard → First value action → Team invite → Deep setup
MarketplaceComplete profile → Browse → First transaction → Repeat loop
Mobile AppPermissions → Quick win → Push setup → Habit loop
Content PlatformFollow/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

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 — WHEN optimizing the registration and pre-onboarding flow before users ever land in-app. NOT when users have already signed up and activation is the goal.
  • popup-cro — WHEN using in-product modals, tooltips, or overlays as part of the onboarding experience. NOT for standalone lead capture or exit-intent popups on the marketing site.
  • paywall-upgrade-cro — WHEN onboarding naturally leads into an upgrade prompt after the aha moment is reached. NOT during early onboarding before value is delivered.
  • ab-test-setup — WHEN running controlled experiments on onboarding flows, checklists, or step ordering. NOT for initial brainstorming or design.
  • marketing-context — Foundation skill. ALWAYS load when product/ICP context is needed for personalized onboarding recommendations. NOT optional — load before this skill if available.

Communication

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).


Proactive Triggers

  • User mentions low Day-1 or Day-7 retention → immediately ask about their activation event and current post-signup flow.
  • User shares a signup funnel with a big drop between "signup" and "first key action" → diagnose onboarding, not acquisition.
  • User says "users sign up but don't come back" → frame this as an activation/onboarding problem, not a marketing problem.
  • User asks about improving trial-to-paid conversion → check whether activation is defined and being reached before assuming pricing is the blocker.
  • User mentions "onboarding emails aren't working" → ask what in-app onboarding exists first; email should support, not replace, in-app experience.

Output Artifacts

ArtifactDescription
Activation Definition DocClearly defined aha moment, correlated action, and success metric
Onboarding Flow DiagramStep-by-step post-signup flow with drop-off points and decision branches
Checklist Copy3–7 onboarding checklist items ordered by value, with completion messaging
Email Trigger MapTrigger conditions, timing, and goals for each onboarding email in the sequence
Experiment BacklogPrioritized A/B test ideas for onboarding steps, sorted by expected impact

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.