SkillAgentSearch skills...

onboarding-cro

Post-signup user onboarding optimization covering activation metrics, time-to-value reduction, onboarding flow design, empty state optimization, multi-channel coordination, and stalled user recovery.

Install / Use

npx skills add borghei/Claude-Skills --skill onboarding-cro

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

92/100

Supported Platforms

Universal

Our assessment of onboarding-cro

onboarding-cro scores 92/100 on our quality scale, 12th of 46 Human Resources skills we index (top 27%).

Its SKILL.md is 23 KB long, well organised into 54 sections with 10 code examples: a thorough specification that gives an agent plenty to work with.

It has 817 GitHub stars, a meaningful sign that others use it.

Substance
30/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so onboarding-cro is actively maintained.
  • Our last check on 2026-10-28 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 88/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

onboarding-cro compared with similar skills

All 4 of these similar skills score higher than onboarding-cro; compare them before choosing.

SkillScoreStarsUpdatedFormat
onboarding-cro (this skill)by borghei9281757d agoSKILL.md
taste-skillby Leonxlnx100117.6k9d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.9k8d agoCLAUDE.md
x402by browser-use100121.0k4d agoSKILL.md
algorithmic-artby anthropics100177.9k56d agoSKILL.md

Frequently asked questions

How do I install onboarding-cro?
Run npx skills add borghei/Claude-Skills --skill onboarding-cro. The install tabs above show the steps for each supported agent.
Which AI agents does onboarding-cro work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is onboarding-cro safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 88/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is onboarding-cro still maintained?
The repository was last updated about 2 months ago, so onboarding-cro is actively maintained.

name: onboarding-cro description: > Post-signup user onboarding optimization covering activation metrics, time-to-value reduction, onboarding flow design, empty state optimization, multi-channel coordination, and stalled user recovery. license: MIT + Commons Clause metadata: version: 1.0.0 author: borghei category: business-growth updated: 2026-03-31 tags: - cro - onboarding - activation - user-experience - retention - time-to-value

Onboarding CRO

Production-grade user onboarding optimization framework covering activation definition, time-to-value engineering, flow architecture, empty state design, multi-channel coordination, stalled user recovery, and experiment design. Focused on the critical window between signup and habitual product usage.


Table of Contents


Clarify First

Before designing the onboarding, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • [ ] Product type — B2B SaaS, B2C app, marketplace, or content platform (selects the onboarding pattern)
  • [ ] Activation event (aha moment) — the action correlated with 30-day retention (defines what the whole flow drives toward)
  • [ ] Current activation rate + where users drop off — baseline and the biggest funnel bottleneck to fix
  • [ ] Day-1/7/30 retention — sets urgency and whether the problem is onboarding vs product-market fit

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the deliverable.

Initial Assessment

Required Context

| Question | Why It Matters | |----------|---------------| | What is the product type? (B2B SaaS, B2C app, marketplace, content platform) | Determines the onboarding pattern | | What is the core value proposition? | Defines what the aha moment should demonstrate | | What happens immediately after signup? | Identifies the current first-run experience | | What action correlates most with 30-day retention? | Defines the activation event | | Where do users drop off? (funnel data if available) | Pinpoints the biggest bottleneck | | What is the current activation rate? | Baseline for improvement | | What is Day-1 / Day-7 / Day-30 retention? | Context for urgency |


Activation Definition Framework

Finding the Aha Moment

The aha moment is the specific action that, once completed, makes a user significantly more likely to retain. It is NOT a feature -- it is the moment the user experiences the core value.

Method to identify it:

  1. Cohort comparison: Compare 90-day retained users vs churned users. What actions did retained users do in the first 7 days that churned users did not?
  2. Correlation analysis: For each candidate action, calculate the correlation between completing that action in week 1 and being retained at day 30.
  3. Timing analysis: When do retained users complete this action? (Day 1? Day 3? Day 7?)

Activation Event Examples

| Product Type | Activation Event | Why This Works | |-------------|-----------------|----------------| | Project management | Create project + invite 1 team member | Collaboration creates switching costs | | Analytics tool | Install tracking + view first report | Seeing their own data is the value | | Design tool | Create first design + export or share | Output = value realized | | CRM | Import contacts + log first activity | Data investment creates lock-in | | Marketplace | Complete first transaction | Transaction = value delivered | | Content platform | Follow 3+ sources + consume 5+ items | Personalization drives habit | | Communication tool | Send first message + get a reply | Two-sided value activation |

Activation Metric Structure

Activation Rate = Users who reach activation event / Total signups
                  (within first N days)

Target: 40-60% activation within 7 days for B2C
        25-40% activation within 14 days for B2B

Onboarding Flow Architecture

Flow Type Selection

| Approach | Best For | Risk | Mitigation | |----------|----------|------|------------| | Product-first (drop into product) | Simple products, B2C, mobile apps | Blank slate overwhelm | Pre-populated sample data | | Guided setup (wizard) | Products needing configuration | Adds friction before value | Keep to 3-5 steps max | | Value-first (show results immediately) | Products with demo data | May not feel personalized | Use their data if possible | | Template-first | Creative/productivity tools | Choice paralysis | Curate 3-5 starter templates | | Video walkthrough | Complex B2B products | Users skip videos | Keep under 90 seconds |

The First 30-Second Rule

Whatever flow type you choose, within 30 seconds of landing in the product, the user must:

  1. See a clear single next action (not 5 options)
  2. Understand what the product will do for them
  3. Have a visible path forward (no dead ends)

Flow Design Principles

