← Back to Skills Marketplace
alirezarezvani

Customer Success Manager

by Alireza Rezvani · GitHub ↗ · v2.1.1 · MIT-0
cross-platform ⚠ suspicious
920
Downloads
0
Stars
4
Active Installs
3
Versions
Install in OpenClaw
/install customer-success-manager
Description
Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analy...
README (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:

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:

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:

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

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

Usage Guidance
This skill appears to implement what it claims (health scoring, churn prediction, expansion scoring) and includes relevant templates, but I found important inconsistencies and unknowns to check before installing or running on real customer data: 1) Fix the metadata quality issues: declare Python as a required binary and reconcile the version fields. 2) Investigate the mismatch between health score ranges and the risk-playbook ranges (health: 75–100 = Green/Healthy vs. playbook: 80–100 = Critical Risk). Confirm which numeric scale is authoritative so you don't trigger the wrong interventions. 3) Review the three Python scripts (health_score_calculator.py, churn_risk_analyzer.py, expansion_opportunity_scorer.py) yourself or have a developer inspect them for any network calls, environment-variable reads, or external process execution — SKILL.md asserts 'no API calls' but I could not verify the script internals from the provided content. 4) Test locally with the included sample_customer_data.json and review outputs (JSON mode) before integrating into any pipelines; run them in an isolated environment or container if you have sensitive data. If you want, I can (a) inspect the full contents of the three scripts for suspicious patterns, or (b) produce a short checklist/tests to run safely when first executing the skill.
Capability Analysis
Type: OpenClaw Skill Name: customer-success-manager Version: 2.1.1 The customer-success-manager skill bundle is a legitimate set of tools for SaaS customer analytics. It includes three Python scripts (churn_risk_analyzer.py, expansion_opportunity_scorer.py, and health_score_calculator.py) that process local JSON data using only standard libraries. The code contains no network requests, file system modifications, or access to sensitive environment variables. The instructions in SKILL.md are consistent with the provided scripts and do not contain any prompt injection attempts or malicious commands.
Capability Assessment
Purpose & Capability
Name, description, and included files line up: three Python tools plus templates for CSM workflows are appropriate for a Customer Success Manager skill. Minor inconsistencies: SKILL metadata in the registry claims version 2.1.1 while SKILL.md lists version 1.0.0; SKILL.md instructs using Python but the skill declares no required binary (python) in the registry. These are likely quality-control issues but worth fixing.
Instruction Scope
SKILL.md instructs running three Python CLI scripts on JSON input only (no network calls claimed). However, the references/playbooks contain a glaring contradiction: health_score_calculator classifies 75–100 as Green (healthy), while the playbook labels 'Critical Risk' as score 80–100 and prescribes immediate escalation. That conflict could cause dangerous, incorrect operational actions. Also, the provided listing did not include the full contents of the three scripts in the materials shown here, so I could not confirm they contain only standard-library logic or lack hidden endpoints—you should review those files for outbound network calls or environment-var access before running on sensitive data.
Install Mechanism
No install script is provided (instruction-only install), which minimizes supply-chain risk. Files are included in the skill bundle and are intended to be executed with an on-host Python interpreter; no external packages or downloaded archives are declared. The only missing declaration is that Python is required—SKILL.md notes Python 3.7+, but the registry's required-binaries list is empty.
Credentials
Skill requires no environment variables or credentials, which fits a local scoring tool. However, SKILL.md claims 'standard library only' but the scripts themselves were not shown in full here; verify the scripts do not read unexpected environment variables or access configuration paths. Also add a declared 'python' binary requirement to the metadata to remove ambiguity.
Persistence & Privilege
The skill is not always-enabled, and it does not request elevated persistence or system-wide configuration changes in the instructions. Nothing in SKILL.md asks the agent to modify other skills or global agent settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install customer-success-manager
  3. After installation, invoke the skill by name or use /customer-success-manager
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.1.1
v2.1.1: optimization, reference splits
v1.0.0
v2.1.1 release
v0.1.0
Initial release of Customer Success Manager skill with core analytics tools for SaaS customer success teams. - Multi-dimensional health scoring with usage, engagement, support, and relationship metrics; Red/Yellow/Green classification per segment. - Churn risk analysis using behavioral, support, relationship, and commercial signals with tiered intervention playbooks. - Expansion opportunity identification through adoption depth, whitespace mapping, and revenue impact estimation. - Configurable benchmarking for enterprise, mid-market, and SMB segments. - Trend analysis and executive-ready reporting/plan templates included. - No external dependencies; all Python CLI tools use standard library only.
Metadata
Slug customer-success-manager
Version 2.1.1
License MIT-0
All-time Installs 4
Active Installs 4
Total Versions 3
Frequently Asked Questions

What is Customer Success Manager?

Monitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success. Use when analy... It is an AI Agent Skill for Claude Code / OpenClaw, with 920 downloads so far.

How do I install Customer Success Manager?

Run "/install customer-success-manager" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Customer Success Manager free?

Yes, Customer Success Manager is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Customer Success Manager support?

Customer Success Manager is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Customer Success Manager?

It is built and maintained by Alireza Rezvani (@alirezarezvani); the current version is v2.1.1.

💬 Comments