본문으로 건너뛰기
cccskills
무료GitHub에 공개

onboarding-cro

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value — "activation rate," "empty states," "onboarding checklist," "aha moment," "users sign up but don't use the product." Use when users sign up but don't stick around. For signup/registration optimization, see signup-flow-cro. For email sequences, see email-sequence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(3)

  • SKILL.md5.8 KB
  • evals/evals.json6.2 KB
  • references/experiments.md7.6 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Onboarding CRO

Get users to their "aha moment" fast and build habits that drive long-term retention.

Initial Assessment

Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.

Understand first:

  1. Product Context - product type? B2B or B2C? Core value proposition?
  2. Activation Definition - the "aha moment"? What action shows 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 the 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 most strongly correlated with retention: what retained users do that churned users don't; 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 reaching 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, 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

Onboarding opportunities, not dead ends: explain what the area is for, show what it looks like with data, offer one clear action to add the first item, optionally pre-populate 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 a specific CTA, personalize 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 - personal outreach for high-value accounts

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; focus on the biggest drops.

Signup → Step 1 → Step 2 → Activation → Retention
100%      80%       60%       40%         25%

Output Format

Onboarding Audit — per 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

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. Any cohort analysis on successful vs. churned users?

Related Skills

  • signup-flow-cro — optimizing the signup before onboarding
  • email-sequence — onboarding email series
  • paywall-upgrade-cro — converting to paid during/after onboarding
  • ab-test-setup — testing onboarding changes

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Act as a Senior Accessibility Engineer to audit a page, component, or design against WCAG 2.2 AA. Produces a triaged finding list (critical/serious/moderate), focus-order map, contrast report, ARIA decision tree, and a screen-reader test plan. Use when shipping new UI, hardening an existing flow, or preparing for VPAT/accessibility conformance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

When the user wants to plan, design, or implement an A/B test or experiment — "split test," "variant copy," "multivariate test," "hypothesis," "statistical significance," "how long should I run this test," or comparing two versions. For tracking implementation, see analytics-tracking. For page-level conversion optimization, see page-cro.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, full variations — for any paid platform; 'ad copy variations,' 'RSA headlines,' 'bulk ad copy,' 'creative testing,' 'write me some ads.' For campaign strategy and targeting, see paid-ads. For landing page copy, see copywriting.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

ai-seo

무료

When the user wants content cited by LLMs or surfaced in AI-generated answers — 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'AI Overviews,' 'optimize for ChatGPT/Perplexity/Claude,' 'AI citations,' 'zero-click search.' For traditional technical/on-page audits, see seo-audit. For structured data, see schema-markup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

When the user wants to set up, improve, or audit analytics tracking and measurement — "GA4," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "attribution," "Mixpanel," "Segment," "are my events firing," or how to measure marketing results. For A/B test measurement, see ab-test-setup.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

architect

무료

Architectural decision advisor for cloud, data, and SaaS distributed systems. Use when the user asks "should we use X or Y", weighs a tradeoff, or needs a decision matrix, scaling analysis, cost-at-scale review, data-tier design, multi-tenancy model, or API/resilience guidance. For full technical blueprints, use enterprise-design.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

rajitsaha/100xprism102026년 10월 14일 업데이트

rajitsaha의 스킬 모두 보기

이 스킬의 문제 신고