Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Customer success across onboarding, adoption, retention, and expansion.
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills customer-success-manager --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/sales-success/customer-success-manager .claude/skills/customer-success-manager && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .claude/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-managerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills customer-success-manager --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/sales-success/customer-success-manager .agents/skills/customer-success-manager && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .agents/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills customer-success-manager --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/sales-success/customer-success-manager .cursor/skills/customer-success-manager && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .cursor/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path sales-success/customer-success-manager--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills customer-success-manager --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/sales-success/customer-success-manager .gemini/skills/customer-success-manager && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .gemini/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills customer-success-managerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/sales-success/customer-success-manager .github/skills/customer-success-manager && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .github/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill customer-success-manager -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills customer-success-manager --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/sales-success/customer-success-manager .opencode/skills/customer-success-manager && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "customer-success-manager" agent skill from https://github.com/borghei/Claude-Skills/tree/main/sales-success/customer-success-manager into .opencode/skills/customer-success-manager/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "customer-success-manager", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
customer-success-managerCustomer success across onboarding, adoption, retention, and expansion.
Customer Success Manager is an agent skill from borghei/Claude-Skills. Customer success across onboarding, adoption, retention, and expansion. Use when designing onboarding playbooks, calculating health scores, building QBR decks, planning renewal strategies, or identifying expansion opportunities.
Its SKILL.md is about 3.7k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/churn_predictor.py`, `scripts/health_scorer.py` and `scripts/qbr_generator.py`).
It sits in Sales & Support, covering Customer success. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
7 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
pythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Customer Success Manager loads about 3.7k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 1,452 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 1,452 words, ~3,673 tokens.
.claude/skills/customer-success-manager/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.The agent operates as an expert customer success manager, driving retention and growth through structured onboarding, health monitoring, risk mitigation, expansion identification, and customer advocacy programs.
Before generating, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
ONBOARDING (0-30d) -> ADOPTION (30-90d) -> VALUE REALIZATION (90d+) -> EXPANSION -> ADVOCACY# Customer Onboarding: [Customer Name]
## Pre-Kickoff
- [ ] Account setup complete
- [ ] Key contacts identified
- [ ] Success criteria defined
- [ ] Implementation timeline agreed
- [ ] Resources allocated
## Week 1: Kickoff
- [ ] Kickoff meeting conducted
- [ ] Goals and milestones confirmed
- [ ] Training schedule set
- [ ] Communication channels established
## Week 2-4: Implementation
- [ ] Technical setup complete
- [ ] Data migration (if applicable)
- [ ] Integrations configured
- [ ] Initial users trained
## Week 4-8: Adoption
- [ ] Power users identified
- [ ] Workflow adoption started
- [ ] Early wins documented
- [ ] Feedback collected
## Handoff (Week 8)
- [ ] Onboarding review meeting
- [ ] Success metrics baseline
- [ ] Ongoing cadence established
- [ ] Escalation paths clearHEALTH SCORE = (Product x 40%) + (Relationship x 30%) + (Outcomes x 30%)
PRODUCT (40%)
Login frequency: [0-10]
Feature adoption: [0-10]
Active users vs. licensed: [0-10]
Support tickets (inverse): [0-10]
RELATIONSHIP (30%)
Executive engagement: [0-10]
Meeting attendance: [0-10]
NPS score: [0-10]
Response time: [0-10]
OUTCOMES (30%)
Goals achieved: [0-10]
ROI demonstrated: [0-10]
Business impact: [0-10]
THRESHOLDS
80-100: Healthy (Green) -- maintain cadence, pursue expansion
60-79: Attention (Yellow) -- increase touchpoints, address gaps
0-59: At Risk (Red) -- activate risk playbook immediatelyCustomer: Acme Corp
Product: (9 + 8 + 9 + 9) / 4 = 8.75 -> weighted: 8.75 x 0.40 = 3.50
Relationship: (8 + 7 + 9 + 8) / 4 = 8.00 -> weighted: 8.00 x 0.30 = 2.40
Outcomes: (8 + 9 + 8) / 3 = 8.33 -> weighted: 8.33 x 0.30 = 2.50
Total: (3.50 + 2.40 + 2.50) x 10 = 84 -> GreenLow Engagement:
Low Adoption:
Executive Change:
Competitor Evaluation:
| Signal | Score | Recommended Action |
|---|---|---|
| High adoption (>80% licensed seats active) | +3 | Explore user expansion |
| New department expressing interest | +3 | Schedule discovery call |
| Feature requests for premium tier | +2 | Position upgrade path |
| Executive engagement increasing | +2 | Propose strategic review |
| Contract renewal within 90 days | +2 | Bundle expansion into renewal |
# Quarterly Business Review: [Customer Name]
## Partnership Summary
- Customer since: [Date]
- Current ARR: $[X]
- Users: [X] active / [Y] licensed
## Quarter in Review
### Achievements
- [Achievement 1 with metric]
- [Achievement 2 with metric]
### Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric] | [Target] | [Actual] | up/down/flat |
## Value Delivered
- Time saved: [X] hours
- Cost reduction: $[Y]
- Other impact: [Description]
## Next Quarter Goals
1. [Goal 1 with success metric]
2. [Goal 2 with success metric]# Health score calculator
python scripts/health_scorer.py --data customers.csv
# QBR generator
python scripts/qbr_generator.py --data customers.csv --quarter Q4-2026
# Churn risk predictor
python scripts/churn_predictor.py --data customers.csv --horizon 90| Problem | Root Cause | Resolution |
|---|---|---|
| Health scores not predicting churn | Model weights are stale or too generic | Recalibrate weights quarterly by comparing predicted scores against actual renewal outcomes. Segment scoring by customer tier, lifecycle stage, and use case. |
| Onboarding stalls at Week 2-4 | Technical blockers or lack of internal champion | Escalate to implementation team within 48 hours. Schedule a joint troubleshooting call. If champion is absent, request executive sponsor intervention. |
| NPS scores dropping across portfolio | Product issues, unresolved support backlog, or relationship decay | Analyze NPS verbatims for common themes. Prioritize red accounts for immediate outreach. Coordinate with Product on systemic issues. |
| Expansion conversations rejected | Timing misaligned with customer value realization | Only initiate expansion after demonstrating measurable ROI. Lead with value recap before any commercial discussion. Wait until health score is Green for 60+ days. |
| QBR attendance declining | Content not relevant; too much self-promotion, not enough customer value | Restructure QBR to lead with customer achievements and metrics. Limit product roadmap to items relevant to their use cases. Keep meetings under 45 minutes. |
| Executive sponsor changes | Organizational restructuring or M&A activity | Request introduction to new sponsor within 5 business days. Prepare a condensed value summary. Reset success metrics aligned to new sponsor's priorities. |
| Customer goes silent (no engagement) | De-prioritization, internal changes, or dissatisfaction not surfaced | Trigger the Low Engagement playbook immediately. Try multiple channels (email, phone, LinkedIn). Engage other known contacts. If no response in 14 days, escalate to your manager for executive outreach. |
| Renewal at risk with 60 days remaining | Late identification of churn signals; health score reviewed too infrequently | Increase monitoring cadence to weekly for all renewals within 90 days. Run churn risk scoring monthly. Pre-negotiate renewal terms 120 days before expiry. |
| Metric | Target | Measurement Method |
|---|---|---|
| Gross revenue retention (GRR) | 90%+ | Renewed ARR / Expiring ARR (excluding expansion) |
| Net revenue retention (NRR) | 110%+ | (Renewed + Expansion - Contraction) / Beginning ARR |
| Logo retention rate | 90%+ | Renewed customers / Total customers up for renewal |
| Customer health score accuracy | 80%+ predictive | Percentage of Green accounts that actually renewed |
| Time-to-value | Under 30 days | Days from contract signature to first measurable outcome |
| QBR completion rate | 100% for accounts above ARR threshold | QBRs delivered / QBRs due per quarter |
| NPS score | 50+ | Portfolio-wide NPS from quarterly surveys |
| Expansion revenue | 20%+ of book | Expansion ARR / Total managed ARR |
| Support escalation resolution | Under 48 hours | Average time from escalation to resolution |
In Scope:
Out of Scope:
Limitations:
| Integration | Direction | Purpose | Handoff Artifact |
|---|---|---|---|
| Account Executive | AE -> CSM | Post-sale handoff with deal context and success criteria | Handoff template with stakeholder map, success criteria, implementation timeline |
| Sales Engineer | SE -> CSM | Technical context from pre-sale evaluation | Technical discovery notes, POC results, integration requirements |
| Sales Operations | Bidirectional | Renewal forecasting, expansion pipeline tracking, churn reporting | Renewal forecast submissions, health score data exports |
| Product Team | CSM -> Product | Feature requests, usage feedback, product issues | Aggregated feedback reports, feature request rankings, bug reports |
| Support Team | Support -> CSM | Escalation routing, ticket trends, resolution tracking | Escalation alerts, monthly ticket summaries by account |
| Marketing | CSM -> Marketing | Customer stories, references, advocacy program | Case study candidates, reference availability, NPS promoters list |
| Finance | Bidirectional | Renewal pricing, credit requests, revenue forecasting | Renewal quotes, churn impact reports, expansion revenue tracking |
Workflow Handoff Protocol:
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 3 other files (scripts) in sales-success/customer-success-manager of borghei/Claude-Skills.
Open the folder on GitHubat commit 4a698e8
Customer Success Manager next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Customer Success Manager this skillborghei/Claude-Skills | 886 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Cs Health Scorecardmohitagw15856/pm-claude-skills | 1.4k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Youtube SearchZeroPointRepo/youtube-skills | 1k | 1 repos | ~1.8k | Automated safety check: Pass | MIT | |
| YtZeroPointRepo/youtube-skills | 1k | 1 repos | ~951 | Automated safety check: Pass | MIT | |
| Loki Modedavila7/claude-code-templates | 32k | 7 repos | ~7.1k | Automated safety check: Warn | MIT | |
| Account Researchexplorium-ai/gtm-skills | 175 | — | ~2.8k | Automated safety check: Pass | MIT |
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
ZeroPointRepo/youtube-skills
A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…
ZeroPointRepo/youtube-skills
A skill your agent uses when YouTube is relevant: pasted video links or IDs, @handles, quick video lookups, summaries, channel latest uploads, topic search, or any request involving YouTube content…
davila7/claude-code-templates
Multi-agent autonomous startup system for Claude Code. An agent skill from davila7/claude-code-templates.
explorium-ai/gtm-skills
Account research skill for Claude Code and Codex: generate a high-signal company intelligence brief including firmographics, technographics, funding history, hiring signals, business events, recent…
tech-leads-club/agent-skills
When the user wants to reduce churn, build expansion revenue, automate customer success, or optimize net revenue retention.
borghei/Claude-Skills
Test and evaluation harness for AI agents — scenario suites, deterministic replay, regression diffing, cost and latency budgets.
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Categories
Customer success across onboarding, adoption, retention, and expansion. Customer Success Manager is an agent skill from borghei/Claude-Skills. Customer success across onboarding, adoption, retention, and expansion.
Customer Success Manager fits situations like: designing onboarding playbooks; calculating health scores; building QBR decks; planning renewal strategies.
Run `npx skills add borghei/Claude-Skills --skill customer-success-manager -a claude-code`. Or copy the skill folder (sales-success/customer-success-manager in borghei/Claude-Skills) into .claude/skills/customer-success-manager in your project. Claude Code loads it when a task matches its description.
Run `npx skills add borghei/Claude-Skills --skill customer-success-manager -a codex`. Or copy the skill folder (sales-success/customer-success-manager in borghei/Claude-Skills) into .agents/skills/customer-success-manager in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill customer-success-manager -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/customer-success-manager, .gemini/skills/customer-success-manager, .github/skills/customer-success-manager and .opencode/skills/customer-success-manager in your project.
Going by SKILL.md and its folder, Customer Success Manager needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
Customer Success Manager is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.7k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Customer Success Manager: Cs Health Scorecard (mohitagw15856/pm-claude-skills, 1.4k stars), Youtube Search (ZeroPointRepo/youtube-skills, 1k stars), Yt (ZeroPointRepo/youtube-skills, 1k stars) and Loki Mode (davila7/claude-code-templates, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 886 GitHub stars. The repository holds 354 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.