account-health
Skill23 starsChanged 2 months agoMITView on GitHub
Score a customer's health, start the renewal motion, and flag churn or expansion early. Trigger when the user asks "how's this account doing", "health check", "are we at risk of churn", "is this account ready to expand", or before a renewal or QBR.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- microsoft/aibast-agents-librarytheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- microsoft/aibast-agents-library★ 8same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- calendar-followupSkill
- churn-saveSkill
- cold-outreachSkill
- content-repurposeSkill
- event-to-pipelineSkill
- example-skillSkill
- expansion-signalSkill
- follow-upSkill
- inbox-digestSkill
- lead-qualifySkill
- marketing-feedbackSkill
- meeting-prepSkill
- onboarding-handoffSkill
- product-signalSkill
- qbr-prepSkill
- retention-feedbackSkill
- status-updateSkill
- support-signalSkill
- triageSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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 26
Don't tag every quiet week as a risk — flag it when usage, the champion, or the value story is actually slipping.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Account Health
The right-side operating skill — the equivalent of lead-qualify for the post-sale half of the bowtie. Where lead-qualify scores a deal's fit, this scores a customer's health: is value landing, is the renewal safe, is there room to grow? It reads the account book and writes the signal back into the same loop the field uses.
From ops/customers.md (or a single account the user names) and any recent post-sale notes:
- Read the adoption signal. Against the account's value hypothesis — is the customer getting what they bought this to do? Usage trend, workflows live vs. in scope, who's actually using it.
- Score it green / amber / red:
- 🟢 Green — using it as intended, champion engaged, value visible.
- 🟡 Amber — one warning sign (a stalled workflow, a quiet month, a single thread).
- 🔴 Red — value not landing: usage down, champion gone quiet, or single-threaded after a change.
- Watch the renewal clock. The renewal motion starts at day 60, not day 85. If the renewal date is inside 60 days, say so and start the motion now — don't wait for the contract to surface it.
- Flag churn early-warnings. Name the leading indicators, not the lagging one: usage trending down, the champion gone quiet, a single-threaded account after a reorg. These precede a lost renewal; the cancellation is just when it becomes visible. When one fires, hand the recovery to
churn-save. - Spot expansion-readiness. A healthy account using the core well, or a second team asking unprompted, is an expansion signal — not a renewal risk. Work it with
expansion-signal. Write the signal to the loop and update the book. Log a tagged line in
ops/feedback-log.md— the same single home marketing and product read:RETENTION-RISK: [account] — [the adoption/churn signal] → [CS or product action]EXPANSION-SIGNAL: [account] — [the readiness signal] → hand to sales with CS context
Then update the account's stage, key signal, and next step in
ops/customers.md.
Don't tag every quiet week as a risk — flag it when usage, the champion, or the value story is actually slipping. A book full of false alarms gets ignored.
Depth
- quick: the green/amber/red call + the one signal driving it.
- standard: the full health read, renewal-clock check, and tagged loop line.
- deep: + the churn early-warning list, the expansion read, and the day-by-day renewal-motion timing.
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.

