Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

customer-onboarding客户引导

Agent Skill

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

总安装

343

周安装

14

GitHub Stars

7

下载量

110
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/jk-0001/skills --skill customer-onboarding

简介

用于查找、检索和筛选相关信息,支持关键词和任务场景定位。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中快速获取候选结果。
  • 结合来源仓库和 README 核验具体用法,确保功能匹配需求。
  • 安装命令:npx skills add https://github.com/jk-0001/skills --skill customer-onboarding。
  • 建议确认权限范围和维护状态,避免触发不必要的联网或文件操作。

SKILL.md

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.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.77%
按下载量换算39

Claude

29.87%
按下载量换算33

Cursor

19.07%
按下载量换算21

Gemini CLI

9.04%
按下载量换算10

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

来源信息

继续浏览同类 Skills