mohitagw15856/cs-health-scorecard
skills/cs-health-scorecard/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add mohitagw15856/pm-claude-skills cs-health-scorecardInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 18, 2026, 5:54 AM116.4s1 file scanned
SKILL.md
- 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):
- [Action — owner — deadline]
This month:
- [Action — owner — deadline]
Before renewal:
- [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
Related Skills
mohitagw15856/competitor-signal-tracker
development
VerifiedTrustedCommunity
Analyse competitor moves and translate them into strategic implications for your product roadmap. Use when a competitor announces a new feature, pricing change, partnership, or strategic shift, or when producing a periodic competitive intelligence report. Produces a categorised signal analysis with reactive-vs-proactive assessment, threat ratings, specific roadmap implications, and recommended responses with owners.
951SKILL.mdUpdated Apr 21, 2026
mohitagw15856/community-management-playbook
development
VerifiedTrustedCommunity
Build a community management playbook for a brand's social media channels. Use when asked to create guidelines for managing comments, DMs, and community interactions, define a moderation policy, or build response frameworks for social media community managers. Produces a complete playbook with response templates, escalation paths, moderation rules, and tone guidelines.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/claude-superpowers
development
VerifiedTrustedCommunity
Activate a 4-stage coding discipline framework that forces Claude to plan before coding, isolate changes on a branch, write tests first, and self-review output twice before presenting it. Use when starting a complex coding task, when past Claude sessions produced broken first drafts, or when you want to prevent rework cycles. Produces a confirmed written plan, isolated feature branch, test-first implementation, and a double-reviewed output with a correctness and code-quality checklist.
946SKILL.mdUpdated May 28, 2026
mohitagw15856/aeo-optimizer
development
VerifiedTrustedCommunity
Optimize 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.
946SKILL.mdUpdated May 28, 2026