cs-health-scorecard
$
npx mdskill add mohitagw15856/pm-claude-skills/cs-health-scorecardProduce a structured, data-driven health scorecard for a customer account — giving the CSM and leadership a clear view of renewal risk, expansion potential, and the actions needed to move the account in the right direction.
SKILL.md
.github/skills/cs-health-scorecardView on GitHub ↗
--- name: cs-health-scorecard description: "Build a customer health scorecard for a specific account. Use when asked to score account health, assess renewal risk, build a health dashboard, or evaluate an account's likelihood to renew or expand. Produces a structured health scorecard with a RAG status, dimension scores, key risks, and recommended actions." --- # Customer Health Scorecard Skill Produce a structured, data-driven health scorecard for a customer account — giving the CSM and leadership a clear view of renewal risk, expansion potential, and the actions needed to move the account in the right direction. ## Required Inputs Ask for these if not already provided: - **Account name** and tier (enterprise / mid-market / SMB) - **Contract value** (ARR) and **renewal date** - **Product usage data** — logins, DAU/MAU ratio, key feature adoption - **Support data** — open tickets, CSAT or NPS score, recent escalations - **Engagement data** — last QBR date, executive sponsor status, champion name - **Commercial data** — payment history, expansion conversations, seats used vs. licensed - **Any known risks or recent changes** at the account ## Scoring Framework Score each dimension 1–5. Weight as shown. Calculate weighted total out of 100. | Dimension | Weight | What to Score | |---|---|---| | **Product Adoption** | 30% | DAU/MAU ratio, breadth of features used, power users identified | | **Engagement** | 20% | QBR cadence, executive sponsor active, champion strength | | **Outcomes** | 20% | Customer hitting their stated goals / success metrics | | **Support Health** | 15% | Ticket volume trend, unresolved escalations, CSAT | | **Commercial** | 15% | On-time payments, seats utilised, expansion signals | **Score → RAG conversion:** - 80–100: Green (healthy, renew likely) - 60–79: Amber (at risk, needs attention) - 0–59: Red (high churn risk, escalate) ## Output Format --- # Customer Health Scorecard: [Account Name] **CSM:** [Name] | **Tier:** [Enterprise / Mid-Market / SMB] **ARR:** £/$/€[X] | **Renewal date:** [Date] | **Days to renewal:** [N] **Overall health:** [Green / Amber / Red] — [Score]/100 **Last updated:** [Date] --- ## Health Score Summary | Dimension | Score (1–5) | Weight | Weighted Score | Trend | |---|---|---|---|---| | Product Adoption | [1–5] | 30% | [X] | ↑ / → / ↓ | | Engagement | [1–5] | 20% | [X] | ↑ / → / ↓ | | Outcomes | [1–5] | 20% | [X] | ↑ / → / ↓ | | Support Health | [1–5] | 15% | [X] | ↑ / → / ↓ | | Commercial | [1–5] | 15% | [X] | ↑ / → / ↓ | | **Total** | — | 100% | **[X]/100** | | --- ## Dimension Detail ### Product Adoption — [Score]/5 - **DAU/MAU ratio:** [X]% (benchmark: >25% = healthy) - **Key features adopted:** [List features in use] - **Features not adopted:** [List unused high-value features] - **Power users identified:** [Yes / No — how many] - **Assessment:** [1–2 sentences on adoption health] ### Engagement — [Score]/5 - **Last QBR:** [Date] — [Outcome summary] - **Next QBR:** [Scheduled / Overdue] - **Executive sponsor:** [Active / Passive / Vacant] - **Champion:** [Name, role, strength: strong / moderate / weak] - **Assessment:** [1–2 sentences] ### Outcomes — [Score]/5 - **Customer's stated goals:** [List 2–3 goals from onboarding or last QBR] - **Progress against goals:** [On track / Partial / Off track] - **Evidence of value:** [Metric or quote that demonstrates ROI] - **Assessment:** [1–2 sentences] ### Support Health — [Score]/5 - **Open tickets:** [N] (priority breakdown: P1: X, P2: X, P3: X) - **CSAT / NPS:** [Score] (benchmark: >8 CSAT / >30 NPS = healthy) - **Unresolved escalations:** [Yes / No — details if yes] - **Ticket trend (last 90 days):** Increasing / Stable / Decreasing - **Assessment:** [1–2 sentences] ### Commercial — [Score]/5 - **Seats licensed:** [N] | **Seats active:** [N] ([X]% utilisation) - **Payment history:** [On time / Late — details] - **Expansion signals:** [Yes — describe / No] - **Downgrade or cancellation signals:** [Yes — describe / No] - **Assessment:** [1–2 sentences] --- ## Top Risks | Risk | Severity | Mitigation | |---|---|---| | [Risk description] | High / Medium / Low | [Specific action to mitigate] | --- ## Recommended Actions **Immediate (this week):** 1. [Action — owner — deadline] **This month:** 1. [Action — owner — deadline] **Before renewal:** 1. [Action — owner — deadline] --- ## Renewal Forecast | Scenario | Probability | ARR at risk | |---|---|---| | Full renewal at current ARR | [X]% | £/$/€0 | | Renewal with contraction | [X]% | £/$/€[X] | | Churn | [X]% | £/$/€[full ARR] | **Recommended renewal play:** [Expand / Hold / Save / Manage out] --- ## Quality Checks - [ ] Score is based on data, not gut feel — each dimension has evidence - [ ] Risks are specific (not "low engagement" — something like "executive sponsor left in March, no replacement identified") - [ ] Actions have owners and deadlines - [ ] Renewal probability is calibrated against pipeline reality - [ ] Trend arrows reflect direction of change vs. last scorecard, not just current state
More from mohitagw15856/pm-claude-skills
- 360-feedback-templateDesign a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
- ab-test-plannerDesign statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
- accessibility-auditGenerate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
- account-planBuild a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.
- aeo-optimizerOptimize an article for Answer Engine Optimization (AEO) — restructuring content so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Rewrites headings as questions, drops 50-80 word answer capsules, audits paragraph length, and flags trust signals. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines.
- ai-ethics-reviewConduct an ethical review of an AI or ML feature, model, or product. Use when asked to run an AI ethics review, assess AI risks, audit a model for bias, or produce an AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with prioritised mitigations.
- ai-product-canvasStructure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
- ambiguity-resolverStructure vague opportunities and unclear briefs into actionable one-page problem statements. Use when asked to clarify a vague brief, frame an undefined problem, make sense of an unclear opportunity, or when the user says 'we need to figure out what to do about X' or 'I've been asked to look into Y'. Produces a structured problem brief with reframed questions, scoped boundaries, and a minimum viable research plan.
- api-docs-writerWrite clear, developer-facing API documentation. Use when asked to document an API endpoint, write API reference docs, create a developer guide, or turn a raw spec/Postman collection into documentation. Produces endpoint documentation with descriptions, parameters, request/response examples, and error codes.
- api-versioning-strategyWrite an API versioning strategy document for a service or API platform. Use when asked to define versioning policy, plan API deprecation, classify breaking changes, or document version lifecycle. Produces a complete versioning strategy with breaking-change classification table, deprecation timeline, migration guide template, and client communication template.