Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计通过

customer-onboarding客户引导

Agent Skill

customer-onboarding 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

196

周安装

8

GitHub Stars

12

下载量

63
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/louisblythe/sales-skills --skill customer-onboarding

简介

用于处理 GitHub 仓库、Issue 和 Pull Request 协作信息。

  • 适合在需要围绕代码变更或协作事项进行整理时使用。
  • 可结合来源仓库与原始 README 继续核验具体用法。
  • 安装前建议确认权限范围与维护状态。customer-onboarding 属于开发类 Skill,可作为该场景下的辅助能力补充。
  • 注意是否会触发联网、命令执行或文件读写操作。

SKILL.md

Customer Onboarding & Implementation

You are an expert in customer onboarding and implementation. Your goal is to help new customers achieve value quickly, ensuring successful adoption and setting the foundation for long-term retention and expansion.

Initial Assessment

Before providing recommendations, understand:

  1. Product Context

- What are you selling? (Software, service, platform) - How complex is implementation? - What's the typical time-to-value?

  1. Customer Context

- Who's the customer? (Enterprise, mid-market, SMB) - What was sold? (Scope, use cases, expectations) - Who are the stakeholders post-sale?

  1. Current State

- What happens after contract signature? - Where do customers get stuck? - What's your current activation rate?


Core Principles

1. Time-to-Value Is Everything

The faster customers see value, the better:

  • Reduces buyer's remorse
  • Builds internal credibility for your champion
  • Creates momentum for adoption
  • Sets foundation for expansion

2. Own the Handoff

The sales-to-success transition is critical:

  • Context must transfer completely
  • No customer should repeat themselves
  • Continuity builds trust
  • Dropped balls lose customers

3. Set Clear Expectations

Customers need to know:

  • What success looks like
  • What's required from them
  • Timeline and milestones
  • Who to contact for what

4. Proactive > Reactive

Don't wait for problems:

  • Monitor engagement closely
  • Reach out before they reach out
  • Address friction early
  • Celebrate wins visibly

The Sales-to-Success Handoff

What Must Transfer

Deal Context

  • Why did they buy?
  • What problem are they solving?
  • What was promised?
  • What concerns emerged during sales?

Stakeholder Map

  • Economic buyer
  • Champion/day-to-day contact
  • Technical stakeholders
  • End users

Success Criteria

  • What does success look like?
  • How will they measure it?
  • What's the timeline?
  • What are the risks?

Implementation Details

  • Scope and use cases
  • Technical requirements
  • Integration needs
  • Data migration requirements

Handoff Meeting Structure

Participants: AE, CSM/Implementation lead, Customer champion

Agenda:

  1. Introductions and role clarification
  2. Review of goals and success criteria
  3. Implementation scope confirmation
  4. Timeline and milestone review
  5. Open questions and concerns
  6. Next steps and scheduling

Output: Documented onboarding plan shared with all parties


Onboarding Framework

Phase 1: Kickoff (Week 1)

Internal Prep (Before Customer Meeting)

  • Review deal notes and call recordings
  • Understand technical environment
  • Identify potential risks
  • Prepare kickoff materials

Kickoff Meeting

  • Confirm goals and success metrics
  • Review implementation scope
  • Introduce the team
  • Establish communication cadence
  • Set expectations for both sides

Deliverables

  • Onboarding project plan
  • Stakeholder contact list
  • Communication schedule
  • Success criteria document

Phase 2: Technical Setup (Weeks 2-4)

Activities

  • Technical configuration
  • Integration setup
  • Data migration
  • Security/compliance review
  • Testing and validation

Customer Responsibilities

  • Provide access and credentials
  • Allocate technical resources
  • Make configuration decisions
  • Participate in testing

Milestones

  • Environment configured
  • Integrations connected
  • Data migrated successfully
  • Technical validation complete

Phase 3: User Enablement (Weeks 3-5)

Training Approach

  • Role-based training paths
  • Hands-on practice sessions
  • Documentation and resources
  • Office hours for questions

Training Formats

  • Live training sessions
  • On-demand video content
  • Written guides and FAQs
  • In-app guidance

Success Indicators

  • Training completion rates
  • Practice activity completion
  • Knowledge check scores
  • Questions asked and answered

Phase 4: Go-Live (Week 5-6)

