中级Agent Skill

客户成功管理

根据 SaaS 客户的使用、互动、支持记录和收入信息,计算客户健康度评分,并检查流失风险与增购机会。这项 Skill 包含三个 Python 工具,帮助客户成功团队把账户资料整理成可重复运行的分析,明确哪些客户值得优先跟进,以及每条建议由哪些规则触发。

浏览量
0
复制次数
0
收藏
0
编辑评分
80/100
01

这个 Skill 是做什么的

这项 Skill 面向按账户管理的客户成功工作,例如向商家销售软件后持续跟进客户使用情况。它读取结构化 JSON 数据,按规则生成健康度、留存风险和增购评估,便于团队定期采用相同口径复查。

适合已经掌握客户使用和商务资料、需要安排跟进优先级的团队。输出用于支持账户讨论和行动计划,不是机器学习预测,也不等于普通零售买家的复购概率分析。CRM 同步和对外联系需要由现有工作流程完成。

02

它有什么特色

01

方法与优势

三个使用 Python 标准库的工具分别处理健康度、流失风险和增购评估。分开看这些维度,有助于避免把使用活跃直接等同于适合增购,或把支持请求较多直接判断为一定会流失。

02

适用任务

示例结构明确需要哪些账户字段,规则输出也便于核对和重复运行。比较不同客户群之前先统一输入口径,再结合建议安排跟进,例如了解使用障碍、检查续费情况或进一步确认增购需求。

03

安装前的特殊要求

需要准备的输入

符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。

Agent 与运行环境

使用支持 Skill 且能访问文件的 Agent。随包 Python 辅助工具需要 Python 3;提供数据前先查看样例结构。

需确认的适用边界

这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

04

安装与开始使用

将指令复制给 Codex 或 Claude Code,让助手从原始仓库下载固定提交,安装完整文件并检查所需依赖。

  1. 打开能访问本机文件和终端的 Codex 或 Claude Code。
  2. 复制下方指令发给正在使用的应用,由助手选择该应用的安装目录。
  3. 查看返回的安装路径和文件检查结果;需要时新建会话,再要求助手使用已安装的 Skill。
请在我当前使用的应用中安装 customer-success-manager,直接执行文件安装,不要只解释步骤。 原始仓库:https://github.com/alirezarezvani/claude-skills.git 固定提交:6d2f02ea077eead1bee5411a31bcc6db5a11a70c Skill 路径:business-growth/skills/customer-success-manager 1. 将这个版本下载到新目录。执行随包脚本前,先阅读 SKILL.md 和安装参考文件,不替换成其他作者的包。 2. Codex 安装到 ~/.agents/skills/customer-success-manager,Claude Code 安装到 ~/.claude/skills/customer-success-manager,只安装到我正在使用的应用。安装完整 Skill 文件夹,保留 scripts、references、assets 和随包声明;将仓库根目录许可证一并保留。先检查所有目标目录;已有安装时,说明差异后再决定是否替换。 3. 比较来源和安装目录的文件清单、文件哈希,检查文档要求的运行时、依赖及外部连接。只配置此 Skill 所需的本地依赖,适用时使用隔离环境;账号登录由我在本地完成,不把凭据贴进聊天。 4. 返回来源提交、实际安装路径、文件检查结果及尚未完成的运行环境配置,说明如何调用 customer-success-manager。文件复制与应用发现分别检查,需要时新建会话。不要执行生产任务,也不要把安装完成说成已确认业务效果。
05

原始 Skill.md

以下为已核对版本未经改写的 SKILL.md。安装完整包才能保留引用的脚本、素材和指引。下方启动提示词为 EcomAgentTools 编写的示例。

---
name: "customer-success-manager"
description: Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analyzing customer accounts, reviewing retention metrics, scoring at-risk customers, or when the user mentions churn, customer health scores, upsell opportunities, expansion revenue, retention analysis, or customer analytics. Runs three Python CLI tools to produce deterministic health scores, churn risk tiers, and prioritized expansion recommendations across Enterprise, Mid-Market, and SMB segments.
license: MIT
metadata:
  version: 1.0.0
  author: Alireza Rezvani
  category: business-growth
  domain: customer-success
  updated: 2026-02-06
  python-tools: health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py
  tech-stack: customer-success, saas-metrics, health-scoring
---

