Token导航 LogoToken导航

Agent Skill · 研究检索

onboarding-cro(入职 cro)

onboarding-cro 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

onboarding-cro 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为只读;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 40,169。

总安装 1,320周安装 55GitHub Stars 103下载 440核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:onboarding-cro(入职 cro)
来源仓库:https://github.com/borghei/claude-skills
仓库路径:skills/onboarding-cro
安装命令:
npx skills add https://github.com/borghei/claude-skills --skill onboarding-cro
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/borghei/claude-skills --skill onboarding-cro

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

onboarding-cro 构建用户入职优化框架,聚焦激活定义、价值实现时间线与流失用户召回机制。覆盖空状态设计、多通道协同与实验驱动的流程改进,提升产品习惯养成率。提供结构化 A/B 测试设计与漏斗转化分析工具,适配不同产品类型。部署时需注意合规要求,避免过度引导或干扰用户体验的设计模式。

适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/onboarding-cro

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/borghei/claude-skills --skill onboarding-cro;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它标注为只读,先用只读任务试一次,确认行为符合预期再扩大使用范围。

常见问题

6 条

onboarding-cro 怎么安装?

在终端执行 npx skills add https://github.com/borghei/claude-skills --skill onboarding-cro。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

onboarding-cro 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

onboarding-cro 需要什么权限?

权限级别是只读。该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

onboarding-cro 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

onboarding-cro 用的人多吗?

公开数据是累计安装 1,320 次,近一周安装 55 次,下载 440 次,GitHub 103 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

onboarding-cro 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 标注为只读权限,试用阶段不容易误改本地文件。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 只想先试试效果、不希望它改动本地文件的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
onboarding-cro

入职 cro · 本页

1,320103只读未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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


Initial Assessment

Required Context

QuestionWhy 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 TypeActivation EventWhy This Works
Project managementCreate project + invite 1 team memberCollaboration creates switching costs
Analytics toolInstall tracking + view first reportSeeing their own data is the value
Design toolCreate first design + export or shareOutput = value realized
CRMImport contacts + log first activityData investment creates lock-in
MarketplaceComplete first transactionTransaction = value delivered
Content platformFollow 3+ sources + consume 5+ itemsPersonalization drives habit
Communication toolSend first message + get a replyTwo-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

ApproachBest ForRiskMitigation
Product-first (drop into product)Simple products, B2C, mobile appsBlank slate overwhelmPre-populated sample data
Guided setup (wizard)Products needing configurationAdds friction before valueKeep to 3-5 steps max
Value-first (show results immediately)Products with demo dataMay not feel personalizedUse their data if possible
Template-firstCreative/productivity toolsChoice paralysisCurate 3-5 starter templates
Video walkthroughComplex B2B productsUsers skip videosKeep 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

PrincipleImplementation
One goal per sessionFirst session focuses ONLY on reaching the aha moment
Do, don't showUser performs the action, not watches a tutorial about it
Progress creates motivationShow advancement (checklist, progress bar, celebration)
Defer complexityAdvanced settings and features surface AFTER activation
Always escapableUsers can skip or dismiss any onboarding element
Remember stateIf 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.

BottleneckDetectionFixExpected TTV Reduction
Setup required before useUsers drop off during setupReduce required setup steps, use defaults30-50%
Waiting for dataNo value until data arrivesProvide sample/demo data immediately40-60%
Waiting for team membersValue requires collaborationEnable solo value first, then team20-40%
Integration requiredCannot function without connecting toolsOffer manual input as alternative30-50%
Learning curveProduct too complex for quick winGuided first action with templates20-30%
Approval/verification requiredEmail verification, admin approvalDefer verification to after first value40-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

RuleGoodBad
Show the end statePreview with sample dataCompletely 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" linkForce 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