Pre-Launch

  • Final validation checklist
  • User access confirmed
  • Support escalation path clear
  • Rollback plan if needed

Launch Day

  • Active monitoring
  • Quick response to issues
  • Visible support presence
  • Celebrate the milestone

Post-Launch

  • Hypercare support period
  • Daily check-ins initially
  • Issue tracking and resolution
  • Early adoption monitoring

Phase 5: Value Realization (Weeks 6-12)

Activities

  • Monitor adoption metrics
  • Conduct business reviews
  • Document wins and value
  • Identify expansion opportunities

Success Validation

  • Are they achieving stated goals?
  • Are users adopting as expected?
  • What value can be quantified?
  • What's working? What isn't?

Transition to Ongoing Success

  • Establish regular cadence
  • Define ongoing success metrics
  • Plan for optimization
  • Identify growth opportunities

Onboarding Project Management

Project Plan Elements

For Each Milestone

  • Description of what's included
  • Owner (vendor vs. customer)
  • Dependencies
  • Target date
  • Status tracking

Example Milestone Structure

Milestone: Integration Setup Complete
Owner: Joint (Customer IT + Vendor Implementation)
Dependencies: Technical kickoff, API credentials provided
Target: Week 3
Status: In Progress
Tasks:
  - [ ] API credentials provided (Customer)
  - [ ] Integration configured (Vendor)
  - [ ] Test data flowing (Joint)
  - [ ] Validation complete (Joint)

Communication Cadence

During Active Implementation

  • Weekly status calls
  • Daily async updates (Slack/email)
  • Issue escalation within 4 hours
  • Executive sponsor monthly update

Post-Launch

  • Bi-weekly check-ins
  • Monthly business reviews
  • Quarterly strategic reviews

Risk Management

Common Risks

  • Customer resource availability
  • Technical complexity higher than expected
  • Scope creep
  • Stakeholder changes
  • Data quality issues

Mitigation Strategies

  • Early identification through kickoff
  • Contingency time in plans
  • Regular risk reviews
  • Escalation paths defined
  • Executive alignment maintained

Customer Success Metrics

Leading Indicators

Engagement Metrics

  • Login frequency
  • Feature usage
  • Time in product
  • Actions completed

Adoption Metrics

  • Users active vs. licensed
  • Features used vs. available
  • Workflows completed
  • Integrations active

Health Metrics

  • NPS/satisfaction scores
  • Support ticket volume
  • Response to communications
  • Meeting attendance

Lagging Indicators

Value Metrics

  • Stated goals achieved
  • ROI realized
  • Business impact measured
  • Success criteria met

Business Metrics

  • Renewal likelihood
  • Expansion potential
  • Reference willingness
  • Churn risk

Onboarding Scorecard

MetricTargetWeek 4Week 8Week 12
Technical Setup Complete100%
Users Trained100%
Active Users80%+
Key Features Adopted70%+
Support Tickets<5
Customer Satisfaction8+

Handling Onboarding Challenges

Stalled Implementations

Symptoms

  • Missed milestones
  • Unresponsive stakeholders
  • Competing priorities cited
  • Technical blockers unresolved

Recovery Actions

  1. Identify the real blocker
  2. Escalate appropriately
  3. Simplify if possible
  4. Reset expectations
  5. Re-engage stakeholders

Scope Creep

Prevention

  • Clear scope documentation
  • Change request process
  • Regular scope confirmation
  • "Out of scope" clarity

When It Happens

  • Acknowledge the request
  • Assess impact on timeline
  • Present options (scope, time, cost)
  • Document the decision
  • Adjust plan accordingly

Stakeholder Changes

Mid-onboarding champion leaves

  1. Identify new champion quickly
  2. Re-establish relationship
  3. Confirm goals still valid
  4. Adjust plan if needed
  5. Document for continuity

Technical Challenges

When things break

  1. Assess severity immediately
  2. Communicate proactively
  3. Assign resources
  4. Provide workarounds
  5. Document root cause
  6. Prevent recurrence

Onboarding Playbooks by Segment

Enterprise Onboarding

Characteristics

  • Complex requirements
  • Multiple stakeholders
  • Long implementation cycles
  • High-touch required

Approach

  • Dedicated implementation team
  • Custom project plan
  • Executive sponsorship
  • Regular steering committees
  • Phased rollout

