Customer Success
Audits a periodic QBR or account health-review call transcript against a rubric covering value delivered, usage breadth, open issues, and forward alignment, or sweeps a CRM export for accounts overdue for a health review. Use when reviewing a QBR or ongoing health check-in, distinct from a renewal-risk-triggered or expansion-triggered conversation.
Install
$ agentstack add skill-zime-ai-zime-gtm-skills-customer-success ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-zime-ai-zime-gtm-skills-customer-success) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
GTM Customer Success Audit
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.
Modes
Dispatch on the input file's extension.
Transcript mode (.txt, .vtt, .json, .md)
claude "run customer-success on ./calls/acme-qbr.txt"Score against references/rubric.md. Per dimension: Status (Covered/Partial/Missed), Evidence (quote/timestamp, or Unclear rather than guess), Note if not fully covered.
Close with a one-line overall account read and the single most useful follow-up action. Run the reads-well-too check first.
CSV mode (.csv)
claude "run customer-success on ./exports/accounts.csv"Structural sweep only. Check whether accounts have a health-review field populated within a reasonable window (e.g. last 90 days) and flag those that don't, sorted by ARR descending.
Sample data
assets/sample-transcript.txt — synthetic QBR call.
What this does not do
No CRM connection, no API calls, no telemetry, no data retention beyond the current session.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: zime-ai
- Source: zime-ai/zime-gtm-skills
- License: MIT
- Homepage: https://zime.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.