customer-success-management SKILL.md skillA
customer-success-management from cbrock84/headcount is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cbrock84/headcount/customer-success-management@git:20260901.49e89d6Pins git:20260901.49e89d6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cbrock84/headcount
- Path
plugins/customer-experience/skills/customer-success-management/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260901.49e89d6, committed Sep 1, 2026
- First version recorded
- Sep 1, 2026
- Size
- 4,975 bytes
- Repository stars
- 2,543
- License
- MIT
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to design a customer success motion, decide who gets a named contact, work out why renewals surprise you, or fix a health score everyone ignores.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Customer success management This is the motion that keeps accounts, as distinct from diagnosing why they leave — for the churn analysis itself, see `revenue:retention`. The failure this discipline exists to prevent is finding out at renewal. ## Segment coverage before hiring anyone Coverage is a cost decision and it should be made explicitly rather than by whoever shouts. - **Named coverage** for accounts where the revenue justifies a person and the relationship is genuinely complex. Fewer accounts per person than instinct suggests — a manager with sixty accounts is running a queue, not a relationship. - **Pooled coverage** for the middle: a team owning a segment, working from signals rather than from a calendar. - **Programmatic coverage** for the long tail: in-product guidance, lifecycle messaging, and self-service. This is not a lesser tier, it is the only one that scales, and it usually deserves more investment than it gets. Assign by what the account needs, not only by what it pays. A large account that is live, stable and happy needs less than a small one mid-implementation. ## Build a health score that predicts something …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/customer-success-management@sha256:bb94e1adc60b0a78The line at the top of this page pins the label git:20260901.49e89d6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_astsk2bl2jicq45h)
8 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 1, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260901.49e89d6 latest | 2026-09-01 | 49e89d6 | 4,975 B | A | view · diff |
| git:20260901.9844f9d | 2026-09-01 | 9844f9d | 4,521 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4975 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
cbrock84/headcount · 2,543 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_astsk2bl2jicq45h GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/customer-success-management GET https://markdownregistry.com/api/v1/blob/bb94e1adc60b0a7830613e04f98fbaf17eafc334dc96af74191abd6c9d737d64
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.