customer-success SKILL.md skillA
customer-success from varunk130/ai-gtm-skill-library is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add varunk130/ai-gtm-skill-library/customer-success@git:20260522.2e90392Pins git:20260522.2e90392 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- varunk130/ai-gtm-skill-library
- Path
revops-skills/customer-success/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260522.2e90392, committed May 22, 2026
- First version recorded
- May 16, 2026
- Size
- 5,683 bytes
- Repository stars
- 7
- License
- MIT
Customer Success operating system - segmented coverage model, health scoring, risk playbooks, value reviews, and expansion motions tied to net revenue retention. Use when: customer success strategy, CS operating model, health score, risk playbook, EBR / QBR design, churn prevention, net retention, NRR, GRR, success plan, value realization, customer journey post-sale.
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 (THRIVE Framework) Design a Customer Success operating system that turns post-sale into a predictable revenue engine. The skill enforces explicit coverage tiering, a health score that actually predicts churn, named risk playbooks, value reviews that earn renewals, and expansion motions that move NRR - instead of a generic "we should do QBRs" plan. ## Core Principle **Customer Success is a *coverage and signal* problem, not a relationship problem.** Most CS teams over-invest in friendly check-ins with healthy accounts and under-invest in early risk signals and value proof. THRIVE forces tiered coverage, leading indicators, and renewal-defensible value evidence. ## The THRIVE Framework | Letter | Stage | The Question | |--------|-------|--------------| | **T** | Tier the Book | Which accounts get high-touch, tech-touch, or pooled coverage - and why? | | **H** | Health Scoring | What 4-6 leading signals predict churn 90+ days out? | | **R** | Risk Playbooks | When a signal trips, what named play runs in what timeframe? | | **I** | Insight Reviews | What evidence of value gets shown at each review cadence? | …
Read the whole file at its exact version.
How to install
mdr add varunk130/ai-gtm-skill-library/customer-success@sha256:d0a102fafee34016The line at the top of this page pins the label git:20260522.2e90392, 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_7bmq2djxex5ynyis)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 16, 2026 and May 22, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260522.2e90392 latest | 2026-05-22 | 2e90392 | 5,683 B | A | view · diff |
| git:20260516.4225f52 | 2026-05-16 | 4225f52 | 5,723 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 (5683 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
varunk130/ai-gtm-skill-library · 7 stars · license MIT · pushed 2026-11-01 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_7bmq2djxex5ynyis GET https://markdownregistry.com/api/v1/resolve?ref=varunk130/ai-gtm-skill-library/customer-success GET https://markdownregistry.com/api/v1/blob/d0a102fafee34016a385b153f63224f7b4aa3933d0a87832ba2af83e82128c0b
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.
More from varunk130/ai-gtm-skill-library
Every file in varunk130/ai-gtm-skill-library