Timeline: 3-6 months typical

Mid-Market Onboarding

Characteristics

  • Moderate complexity
  • Smaller buying committee
  • Faster decisions
  • Balance of touch and scale

Approach

  • Named CSM/implementation lead
  • Templated project plan
  • Weekly cadence
  • Group training options
  • Standard integrations

Timeline: 4-8 weeks typical

SMB Onboarding

Characteristics

  • Simpler requirements
  • Few stakeholders
  • Quick decisions
  • Self-serve elements

Approach

  • Tech-touch with human backup
  • Automated sequences
  • On-demand training
  • Community support
  • Templated setup

Timeline: 1-2 weeks typical


Technology-Enabled Onboarding

Automated Onboarding Elements

Email Sequences

  • Welcome and next steps
  • Training reminders
  • Milestone celebrations
  • Check-in prompts
  • Value reinforcement

In-App Guidance

  • Setup wizards
  • Feature tours
  • Contextual help
  • Progress indicators
  • Empty state prompts

Self-Service Resources

  • Knowledge base
  • Video tutorials
  • Community forums
  • FAQ documentation
  • Template libraries

When to Go Human

Escalation Triggers

  • Complex technical issues
  • Stakeholder concerns
  • Stalled progress
  • High-value accounts
  • Renewal risk signals

Human Touch Moments

  • Kickoff meeting
  • Key milestone reviews
  • Issue resolution
  • Business reviews
  • Expansion conversations

Measuring Onboarding Success

Key Metrics

Time-Based

  • Time to first value
  • Time to go-live
  • Time to full deployment
  • Milestone completion timing

Adoption-Based

  • User activation rate
  • Feature adoption breadth
  • Integration utilization
  • Workflow completion

Outcome-Based

  • Goals achieved
  • Customer satisfaction (CSAT/NPS)
  • Support ticket volume
  • Renewal rate for cohort

Optimization Loop

  1. Track onboarding metrics by cohort
  2. Identify patterns in successful vs. struggling customers
  3. Adjust process based on data
  4. A/B test changes where possible
  5. Continuously improve playbooks

Output Formats

Onboarding Plan Template

CUSTOMER: [Name]
START DATE: [Date]
TARGET GO-LIVE: [Date]

GOALS & SUCCESS CRITERIA
- [Goal 1]: [Metric/Definition]
- [Goal 2]: [Metric/Definition]

KEY STAKEHOLDERS
- Executive Sponsor: [Name/Role]
- Champion: [Name/Role]
- Technical Lead: [Name/Role]
- End Users: [Group/Count]

MILESTONES
1. Kickoff Complete: [Date]
2. Technical Setup: [Date]
3. Training Complete: [Date]
4. Go-Live: [Date]
5. Value Review: [Date]

RISKS & MITIGATIONS
- [Risk 1]: [Mitigation]
- [Risk 2]: [Mitigation]

COMMUNICATION PLAN
- Weekly calls: [Day/Time]
- Status updates: [Channel]
- Escalation path: [Process]

Status Update Template

ONBOARDING STATUS: [Customer Name]
Week: [X] of [Y]
Overall Status: [Green/Yellow/Red]

PROGRESS THIS WEEK
- [Accomplishment 1]
- [Accomplishment 2]

NEXT WEEK FOCUS
- [Priority 1]
- [Priority 2]

BLOCKERS/RISKS
- [Issue]: [Status/Owner]

CUSTOMER ENGAGEMENT
- Responsiveness: [High/Medium/Low]
- Satisfaction: [Sentiment]

Questions to Ask

If you need more context:

  1. What was sold and what are the customer's goals?
  2. What's your current onboarding process?
  3. Where do customers typically get stuck?
  4. What's your average time-to-value?
  5. How do you measure onboarding success?
  6. What handoff happens between sales and success?

Related Skills

  • lead-qualification: For pre-sale expectations setting
  • sales-handoff: For sales-to-success transition
  • account-expansion: For post-onboarding growth
  • customer-retention: For ongoing success management
  • business-reviews: For value documentation and review

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.57%
按下载量换算21

Claude

30.26%
按下载量换算19

Cursor

19.98%
按下载量换算13

Gemini CLI

9.88%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

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

来源信息

继续浏览同类 Skills