customer-health-score

$npx mdskill add Significant-Gravitas/skills-catalog/customer-health-score

Use this to define or apply an account health model.

SKILL.md

.github/skills/customer-health-scoreView on GitHub ↗
---
name: "customer-health-score"
description: "Build an auditable customer health score while keeping observed signals, judgement, and missing data separate."
triggers: ["customer health score", "account health", "health model", "red yellow green accounts", "customer score"]
version: "1"
---

# Customer health score

Use this to define or apply an account health model.

## Define before scoring

For every signal record its meaning, source, date range, refresh rate, good and
bad thresholds, weight, and missing-data rule. Keep adoption, outcome,
support, relationship, and commercial measures visible as separate parts.

## Score with evidence

For each account show the raw value, baseline or target, trend period, component
score, and source. Label manual judgement and explain it. Do not convert a
missing value to zero or healthy. Do not use logins as proof of value when the
customer's outcome calls for another measure.

## Return

Give the component view, overall result, confidence, missing data, material
change since the last period, and next check. Include the formula or rules so a
person can reproduce the result.

Never invent usage, sentiment, support history, goals, or contract facts. A
health score directs review; it does not prove renewal or churn.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.