# 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](#input-requirements)
- [Output Formats](#output-formats)
- [How to Use](#how-to-use)
- [Scripts](#scripts)
- [Reference Guides](#reference-guides)
- [Templates](#templates)
- [Best Practices](#best-practices)
- [Limitations](#limitations)

---

## 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

```bash
# 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

```bash
# 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:**
| Dimension | Weight | Metrics |
|-----------|--------|---------|
| Usage | 30% | Login frequency, feature adoption, DAU/MAU ratio |
| Engagement | 25% | Support ticket volume, meeting attendance, NPS/CSAT |
| Support | 20% | Open tickets, escalation rate, avg resolution time |
| Relationship | 25% | 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:**
```bash
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 Category | Weight | Indicators |
|----------------|--------|------------|
| Usage Decline | 30% | Login trend, feature adoption change, DAU/MAU change |
| Engagement Drop | 25% | Meeting cancellations, response time, NPS change |
| Support Issues | 20% | Open escalations, unresolved critical, satisfaction trend |
| Relationship Signals | 15% | Champion left, sponsor change, competitor mentions |
| Commercial Factors | 10% | 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:**
```bash
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:**
```bash
python scripts/expansion_opportunity_scorer.py customer_data.json
python scripts/expansion_opportunity_scorer.py customer_data.json --format json
```

---

## Reference Guides

| Reference | Description |
|-----------|-------------|
| `references/health-scoring-framework.md` | Complete health scoring methodology, dimension definitions, weighting rationale, threshold calibration |
| `references/cs-playbooks.md` | Intervention playbooks for each risk tier, onboarding, renewal, expansion, and escalation procedures |
| `references/cs-metrics-benchmarks.md` | Industry benchmarks for NRR, GRR, churn rates, health scores, expansion rates by segment and industry |

---

## Templates

| Template | Purpose |
|----------|---------|
| `assets/qbr_template.md` | Quarterly Business Review presentation structure |
| `assets/success_plan_template.md` | Customer success plan with goals, milestones, and metrics |
| `assets/onboarding_checklist_template.md` | 90-day onboarding checklist with phase gates |
| `assets/executive_business_review_template.md` | Executive 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
06

开始使用

以下是主要功能的用例提示词,可以直接复制使用。

01

检查商家软件客户群的账号健康度

检查商家软件客户群的账号健康度 适用于:检查商家软件客户群的账号健康度。请准备:符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 customer-success-manager Skill。任务:检查商家软件客户群的账号健康度。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

需要替换的变量

[INPUT]
符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
02

排列需人工跟进的续费风险账号

排列需人工跟进的续费风险账号 适用于:排列需人工跟进的续费风险账号。请准备:符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 customer-success-manager Skill。任务:排列需人工跟进的续费风险账号。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

需要替换的变量

[INPUT]
符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
03

比较客户扩展机会与投入成本

比较客户扩展机会与投入成本 适用于:比较客户扩展机会与投入成本。请准备:符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。

查看 Prompt 和变量收起 Prompt 和变量
请使用已安装的 customer-success-manager Skill。任务:比较客户扩展机会与投入成本。输入:[INPUT]。限制:[CONSTRAINTS]。先检查缺失信息,再输出可审查的结果、依据、假设和下一步。这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

需要替换的变量

[INPUT]
符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。
[CONSTRAINTS]
任务范围、允许的操作、输出格式和审核要求。
07

实际使用案例:为运营软件续约核对席位、采用情况和支持问题

家居用品电商团队准备与运营软件供应商开季度回顾会,提供账号使用、合同和支持记录,希望判断先补培训、调整席位还是增加采购。所用账号资料为模拟数据。

使用步骤与 Prompt

  1. 准备下方案例输入资料,保留商品、政策和经营记录中的金额、单位及时间口径。
  2. 从软件账号导出记录中检查采用情况、闲置席位和支持风险,把扩展金额解释为新增采购成本,再准备续约讨论与团队改进计划。
  3. 提交下方完整 Prompt,查看右侧主要产物;需要交接给同事时,下载包含全部交付文件的压缩包。

案例输入资料:business-inputs.zip

Use the customer-success-manager Skill.

Our ecommerce operations team is preparing a quarterly review and renewal discussion for its shared order, stock and customer-support software. Use the supplied account export to assess adoption, unused capacity, support risk and renewal options. Run the Skill’s health, churn-risk and expansion analysis, but interpret ARR as our annual vendor bill and any expansion amount as additional software spend, never store revenue. Recommend onboarding actions, seat right-sizing or expansion only where usage supports it, and prepare a vendor meeting agenda with owners and success checks. We have no measured labor-saving or sales-uplift data, so do not invent an ROI.

The attached business materials are:
- inputs/business-brief.json
- inputs/software-account.json

Deliver a complete result.md report that the operations team can read, plus any finished files needed for this task. Keep supporting calculations and evidence with the deliverables. Write the report in English; use the requested target language for customer-facing copy. The business datasets are fictional examples unless the brief explicitly names a live public website.

运行结果

下方直接展示本次 Prompt 产生的主要文件,保留实际输出语言。

Merchant-side software review: improve adoption before buying more

Keep the existing 100-seat scope while checking the five inactive seats and resolving the export issue. The original Skill's three tools report health 86.2/100 (green), churn risk 0.6/100 (low) and seven expansion suggestions. The expansion output is a vendor upsell model; it is not evidence that the store needs those purchases or would earn more revenue.

What the account actually shows

MeasureSupplied or calculated valueMerchant implication
Annual vendor subscription charge$120,000Software expense, not merchandise revenue
Active / licensed seats95 / 100 = 95%Five seats currently inactive; inspect intended use before cutting or adding
Prior seat utilization85%Ten percentage-point increase; not a measured labor saving
Adopted modules3 of 5 = 60%Identify why integrations and advanced reporting are not used
Module usageCore 85%, analytics 60%, API 40%Focus onboarding on a defined business workflow
Support2 open tickets, 18-hour average resolution, 5% escalation rateThese are snapshots; compare with the actual contractual SLA
Export issueFormatting workaround; supplied ETA Nov 10Obtain a reproducible example and verify the eventual fix
Contract endDec 31, 2027421 days from this run; no artificial immediate-renewal pressure

Health dimensions are usage 91.6 (30%), engagement 82.0 (25%), support 78.5 (20%) and relationship 90.1 (25%). Their weighted sum is approximately 86.2. The prior overall score is 67; this is a model-score improvement, not measured commercial value. The field called nps_score is an 8/10 response under this Skill's definition, not an aggregate NPS of +8.

Evaluate the expansion suggestions as possible costs

The scorer estimates $80,000 for a tier upgrade, $30,000 for 25 more seats, $21,600 for advanced reporting, $14,400 for integrations and $48,000 for each of three departments. Its sum is $290,000. These are model-generated potential vendor charges using generic assumptions, not a quote or a justified budget. Options can overlap and must not be blindly added to the existing bill.

At the current average $1,200 annual bill per licensed seat, five inactive seats represent a nominal $6,000 allocation. This is not guaranteed removable spend: minimum commitments, blended modules and contract terms may prevent proportional savings. Verify entitlements and the hiring/coverage plan before right-sizing. A 95% snapshot alone does not justify buying 25 extra seats.

Thirty-day action plan

OwnerActionDue / success check
Workspace administratorReview five inactive seats with team leadsWithin 7 days; each seat has a named business purpose or a removal proposal
Operations process ownerChoose one order/stock reporting workflow and document the current stepsWithin 7 days; baseline completion time and error count measured before training
Vendor support ownerConfirm the export defect scope and Nov 10 targetOn the target date, reproduce the workflow and compare the exported fields with the agreed format
Team training ownerRun focused onboarding for the selected workflow using existing entitlementsWithin 14 days; users complete the task and unresolved issues are logged
Finance/procurement ownerObtain current tier, module and seat pricing with minimumsWithin 30 days; separate optional expansion from existing contractual spend
Operations sponsorReview utilization and workflow evidenceDay 30; retain, right-size or pilot a module based on evidence

Do not promise the vendor's roadmap dates: no confirmed release commitments are supplied. The named export ETA is an input to verify, not a new guarantee created by this report.

Vendor meeting agenda

Five minutes: agree on the merchant's order, stock and support tasks and the current $120,000 annual cost. Ten minutes: review active seats, inactive-seat intent and existing module entitlements. Ten minutes: reproduce the export issue and agree on an acceptance check. Ten minutes: discuss training and a bounded workflow pilot. Five minutes: request written renewal and optional-expansion pricing with an owner and follow-up date.

No labor-hours saved, order uplift or ROI was supplied, so the QBR deliberately contains no invented return-on-investment claim. The three original JSON outputs are retained for traceability, with their vendor-oriented revenue labels interpreted as possible merchant expense in this report. No account plan, seat count or subscription was changed.

案例中的商家经营资料为模拟数据;涉及网站检查时,报告中的页面观察来自所列公开网址。

08

风险与使用注意事项

已知限制

这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

证据与复核

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。

采用结果前

使用获授权输入,不把密钥贴入提示词。采用前检查面向客户的声明、计算、代码改动及任何拟议的外部操作。

常见问题

它能做什么,有什么优势?

根据本地 JSON 数据评估 SaaS 客户健康度、流失风险和扩展机会。三个标准库 Python 工具按客户分层输出可重复的评分与建议。

如何安装和开始使用?

按实际 Agent 选择方式,安装完整包,不要只复制页面中的 SKILL.md。 符合样例结构的账号使用、互动、客服、关系、收入、续费和扩展字段。 开启新 Agent 会话,明确要求使用 customer-success-manager。先用小型样本尝试下方一个场景,并检查输出。

适合哪些使用场景?

检查商家软件客户群的账号健康度;排列需人工跟进的续费风险账号;比较客户扩展机会与投入成本

使用前需要了解哪些限制?

这是规则式 SaaS 账号模型,不是机器学习预测或消费者复购预测;不含 CRM 连接或自动外联。

本页核对了什么?

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。

暂无评论。

发表评论

请先为每一项打分,再分享你的真实使用体验。

任务有效性
安装与使用难度
稳定性与边界
文档清晰度
首次获得有效结果
作者 / 维护者

Alireza Rezvani

核对源码及随包文件:GitHub 6d2f02ea077e。本次为静态审查,不代表已完成安装运行或业务效果测试。