| Principle | Implementation | |-----------|---------------| | One goal per session | First session focuses ONLY on reaching the aha moment | | Do, don't show | User performs the action, not watches a tutorial about it | | Progress creates motivation | Show advancement (checklist, progress bar, celebration) | | Defer complexity | Advanced settings and features surface AFTER activation | | Always escapable | Users can skip or dismiss any onboarding element | | Remember state | If user leaves and returns, resume where they left off |


Time-to-Value Engineering

Time-to-Value (TTV) Reduction Framework

TTV is the elapsed time between signup and the user experiencing core value. Shorter = better.

| Bottleneck | Detection | Fix | Expected TTV Reduction | |-----------|-----------|-----|----------------------| | Setup required before use | Users drop off during setup | Reduce required setup steps, use defaults | 30-50% | | Waiting for data | No value until data arrives | Provide sample/demo data immediately | 40-60% | | Waiting for team members | Value requires collaboration | Enable solo value first, then team | 20-40% | | Integration required | Cannot function without connecting tools | Offer manual input as alternative | 30-50% | | Learning curve | Product too complex for quick win | Guided first action with templates | 20-30% | | Approval/verification required | Email verification, admin approval | Defer verification to after first value | 40-60% |

Quick Win Architecture

Design the onboarding to deliver a "quick win" within the first 3 minutes:

  1. Identify the simplest valuable output the product can deliver
  2. Pre-populate inputs where possible
  3. Minimize decisions (use smart defaults)
  4. Celebrate the output ("You just created your first [X]!")
  5. Immediately show the next step

Empty State Design

Empty states are onboarding moments, not dead ends. Every blank screen is an opportunity to guide the user toward activation.

Empty State Anatomy

┌─────────────────────────────────────┐
│                                     │
│      [Illustration or Preview]      │  Show what this will look like with data
│                                     │
│   What this section does            │  1 sentence, benefit-focused
│                                     │
│   [Primary CTA: Create First X]    │  Single clear action
│                                     │
│   Or try with sample data →        │  Low-friction alternative
│                                     │
└─────────────────────────────────────┘

Empty State Rules

| Rule | Good | Bad | |------|------|-----| | Show the end state | Preview with sample data | Completely blank screen | | Single CTA | "Create your first project" | "Learn more" + "Watch video" + "Read docs" | | Explain the value | "Track your team's progress in one view" | "No projects found" | | Offer sample data | "Try with example data" link | Force creation from scratch |


Onboarding Patterns by Product Type

B2B SaaS

Signup → Setup Wizard (3-5 steps) → First Value Action → Team Invite → Deep Setup
         ├── Company info              ├── Template selection     ├── Email invites
         ├── Role/goal selection       ├── Quick configuration    └── Permissions
         └── Integration connect       └── First output created

Key metric: Time from signup to first team collaboration

Marketplace / Two-Sided

Signup → Complete Profile → Browse/Discover → First Transaction → Repeat Loop
         ├── Photo/avatar         ├── Curated feed          ├── Guided first action
         ├── Preferences          ├── Search + filters      └── Transaction completion
         └── Verification         └── Saved/bookmarked

Key metric: Time from signup to first completed transaction

Mobile App (B2C)

Install → Permission Requests → Quick Win → Push Notification Setup → Habit Loop
          ├── Location (if needed)   ├── Core action            ├── Value-based ask
          ├── Notifications          ├── Immediate result       └── Frequency choice
          └── Camera/contacts        └── Celebration

Key metric: Day-1 retention rate

Content / Media Platform

Signup → Interest Selection → Personalized Feed → First Engagement → Social Connection
         ├── Topic picks          ├── Curated content      ├── Read/watch/listen
         ├── Creator follows      ├── Algorithmic mix      └── Like/save/share
         └── Format preferences   └── Notification prefs

Key metric: Sessions per week in first 14 days


Multi-Channel Coordination

Email + In-App Matrix

| Trigger | In-App Action | Email Action | Timing | |---------|--------------|--------------|--------| | Signup complete | Welcome screen with first step | Welcome email with single CTA | Immediate | | Step 1 complete | Show step 2 | -- (don't email for every step) | Immediate | | 24 hours, incomplete onboarding | Persistent banner/checklist | "Complete your setup" email | 24h after signup | | 72 hours, not activated | Welcome back modal | "Here's what you can do" email | 72h after signup | | Activation achieved | Celebration modal + next feature | Celebration email + next step | Immediate | | Day 7, feature discovery | Contextual tooltip | "Did you know?" feature email | Day 7 | | Day 14, engagement dip | -- | Re-engagement with use case examples | Day 14 |

Email Design Rules

  • Each email has ONE CTA that drives back into the product
  • Personalize based on actions already taken (do not ask them to do what they already did)
  • Keep emails short (< 150 words body)
  • Subject line references the specific next step, not generic "Welcome to [Product]"

Stalled User Recovery

Stalled User Definition

| Stalled State | Criteria | Recovery Priority | |--------------|----------|------------------| | Never started | Signed up, never logged in again | Medium (may be wrong ICP) | | Partially onboarded | Completed 1-2 setup steps, stopped | High (invested effort, hit a wall) | | Active but not activated | Logged in 3+ times, never reached aha moment | Highest (engaged but stuck) | | Activated but churning | Reached aha moment, usage declining | High (retention problem, not onb

Truncated for display — read the full file on GitHub.

Related Skills

View on GitHub
GitHub Stars817
CategoryHuman
Updated1mo ago
Forks141

Languages

HTML

Trust signals

88/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

1 medium