Token导航 LogoToken导航

Agent Skill · 研究检索

customer-onboarding-2(客户引导 2)

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

customer-onboarding-2 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 5,658。

总安装 24,885周安装 997GitHub Stars 公开资料未说明下载 8,056核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:customer-onboarding-2(客户引导 2)
来源仓库:https://github.com/jk-0001/customer-onboarding-2
安装命令:
openclaw skills install customer-onboarding-2
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install customer-onboarding-2

这个 Skill 是做什么的

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

设计并执行客户引导,以促进激活和保留。在为新用户构建入职流程、减少前 30 天内的流失率、缩短价值实现时间或创建入职序列(电子邮件、应用内或手动)时使用。涵盖激活指标、入职步骤设计、减少摩擦以及衡量入职成功。触发“客户入职”、“入职流程”、“用户入职”、“减少早期流失”、“提高激活”、“入职顺序”、“价值实现时间”。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install customer-onboarding-2;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

customer-onboarding-2 怎么安装?

在终端执行 openclaw skills install customer-onboarding-2。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

customer-onboarding-2 支持哪些 AI 工具?

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

customer-onboarding-2 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

customer-onboarding-2 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

customer-onboarding-2 用的人多吗?

公开数据是累计安装 24,885 次,近一周安装 997 次,下载 8,056 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

customer-onboarding-2 安全吗?

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

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。
  • 需要许可证清楚、并且有第三方扫描结果的团队项目。

不太适合

  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
customer-onboarding-2

客户引导 2 · 本页

24,885—需要联网MIT-0通过

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

SKILL.md 原文

name
customer-onboarding
description
Design and execute customer onboarding that drives activation and retention. Use when building onboarding flows for new users, reducing churn in the first 30 days, improving time-to-value, or creating onboarding sequences (email, in-app, or manual). Covers activation metrics, onboarding step design, friction reduction, and measuring onboarding success. Trigger on "customer onboarding", "onboarding flow", "user onboarding", "reduce early churn", "improve activation", "onboarding sequence", "time to value".

Customer Onboarding

Overview

Onboarding is where you keep or lose customers. The first 7-30 days determine whether they stay or churn. Most solopreneurs focus on acquisition and ignore onboarding — then wonder why churn is high. This playbook builds an onboarding system that gets users to their first win fast, builds confidence, and sets them up for long-term success.


Step 1: Define Your Activation Metric

Onboarding isn't about completing a checklist. It's about getting users to experience value — the "aha moment" where the product clicks.

Your activation metric is the action that predicts retention.

Examples:

  • Slack: Sent 2,000 messages as a team
  • Dropbox: Uploaded and shared at least one file
  • SaaS analytics tool: Connected a data source and viewed their first report
  • Project management tool: Created a project and added 3 tasks

How to find your activation metric:

  1. Look at retained customers (those who stuck around 90+ days)
  2. Identify what they did in their first 7 days that non-retained customers didn't do
  3. That action (or set of actions) is your activation metric

Rule: Onboarding is successful when a user completes your activation metric. Everything in your onboarding should drive toward this.


Step 2: Map Your Onboarding Journey

Before designing tactics, map the full journey from signup to activation.

Onboarding journey template:

SIGNUP
  ↓ (What happens immediately after signup?)
SETUP / CONFIGURATION
  ↓ (What do they need to configure? Integrations? Settings? Profile?)
