health-score
Skill2 starsChanged 3 months agoMITView on GitHub
Use when the user says "audit our health score", "the score said green but they churned", "build a health score", "is our health score any good", "why is this account red", "backtest the score". AUDIT mode sorts inputs into measured, inferred and proxy and backtests against churned accounts 90 days before they left. BUILD mode designs 6 to 12 explainable signals scored against each account's own baseline, with a CSM override. Not for one account's renewal call (use renewal-risk) or book-level coverage (use coverage-model).
In this repository54 other files it gives its agents.
- account-contextSkill
- account-planSkill
- account-reviewSkill
- adoption-planSkill
- advocacy-askSkill
- book-reviewSkill
- book-triageSkill
- business-reviewSkill
- call-prepSkill
- call-recapSkill
- champion-lossSkill
- churn-postmortemSkill
- coachingSkill
- commitmentsSkill
- coverage-modelSkill
- csm-hiringSkill
- csm-rampSkill
- csql-motionSkill
- cs-scorecardSkill
- cs-startSkill
- customer-updateSkill
- day-planSkill
- email-criticSkill
- escalationSkill
- exec-conversationSkill
- expansion-caseSkill
- expansion-scanSkill
- handoffSkill
- hard-conversationSkill
- internal-askSkill
- invoice-chaseSkill
- mutual-action-planSkill
- nrr-narrativeSkill
- offboardingSkill
- onboarding-planSkill
- one-pagerSkill
- playbook-builderSkill
- portfolio-reviewSkill
- price-increaseSkill
- renewal-forecastSkill
- renewal-negotiationSkill
- renewal-riskSkill
- renewal-runwaySkill
- sales-handoffSkill
- save-planSkill
- stakeholder-mapSkill
- status-updateSkill
- survey-follow-upSkill
- team-rollupSkill
- usage-emailSkill
- value-ledgerSkill
- voice-of-customerSkill
- what-do-i-oweSkill
- skill-nameSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Ask for at most 3 things in ONE message, then proceed.
- Distinctive: line 31
Add a qualitative CSM override with a required reason and an expiry date.
- Distinctive: line 63
Averaging hides the disagreement: If the score says green and the CSM says red, one is wrong.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Health Score
Either an honest verdict on how far an existing score can be trusted, or a small explainable score the team can validate.
Start here
Pick the mode from the request. If unclear, ask one question: "Audit a score you have, or build one?" If an "Account context" block exists in the conversation, use its idea of healthy usage.
AUDIT needs: the inputs and weights (rough is fine), and, if possible, accounts that churned in the last year with their scores 90 days before. BUILD needs: the signals available, the product's usage rhythm, and what counts as retained.
Ask for at most 3 things in ONE message, then proceed. Missing data becomes a line under What I could not check.
Do this
AUDIT
- List each input, its weight, who chose it and when. Weights nobody can explain are a finding.
- Label every input
measured(the thing itself is counted),inferred(derived from something else) orproxy(a stand-in for value, like logins). Name what is absent: sponsor change, budget, competitor, a stale value metric. - Break the composite apart: by module, team and role. Averaging a growing signal with a dying one hides both.
- Backtest: for each churned account, what did the score say 90 days before? For red accounts a year ago, how many left? Report hits, misses and false alarms with counts.
- Give a trust level and what to fix first.
BUILD
- Pick 6 to 12 signals the team can explain in one sentence each, with at least one from the buyer side (sponsor contact, executive meeting), not usage only.
- Score each as change against the account's own baseline, not a portfolio average.
- Add a qualitative CSM override with a required reason and an expiry date.
- Specify what to validate: backtest on past outcomes (several dozen before trusting weights), check against expansion as well as churn, and recalibrate on a schedule.
Output
HEALTH SCORE: [AUDIT / BUILD] | [Company or score name]
Verdict: [Trust fully / trust as adoption only / do not act on it] because [one sentence]. Confidence: low / medium / high
AUDIT: Inputs
| Input | Weight | Class (measured/inferred/proxy) | Note |
Backtest: [n] churned, [n] scored green 90 days before, [n] red. False alarms: [n]
Hidden by averaging: [what]. Blind to: [what]
BUILD: Signals
| Signal | Measure | Baseline | Alert when | Why it matters |
Override: [rule]. Validate: [steps]
Fix first: [action] | Owner | By
What I could not check
- [gap]A filled example is in examples/sample.md. Match its length.
Rules
- Most scores were never backtested. A number built in a meeting and never checked against churners is a hypothesis; the 90 day lookback is the cheapest test there is.
- Trust needs outcomes. With a handful of churns, weights are noise; collect a few dozen outcomes (a common default, set your own) before tuning.
- Score the change, not the level. A 7 that was 8.5 last month says more than a 7, and a normal level for one deployment alarms another.
- Averaging hides the disagreement. If the score says green and the CSM says red, one is wrong; splitting the difference destroys the information. Find out which.
- Usage describes the user; the renewal is decided by the buyer. A usage-only score is an adoption score, so say so.
- Keep it explainable. Past roughly a dozen signals nobody can say why an account is red, and an unexplained red gets ignored.
- Validate against expansion too. A score that predicts churn but misses growth steers the team away from the accounts that matter most.
Related (only if installed)
renewal-risk for a single account call. coverage-model to set touch levels from the score. portfolio-review to spot reads that only echo the score.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

