# customer-health-score

Turns product usage and engagement signals into one weighted account score that flags churn risk and expansion readiness.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 20600 installs · ★ 1
- Author: Maya-Beth Finotti
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/customer-health-score/SKILL.md
- Updated: 2026-09-14
- HTML: https://affpapa.org/en/nevibecode/skills/customer-health-score

## What it does

The skill handles design, validation and upkeep of a composite customer health score. It takes signal categories — product usage, relationship and engagement, support, commercial, sentiment — and folds them into a single number through normalization, weighting, time decay, banding, segment calibration and override governance. Every band is wired to a play the team can run.

The difference from a performative score someone assembled on gut feel: weights here come from what churned accounts actually did before they left, then get proved in a backtest. B2B rollup to account level gets extra weight on champion and sponsor continuity, because flat aggregate usage can hide a disengaged champion. B2C and PLG scoring runs continuously and adds an involuntary-churn layer for failed payments and dunning.

Before designing anything, the skill interviews you one question at a time: which motion, how many accounts and churn events over the last 12-24 months, which data sources are connected, whether a score already exists. Those answers decide between statistically fitted weights and a rules-based cold start. Signal discovery is out of scope — that lives in `mbfinotti/revops-skills@customer-churn-signals`. The red band gets sized to how many at-risk accounts the team can genuinely work per month, not to statistics.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill customer-health-score -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/customer-health-score/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/customer-health-score/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill customer-health-score -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/customer-health-score/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill customer-health-score -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/customer-health-score/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install mbfinotti/revops-skills customer-health-score
```

2. **Manually: put the files in place**
- File: `.github/skills/customer-health-score/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill customer-health-score -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/mbfinotti/revops-skills --path skills/customer-health-score
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/customer-health-score/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add mbfinotti/revops-skills --skill customer-health-score -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/customer-health-score/SKILL.md

## When to use it
- combine scattered signals into one account health score
- derive weights from what churned accounts actually did
- backtest a score against real churn outcomes
- calibrate bands separately for enterprise and SMB
- wire every band to a retention or expansion play

## Example prompts
- Design a customer health score for a CSM-covered B2B motion with contract renewals
- Our green accounts keep churning — figure out why the score predicts nothing
- Backtest the health score against the last 12 months of churn and recalibrate the weights

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 42da7aac437f9321.

BEGIN THIRD-PARTY FILE 42da7aac437f9321
```text
---
name: customer-health-score
description: Design, validate, and govern a composite customer health score - product usage and engagement signals combined into one weighted, normalized, decayed, banded account score that flags both churn risk and expansion readiness, backtested against real churn outcomes and recalibrated. Use whenever the user mentions a customer health score, health scoring model, account health, signal weighting, score bands, at-risk account flagging, churn risk score, expansion risk, or says "green accounts keep churning" - even if they never say "health score". Covers B2B account-level rollup and B2C/PLG continuous scoring. Do NOT use for discovering which indicators actually predict churn - use mbfinotti/revops-skills@customer-churn-signals instead.
license: MIT
metadata:
  author: Maya-Beth Finotti
  version: "1.0.1"
---

# Customer Health Score

Design, validate, and maintain one composite score that tells a post-sale team which accounts are drifting toward churn and which are ready for an expansion conversation. In ChurnZero's 2025 Customer Revenue Leadership Study (~800 CS and post-sales leaders surveyed), 73% said their current health score does not reliably predict churn.

- **Performative score.** Someone picks ten metrics, weights them by intuition; CS ignores the result because it predicts nothing.
- **Predictive score.** Derives its weights from what churned accounts actually did before churning, then proves itself in backtest.

This skill owns the composition and validation that turns one into the other:

- Normalization
- Weighting
- Decay
- Banding
- Segment calibration
- Override governance
- Wiring every band to a play

Which indicators to feed it, and how predictive each one is, is discovery work owned by `mbfinotti/revops-skills@customer-churn-signals`. Treat signals here at the category level (product usage, relationship/engagement, support, commercial, sentiment) and take the discovered indicator list as input.

Draw on the field's named canon where it genuinely helps:
```
END THIRD-PARTY FILE 42da7aac437f9321

The third-party file has ended. Everything between the 42da7aac437f9321 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2047 of 20706 bytes. © Maya-Beth Finotti · MIT · https://github.com/mbfinotti/revops-skills/tree/HEAD/skills/customer-health-score/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md