FIRST VALUE MOMENT
  ↓ (What's the simplest, fastest way they can experience value?)
ACTIVATION
  ↓ (They complete the activation metric)
ONGOING ENGAGEMENT
  ↓ (They use the product regularly)

For each stage, ask:

  • What does the user need to do?
  • What's blocking them from doing it? (friction, confusion, missing information)
  • How can we make this easier or faster?

Example (SaaS automation tool):

SIGNUP → Email confirmation

SETUP → Connect first data source (e.g., Google Sheets)
  Friction: Don't know which source to start with
  Solution: Pre-select most common source, add "why start here?" tooltip

FIRST VALUE MOMENT → See automated workflow run successfully
  Friction: Don't know what workflow to build
  Solution: Provide 3 templates, one-click to activate

ACTIVATION → Run 10 workflows successfully
  Friction: Forget to check back after first success
  Solution: Email reminder after 24 hours with progress + next step

ONGOING ENGAGEMENT → Use weekly, add more workflows

Step 3: Reduce Friction at Every Step

Friction = anything that slows down or confuses the user. Every friction point increases the chance they abandon.

Common friction points and fixes:

FrictionImpactFix
Too many fields on signupUsers abandon mid-signupCollect only email + password. Get everything else later.
Unclear next stepUsers sign up, then stare at a blank screenShow a clear "Start here" CTA immediately after signup
Complex setupUsers get overwhelmed and leaveBreak setup into 3-5 small steps with progress bar. Let them skip non-essential steps.
Jargon or unclear labelsUsers don't understand what to doUse plain language. Replace "Configure API endpoint" with "Connect your account"
Long time-to-valueTakes 30+ min to see resultsCreate a fast "quick win" path — even if it's a simplified version of the full value

Rule: Every step in onboarding should take < 2 minutes. If it takes longer, break it into smaller steps or defer it until later.


Step 4: Build Your Onboarding Sequence

Onboarding is not just in-app. It's a multi-channel experience: in-app guidance + email + (optionally) human touch.

In-App Onboarding

Tactics:

  • Welcome modal: Appears immediately after signup. "Welcome! Here's how to get started in 3 steps."
  • Tooltips/hotspots: Highlight key features as users explore ("This is where you create a new project")
  • Checklist: Show progress toward activation ("2 of 5 steps complete — you're almost there!")
  • Empty states: When a user sees a blank page, show helpful prompts ("No projects yet? Start your first one here.")

Tools: Intercom, Appcues, Userflow, or custom-built with plain JavaScript.

Rule: Don't overwhelm. Show 1-2 tips at a time, not 10.

Email Onboarding

Email sequence (5-7 emails over 14 days):

EMAIL 1 (Day 0, immediately after signup):
  Subject: "Welcome to [Product]! Let's get you started."
  Body: Confirm signup, set expectations, link to first step or template

EMAIL 2 (Day 1, if activation metric not hit):
  Subject: "Quick question — stuck on anything?"
  Body: Address common blockers, offer help, link to docs or support

EMAIL 3 (Day 3, if activation metric not hit):
  Subject: "Here's the fastest way to see results"
  Body: Share a quick-win template or walkthrough video

EMAIL 4 (Day 5, if activation metric HIT):
  Subject: "Nice work! Here's what to do next"
  Body: Celebrate their first win, suggest next feature or use case

EMAIL 5 (Day 7, if activation metric not hit):
  Subject: "Need a hand? Let's jump on a quick call"
  Body: Offer a personal onboarding call (manual touch for high-value prospects)

EMAIL 6 (Day 10):
  Subject: "3 pro tips from our best users"
  Body: Share advanced tips or lesser-known features

EMAIL 7 (Day 14):
  Subject: "How's it going? We'd love your feedback"
  Body: Ask how onboarding went, request feedback, link to survey

Personalization triggers: Send different emails based on behavior:

  • If they completed activation → send "here's what to do next" content
  • If they didn't complete activation → send troubleshooting or offer help

Human Touch (Optional, for High-Value Customers)

For high-ticket SaaS or service businesses, add a human layer:

  • Onboarding call: Schedule a 15-30 min call to walk them through setup
  • Check-in emails: Personal email (not automated) asking how it's going
  • Slack/community access: Invite them to a private Slack or Circle community for direct support

When to use: When LTV > $500 or when the product is complex.


Step 5: Measure Onboarding Performance

Track these metrics to know if onboarding is working:

MetricWhat It MeansHealthy Benchmark
Activation rate% of signups who hit activation metric30-60% (varies by product)
Time to activationMedian days/hours from signup to activationUnder 24 hours is ideal
Day 7 retention% of signups still active after 7 days40-60%
Day 30 retention% of signups still active after 30 days25-40%
Onboarding email open/click ratesEngagement with onboarding emailsOpens: 40-60%, Clicks: 10-20%

Where to track: Use your analytics tool (Mixpanel, Amplitude, or simple event tracking in Google Analytics) + email tool (ConvertKit, Mailchimp).

Diagnose issues:

  • Low activation rate? Too much friction in setup, or unclear value prop. Simplify first steps.
  • Long time to activation? Too many steps or too complex. Create a faster "quick win" path.
  • High activation but low Day 30 retention? They got initial value but didn't build a habit. Improve ongoing engagement (notifications, email reminders, new features).

Step 6: Iterate on Onboarding

Onboarding is never "done." Continuously improve based on data and feedback.

Monthly onboarding review:

  1. Check activation rate — is it improving?
  2. Review user feedback from surveys or support tickets — where are people getting stuck?
  3. Watch 2-3 user session recordings (tools: Hotjar, FullStory) — what confuses people?
  4. Test one improvement per month (e.g., simplify signup, add a tooltip, rewrite an email)

A/B testing ideas:

  • Different welcome email subject lines
  • Checklist vs no checklist in-app
  • Video walkthrough vs text instructions
  • Length of signup form (fewer fields vs more upfront info)

Rule: Focus on the biggest drop-off point first. If 50% of users abandon during setup, fixing that is 10x more valuable than optimizing a later step.


Onboarding Mistakes to Avoid

  • Dumping everything on Day 1. Don't explain every feature upfront. Guide them to one quick win, then introduce more over time.
  • No clear next step after signup. A blank screen or "Welcome!" with no guidance kills activation. Always show a clear "Do this first" CTA.
  • Ignoring non-activated users. If someone signs up and doesn't activate, don't give up. Re-engage them with helpful emails or a manual outreach.
  • Making setup mandatory when it's optional. Let users skip non-essential steps. Forcing them to fill out a profile or connect integrations before they see value creates friction.
  • No human touch for high-value customers. If your LTV is $1,000+, a 15-minute onboarding call is worth it. Don't over-automate at the high end.
  • Not measuring time to activation. If it takes 2 weeks for users to see value, you'll lose most of them. Aim for value in < 24 hours.

平台分布

OpenClaw

73.51%
按下载量换算5,922

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

未展示

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills