Token导航 LogoToken导航

Agent Skill · 研究检索

customer-success-manager(客户成功经理)

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

customer-success-manager 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为执行命令;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 31,227。

总安装 2,742周安装 112GitHub Stars 13,189下载 887核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/alirezarezvani/claude-skills --skill customer-success-manager

这个 Skill 是做什么的

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

提供客户健康度评分与流失预警分析,支持留存策略和增购机会识别。适用于 SaaS 或订阅制企业的客户成功管理与续约风险管控。基于多维数据生成可解释的健康指数和干预建议。customer-success-manager 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

输入需包含使用频率、支持工单、合同周期和互动记录字段。输出包括风险客户清单、扩容机会列表和定制化沟通话术模板。

来源仓库内路径:skills/customer-success-manager

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

customer-success-manager 怎么安装?

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

customer-success-manager 支持哪些 AI 工具?

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

customer-success-manager 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 npx skills add https://github.com/alirezarezvani/claude-skills --skill customer-success-manager 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

customer-success-manager 是免费的吗?

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

customer-success-manager 用的人多吗?

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

customer-success-manager 安全吗?

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

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。
  • 来源仓库有 13,189 星,维护活跃度相对可查。

先想清楚的地方

  • 需要执行命令,装到常用环境前要先评估影响面。
  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 不能接受 Skill 在你机器上执行命令的人。
  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 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-success-manager

客户成功经理 · 本页

2,74213,189执行命令未明确通过

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

SKILL.md 原文

Customer Success Manager

Production-grade customer success analytics with multi-dimensional health scoring, churn risk prediction, and expansion opportunity identification. Three Python CLI tools provide deterministic, repeatable analysis using standard library only -- no external dependencies, no API calls, no ML models.


Table of Contents


Input Requirements

All scripts accept a JSON file as positional input argument. See assets/sample_customer_data.json for complete schema examples and sample data.

Health Score Calculator

Required fields per customer object: customer_id, name, segment, arr, and nested objects usage (login_frequency, feature_adoption, dau_mau_ratio), engagement (support_ticket_volume, meeting_attendance, nps_score, csat_score), support (open_tickets, escalation_rate, avg_resolution_hours), relationship (executive_sponsor_engagement, multi_threading_depth, renewal_sentiment), and previous_period scores for trend analysis.

Churn Risk Analyzer

Required fields per customer object: customer_id, name, segment, arr, contract_end_date, and nested objects usage_decline, engagement_drop, support_issues, relationship_signals, and commercial_factors.

Expansion Opportunity Scorer

Required fields per customer object: customer_id, name, segment, arr, and nested objects contract (licensed_seats, active_seats, plan_tier, available_tiers), product_usage (per-module adoption flags and usage percentages), and departments (current and potential).


Output Formats

All scripts support two output formats via the --format flag:

  • text (default): Human-readable formatted output for terminal viewing
  • json: Machine-readable JSON output for integrations and pipelines

How to Use

Quick Start

# Health scoring
python scripts/health_score_calculator.py assets/sample_customer_data.json
python scripts/health_score_calculator.py assets/sample_customer_data.json --format json

# Churn risk analysis
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json
python scripts/churn_risk_analyzer.py assets/sample_customer_data.json --format json

# Expansion opportunity scoring
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json
python scripts/expansion_opportunity_scorer.py assets/sample_customer_data.json --format json

Workflow Integration

# 1. Score customer health across portfolio
python scripts/health_score_calculator.py customer_portfolio.json --format json > health_results.json
# Verify: confirm health_results.json contains the expected number of customer records before continuing

# 2. Identify at-risk accounts
python scripts/churn_risk_analyzer.py customer_portfolio.json --format json > risk_results.json
# Verify: confirm risk_results.json is non-empty and risk tiers are present for each customer

# 3. Find expansion opportunities in healthy accounts
python scripts/expansion_opportunity_scorer.py customer_portfolio.json --format json > expansion_results.json
# Verify: confirm expansion_results.json lists opportunities ranked by priority

# 4. Prepare QBR using templates
# Reference: assets/qbr_template.md

Error handling: If a script exits with an error, check that:

  • The input JSON matches the required schema for that script (see Input Requirements above)
  • All required fields are present and correctly typed
  • Python 3.7+ is being used (python --version)
  • Output files from prior steps are non-empty before piping into subsequent steps

Scripts

1. health_score_calculator.py

Purpose: Multi-dimensional customer health scoring with trend analysis and segment-aware benchmarking.

Dimensions and Weights:

DimensionWeightMetrics
Usage30%Login frequency, feature adoption, DAU/MAU ratio
Engagement25%Support ticket volume, meeting attendance, NPS/CSAT
Support20%Open tickets, escalation rate, avg resolution time
Relationship25%Executive sponsor engagement, multi-threading depth, renewal sentiment

Classification:

  • Green (75-100): Healthy -- customer achieving value
  • Yellow (50-74): Needs attention -- monitor closely
  • Red (0-49): At risk -- immediate intervention required

Usage:

python scripts/health_score_calculator.py customer_data.json
python scripts/health_score_calculator.py customer_data.json --format json

2. churn_risk_analyzer.py

Purpose: Identify at-risk accounts with behavioral signal detection and tier-based intervention recommendations.

Risk Signal Weights:

Signal CategoryWeightIndicators
Usage Decline30%Login trend, feature adoption change, DAU/MAU change
Engagement Drop25%Meeting cancellations, response time, NPS change
Support Issues20%Open escalations, unresolved critical, satisfaction trend
Relationship Signals15%Champion left, sponsor change, competitor mentions
Commercial Factors10%Contract type, pricing complaints, budget cuts

Risk Tiers:

  • Critical (80-100): Immediate executive escalation
  • High (60-79): Urgent CSM intervention
  • Medium (40-59): Proactive outreach
  • Low (0-39): Standard monitoring

Usage:

python scripts/churn_risk_analyzer.py customer_data.json
python scripts/churn_risk_analyzer.py customer_data.json --format json

3. expansion_opportunity_scorer.py

Purpose: Identify upsell, cross-sell, and expansion opportunities with revenue estimation and priority ranking.

Expansion Types:

  • Upsell: Upgrade to higher tier or more of existing product
  • Cross-sell: Add new product modules
  • Expansion: Additional seats or departments

Usage:

python scripts/expansion_opportunity_scorer.py customer_data.json
python scripts/expansion_opportunity_scorer.py customer_data.json --format json

Reference Guides

ReferenceDescription
references/health-scoring-framework.mdComplete health scoring methodology, dimension definitions, weighting rationale, threshold calibration
references/cs-playbooks.mdIntervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures
references/cs-metrics-benchmarks.mdIndustry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry

Templates

TemplatePurpose
assets/qbr_template.mdQuarterly Business Review presentation structure
assets/success_plan_template.mdCustomer success plan with goals, milestones, and metrics
assets/onboarding_checklist_template.md90-day onboarding checklist with phase gates
assets/executive_business_review_template.mdExecutive stakeholder review for strategic accounts

Best Practices

  1. Combine signals: Use all three scripts together for a complete customer picture
  2. Act on trends, not snapshots: A declining Green is more urgent than a stable Yellow
  3. Calibrate thresholds: Adjust segment benchmarks based on your product and industry per references/health-scoring-framework.md
  4. Prepare with data: Run scripts before every QBR and executive meeting; reference references/cs-playbooks.md for intervention guidance

Limitations

  • No real-time data: Scripts analyze point-in-time snapshots from JSON input files
  • No CRM integration: Data must be exported manually from your CRM/CS platform
  • Deterministic only: No predictive ML -- scoring is algorithmic based on weighted signals
  • Threshold tuning: Default thresholds are industry-standard but may need calibration for your business
  • Revenue estimates: Expansion revenue estimates are approximations based on usage patterns

Last Updated: February 2026 Tools: 3 Python CLI tools Dependencies: Python 3.7+ standard library only

平台分布

Codex

38.51%
按下载量换算342

Claude

29.34%
按下载量换算260

Cursor

19.82%
按下载量换算176

Gemini CLI

9.22%
按下载量换算82

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 npx skills add https://github.com/alirezarezvani/claude-skills --skill customer-success-manager 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills