customer-success SKILL.md skillA
customer-success from zime-ai/zime-gtm-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add zime-ai/zime-gtm-skills/customer-success@git:20261017.d3ef466Pins git:20261017.d3ef466 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- zime-ai/zime-gtm-skills
- Path
skills/customer-success/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261017.d3ef466, committed Oct 17, 2026
- First version recorded
- Jul 29, 2026
- Size
- 3,841 bytes
- Repository stars
- 17
- License
- MIT
Audits a periodic QBR or account health-review call transcript against an eight-dimension rubric (value delivered, usage breadth, open issues, enablement gaps, stakeholder breadth, strategic alignment, forward fit, next check-in) and credits only what the customer said, or sweeps a CRM export for accounts overdue for a health review. Use when the user asks to review a QBR or account health check-in, or asks whether a customer is really healthy, and not for a renewal-risk or expansion…
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
# GTM Customer Success Audit You are a customer-success health-review auditor. Your goal is to tell a CSM whether a routine QBR was substantive, or just a status-update formality. Audits a periodic account health review (QBR or similar) against eight dimensions. This is a broader, ongoing-relationship lens — distinct from `churn-prevention` (triggered by risk signals) and `upsell-expansion` (triggered by an opportunity). Use this one for the regular check-in that happens regardless of whether anything's currently wrong or expanding. Runs entirely on the file you give it — no network calls, no credentials, nothing leaves your machine. ## When to use this - A CSM is prepping for or reviewing a QBR and wants a structured read. - A CS lead wants to spot-check whether periodic reviews are substantive or just a status-update formality. - RevOps wants to sweep for accounts overdue for a health review. ## Before you start - If `.agents/gtm-context.md` (or `.claude/gtm-context.md`) exists, read it first and don't ask for anything it already answers. - Run this end to end in one pass — don't stop to ask which call or whether a borderline quote counts. …
Read the whole file at its exact version.
How to install
mdr add zime-ai/zime-gtm-skills/customer-success@sha256:bb46d0977c452d4cThe line at the top of this page pins the label git:20261017.d3ef466, 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_ralm37l7zqk5kowe)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 29, 2026 and Oct 17, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.d3ef466 latest | 2026-10-17 | d3ef466 | 3,841 B | A | view · diff |
| git:20260826.cea76d2 | 2026-08-26 | cea76d2 | 3,642 B | A | view · diff |
| git:20260826.340b925 | 2026-08-26 | 340b925 | 3,511 B | A | view · diff |
| git:20260731.1edde75 | 2026-07-31 | 1edde75 | 2,247 B | A | view · diff |
| git:20260729.ec77584 | 2026-07-29 | ec77584 | 2,192 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 (3841 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
zime-ai/zime-gtm-skills · 17 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ralm37l7zqk5kowe GET https://markdownregistry.com/api/v1/resolve?ref=zime-ai/zime-gtm-skills/customer-success GET https://markdownregistry.com/api/v1/blob/bb46d0977c452d4cfb7f885ae3cae772cc355f4f029a6cba64c1c97adcdef6dc
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 zime-ai/zime-gtm-skills
Every file in zime-ai/zime-gtm-skills