Health dimensions, score factors, and risk flags for customer accounts. Use when building or explaining a health score, when assessing account risk, or when pulling inputs from CRM, support, or product analytics.
View on GitHubplugins/CX/skills/health-scoring/SKILL.md
February 3, 2026
Select agents to install to:
npx add-skill https://github.com/propane-ai/kits/blob/main/plugins/CX/skills/health-scoring/SKILL.md -a claude-code --skill health-scoringInstallation paths:
.claude/skills/health-scoring/> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md). # Health Scoring Skill You are an expert at defining and interpreting customer health scores. You combine signals from ~~CRM~~, ~~support platform~~, and (when available) ~~product analytics~~ into a clear score plus factors and risk flags so CX can prioritize attention and interventions. ## Health Dimensions A health score can be built from one or more dimensions. Use what's available from connected tools: | Dimension | Description | Typical sources | |-----------|-------------|-----------------| | **Usage / engagement** | How often and how deeply the customer uses the product | ~~product analytics~~ (logins, feature adoption, sessions), ~~CRM~~ (usage fields) | | **Support load** | Volume and severity of tickets, escalations, reopen rate | ~~support platform~~ (ticket count, resolution time, escalations) | | **Satisfaction** | NPS, CSAT, survey scores, sentiment | ~~CRM~~ (NPS, survey), ~~support platform~~ (sentiment) | | **Commercial** | Contract status, payment, expansion signals | ~~CRM~~ (renewal date, payment status, expansion opportunities) | | **Relationship** | Executive engagement, QBR attendance, response to outreach | ~~CRM~~ (meetings, notes), ~~chat~~ (internal notes) | ### Dimension Weights When combining dimensions into a single score, typical weights (adjust per company): - **Usage / engagement**: Often 30–40% — strong predictor of retention - **Support load**: 20–30% — high or rising support = risk - **Satisfaction**: 20–30% — NPS/CSAT direct signal - **Commercial**: 10–20% — payment issues, renewal proximity - **Relationship**: 10–20% — disengagement = risk If only ~~CRM~~ and ~~support platform~~ are connected, use support load, satisfaction (if in CRM), and commercial as proxies; note "usage not available" if ~~product analytics~~ is not connected. ## Score Factors For each account, list the **factors** that drove t