TriggerIn-App ActionEmail ActionTiming
Signup completeWelcome screen with first stepWelcome email with single CTAImmediate
Step 1 completeShow step 2-- (don't email for every step)Immediate
24 hours, incomplete onboardingPersistent banner/checklist"Complete your setup" email24h after signup
72 hours, not activatedWelcome back modal"Here's what you can do" email72h after signup
Activation achievedCelebration modal + next featureCelebration email + next stepImmediate
Day 7, feature discoveryContextual tooltip"Did you know?" feature emailDay 7
Day 14, engagement dip--Re-engagement with use case examplesDay 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 StateCriteriaRecovery Priority
Never startedSigned up, never logged in againMedium (may be wrong ICP)
Partially onboardedCompleted 1-2 setup steps, stoppedHigh (invested effort, hit a wall)
Active but not activatedLogged in 3+ times, never reached aha momentHighest (engaged but stuck)
Activated but churningReached aha moment, usage decliningHigh (retention problem, not onboarding)

Recovery Tactics

Stalled StateTactic 1Tactic 2Tactic 3
Never started"We set up [X] for you" emailPre-populated account--
Partially onboarded"Pick up where you left off" emailSimplify remaining stepsOffer live help
Active but not activatedIn-app guided walkthrough"Users like you do [X]" suggestionHuman outreach for high-value
Activated but churningFeature discovery emailsUsage tips based on their workflowCSM outreach for enterprise

Human Touch Triggers

For high-value accounts (enterprise, high ACV), trigger human outreach when:

  • User is > 48 hours stalled in onboarding
  • User visits help docs more than 3 times in a session
  • User starts and abandons the same action 2+ times
  • User's engagement score drops below threshold after initial activation

Onboarding Checklist Design

When to Use a Checklist

  • Multiple setup steps required before full value
  • Product has several features to discover
  • Self-serve B2B products where users self-onboard
  • Products with a clear "fully set up" state

Checklist Best Practices

RuleImplementation
3-7 itemsFewer than 3 = not worth a checklist. More than 7 = overwhelming.
Order by valueMost impactful action first
Start with quick winsFirst item should be completable in < 60 seconds
Show progressProgress bar or "3 of 5 complete" counter
Pre-check completed itemsIf they already did something, mark it done
Celebrate completionAnimation, confetti, "You're all set!" message
Dismissable"I'll do this later" option. Never trap users.
Persistent but not blockingSidebar widget or dashboard card, not a blocking modal

Checklist Item Design

Each item should include:

  • Clear action label ("Import your contacts")
  • Why it matters ("So you can track interactions")
  • Estimated time ("Takes about 2 minutes")
  • CTA button ("Import Now")

Tooltip and Tour Design

When to Use Tooltips/Tours

  • Complex UI where features are not self-evident
  • Power features users might miss
  • UI changes after a major update
  • Features that require specific discovery order

Tour Best Practices

RuleImplementation
Max 3-5 steps per tourMore than 5 and users will dismiss
Dismissable at any time"Skip tour" on every step
Don't repeat for returning usersTrack tour completion, never show again
Highlight the actual UI elementSpotlight effect on the element being explained
Action-oriented"Click here to create a project" not "This is where projects live"
ProgressiveShow basic tour on day 1, advanced features tour on day 7

Metrics and Measurement

Key Metrics

MetricFormulaTarget
Activation rateUsers reaching activation / Total signupsB2C: 40-60%, B2B: 25-40%
Time to activationMedian time from signup to activation eventB2C: < 1 day, B2B: < 7 days
Onboarding completion rateUsers completing all steps / Total signups> 60%
Day-1 retentionUsers returning day after signup / Total signups> 40%
Day-7 retentionUsers active 7 days after signup / Total signups> 25%
Day-30 retentionUsers active 30 days after signup / Total signups> 15%
Checklist completion rateUsers finishing all items / Users who saw checklist> 50%

Funnel Analysis Template

Signup                  100%
├── First login          85%  (-15% never return)
├── Setup step 1         70%  (-15% drop during setup)
├── Setup step 2         55%  (-15% setup friction)
├── First value action   40%  (-15% blank slate / confusion)
├── Activation event     30%  (-10% incomplete value delivery)
└── Day-7 return         20%  (-10% no habit formed)

Focus optimization on the step with the largest absolute drop.


Experiment Framework

High-Impact Experiments

ExperimentHypothesisMetric
Reduce setup stepsFewer steps = higher completionActivation rate
Pre-populate with sample dataReduces blank slate anxietyTime to first value action
Add onboarding checklistProgress visibility increases completionOnboarding completion rate
Defer email verificationRemoves friction before valueTime to activation
Personalize by role/goalRelevant path increases activationActivation rate by segment

Medium-Impact Experiments

ExperimentHypothesisMetric
Welcome video vs textVideo may improve or hurt depending on productActivation rate + time on first screen
Checklist order changeValue-first ordering improves completionChecklist completion rate
Guided tour vs self-discoverTours help complex productsFeature adoption rate
In-app chat during onboardingReal-time help reduces stallsStall rate, activation rate

Output Artifacts

ArtifactFormatDescription
Activation Definition DocStructured definitionAha moment, activation event, success metric, measurement plan
Onboarding Flow DiagramStep-by-step flowPost-signup flow with drop-off points and decision branches
Checklist SpecificationItem-by-item design3-7 items with action, rationale, time estimate, and CTA
Email Trigger MapTrigger/timing/goal tableConditions and content for each onboarding email
Empty State CopyPer-screen designIllustration description, headline, body, CTA for each empty state
Experiment BacklogPrioritized tableTest ideas ranked by expected impact and effort
Stalled User PlaybookDecision treeDetection criteria, recovery tactics, escalation rules

Related Skills

  • signup-flow-cro -- Use for optimizing the registration flow before users enter the product. Onboarding-cro starts after signup is complete.
  • paywall-upgrade-cro -- Use when onboarding leads into upgrade moments. Do not show paywalls before the aha moment is reached.
  • churn-prevention -- Use when users activate but then churn. If they never activate, the problem is onboarding, not churn.
  • page-cro -- Use when the marketing page before signup is the bottleneck, not the post-signup experience.

Tool Reference

1. activation_funnel_analyzer.py

Purpose: Analyze an onboarding activation funnel to identify the biggest drop-off points and estimate the impact of fixing each step.

python scripts/activation_funnel_analyzer.py funnel_data.json
python scripts/activation_funnel_analyzer.py funnel_data.json --json
FlagRequiredDescription
funnel_data.jsonYesJSON file with funnel step names and user counts
--jsonNoOutput results as JSON

2. onboarding_checklist_scorer.py

Purpose: Score an onboarding checklist design against best practices (item count, ordering, quick wins, progress indication).

python scripts/onboarding_checklist_scorer.py checklist.json
python scripts/onboarding_checklist_scorer.py checklist.json --json
FlagRequiredDescription
checklist.jsonYesJSON file with checklist items and their properties
--jsonNoOutput results as JSON

3. ttv_estimator.py

Purpose: Estimate time-to-value (TTV) based on onboarding steps and identify bottlenecks that can be reduced or eliminated.

python scripts/ttv_estimator.py onboarding_steps.json
python scripts/ttv_estimator.py onboarding_steps.json --json
FlagRequiredDescription
onboarding_steps.jsonYesJSON file with onboarding steps, estimated minutes, and requirements
--jsonNoOutput results as JSON

Troubleshooting

ProblemLikely CauseSolution
Activation rate below 25% (B2B) or 40% (B2C)Aha moment not reached fast enoughRun ttv_estimator.py to identify TTV bottlenecks; target first value within 5 minutes
Users complete onboarding but do not return Day 7Onboarding leads to setup, not to valueRestructure flow so the first session delivers a meaningful output, not just configuration
Onboarding checklist completion below 50%Too many items or first item is too complexReduce to 3-7 items; start with a quick win completable in under 60 seconds; use onboarding_checklist_scorer.py to audit
Stalled users at 40%+ of signupsBlank slate problem or unclear next stepAdd pre-populated sample data and empty state CTAs; implement stalled user recovery emails at 24h and 72h
Day-1 retention below 30%First-run experience has dead ends or confusionApply the 30-second rule: within 30 seconds, user sees a single next action, understands the value, and has a path forward
Email onboarding sequences have low open ratesGeneric subject lines or wrong timingPersonalize subject lines to reference the specific next step; send at trigger-based timing, not fixed schedules
Team invite rate is lowInvite step placed before value is demonstratedDefer team invite until after the user has experienced core value individually

Success Criteria

  • Activation rate of 30-40% within 14 days for B2B (40-60% for B2C)
  • Time-to-first-value under 5 minutes (verified by ttv_estimator.py)
  • Onboarding completion rate above 60%
  • Day-1 retention above 40%
  • Day-7 retention above 25%
  • Stalled user recovery emails achieve 10%+ reactivation rate
  • Onboarding checklist scores 70+ on onboarding_checklist_scorer.py assessment

Scope & Limitations

  • In scope: Activation definition, onboarding flow design, time-to-value engineering, empty state design, checklist design, tooltip/tour design, email coordination, stalled user recovery, experiment design
  • Out of scope: Signup/registration flow (use signup-flow-cro), marketing page optimization (use page-cro), long-term retention strategy, feature development
  • Data dependency: Best results require funnel analytics (per-step drop-off data); without this, optimization is based on heuristics
  • Product type matters: B2B SaaS, marketplace, mobile app, and content platforms have fundamentally different onboarding patterns; use the correct pattern for your product type
  • No silver bullet: If the product does not deliver value, no amount of onboarding optimization will fix retention; validate product-market fit first

Integration Points

  • signup-flow-cro -- Optimizes the registration flow before onboarding begins; hand-off point is the moment after successful account creation
  • churn-prevention -- When users activate but then churn, the problem shifts from onboarding to retention; use churn-prevention for post-activation churn
  • paywall-upgrade-cro -- Upgrade prompts should only appear after the aha moment is reached; never show paywalls during initial onboarding
  • page-cro -- When the bottleneck is the marketing page (users are not signing up), optimize the page before optimizing onboarding
  • customer-success-manager -- For enterprise accounts, human-assisted onboarding complements product-led flows; CS team should monitor activation metrics

平台分布

Codex

36.51%
按下载量换算161

Claude

26.57%
按下载量换算117

Cursor

19.73%
按下载量换算87

Gemini CLI

8.86%
按下载量换算39

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills