Onboarding Cro

v1.0.0

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

0· 152·0 current·0 all-time
byMario Karras@mariokarras

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mariokarras/abm-onboarding-cro.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Onboarding Cro" (mariokarras/abm-onboarding-cro) from ClawHub.
Skill page: https://clawhub.ai/mariokarras/abm-onboarding-cro
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install abm-onboarding-cro

ClawHub CLI

Package manager switcher

npx clawhub@latest install abm-onboarding-cro
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description (onboarding CRO) match the SKILL.md content. The skill asks only for product/context files and provides UX, metrics, and experiment guidance; there are no unrelated binaries, credentials, or external services requested.
Instruction Scope
Runtime instructions are prescriptive and bounded to onboarding tasks. They explicitly say to read .agents/product-marketing-context.md or .claude/product-marketing-context.md if present — this is reasonable for tailoring advice, but it means the skill will access workspace files if they exist. It does not instruct reading other system files, calling external endpoints, or accessing unrelated credentials.
Install Mechanism
No install spec and no code to execute. Instruction-only skills are lower risk because nothing is written to disk or downloaded.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths beyond optional product-marketing-context files. Requested scope is proportionate to its purpose.
Persistence & Privilege
always is false and the skill is user-invocable; it does not request permanent presence or modification of other skills/configs. Autonomous invocation is permitted by platform default but is not combined with other concerning privileges.
Assessment
This skill is instruction-only and appears coherent with its onboarding/CRO purpose. Before installing, note that it will look for product-marketing-context files in the agent workspace (.agents/product-marketing-context.md or .claude/product-marketing-context.md) and use that content to tailor recommendations — review those files for sensitive data you don't want exposed. There are no network endpoints, installers, or credential requests in the skill itself, but recommendations may imply you should connect analytics or email tools (which would require separate credentials). If you want to be cautious, preview or remove any sensitive workspace context files before invoking the skill, and run it in a controlled environment first.

Like a lobster shell, security has layers — review code before you run it.

latestvk97bqbbhttnnb7jr1tchxdsprh8371nd
152downloads
0stars
1versions
Updated 1mo ago
v1.0.0
MIT-0

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)

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%

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

For comprehensive experiment ideas: See 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

Comments

Loading comments...