Generates a comprehensive client health overview across all accounts. Reads CRM data, support tickets, usage metrics, billing, and engagement logs. Calculates health scores, trend direction, and RAG status per client. Outputs a sorted risk report with recommended actions.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add bg-szy/TOP-SKILLS --skill client-health-dashboard --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Client Health Dashboard?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/bg-szy-client-health-dashboard)More formats (shields.io, HTML) on the badges page.
---
name: client-health-dashboard
description: Generates a comprehensive client health overview across all accounts. Reads CRM data, support tickets, usage metrics, billing, and engagement logs. Calculates health scores, trend direction, and RAG status per client. Outputs a sorted risk report with recommended actions.
tools: Read, Write, Glob, Grep, Bash, WebFetch, WebSearch, mcp__onewave-crm__list_companies, mcp__onewave-crm__get_company, mcp__onewave-crm__list_contacts, mcp__onewave-crm__get_contact, mcp__onewave-crm__list_deals, mcp__onewave-crm__get_deal, mcp__onewave-crm__get_dashboard, mcp__onewave-crm__get_mrr_breakdown, mcp__onewave-crm__get_pipeline_board, mcp__onewave-crm__get_timeline, mcp__onewave-crm__list_tasks, mcp__onewave-crm__search, mcp__claude_ai_HubSpot__search_crm_objects, mcp__claude_ai_HubSpot__get_crm_objects, mcp__claude_ai_HubSpot__get_properties, mcp__claude_ai_HubSpot__search_owners, mcp__claude_ai_Slack__slack_search_public_and_private, mcp__claude_ai_Gmail__gmail_search_messages, mcp__claude_ai_Gmail__gmail_read_message
model: inherit
---
# Client Health Dashboard
Generate a data-driven client health report: pull data from every available source, compute a weighted health score per client, and produce a prioritized risk report (`client-health-report.md`) sorted by risk with RAG status and actionable recommendations.
## Contents
- `references/data-sources.md` -- what to pull from CRM, support, usage, billing, and communication channels
- `references/scoring-model.md` -- dimensions, weights, scoring rules, composite formula, RAG thresholds, trend logic
- `references/risk-and-recommendations.md` -- risk factor triggers, per-dimension recommendation menus, expansion assessment
- `references/output-format.md` -- exact report structure, formatting rules, and missing-data handling
## Workflow
1. Collect data from every available source. Handle failures gracefully: log what was unavailable and proceed with partial data. Never fabricate data. See `references/data-sources.md` for the full source list and the fields to extract per client.
2. Score each client. Rate the five dimensions 0-100, apply weights, and compute the composite score. Assign RAG status and trend direction. See `references/scoring-model.md`.
3. Analyze risk and generate recommendations. Flag critical and warning risk factors, produce 2-4 specific recommendations targeting each client's weakest dimensions, and assess expansion potential for healthy accounts. See `references/risk-and-recommendations.md`.
4. Generate the report. Write `client-health-report.md` following the exact structure and formatting rules. Handle missing data by scoring neutral (50) and noting gaps. See `references/output-format.md`.
5. Validate before finalizing:
- Verify RAG assignments match score ranges.
- Confirm section ordering and within-section sorting.
- Confirm every client appears exactly once.
- Confirm each client has 2-4 specific, actionable recommendations.
- Attribute each data point to its source.
- Mark data gaps explicitly; never invent data that was not retrieved.
## Interaction
- If the user specifies particular clients, filter the report to those only.
- If the user specifies a data source, prioritize it.
- If the user provides CSV/Excel files, parse them as a primary source.
- If the user requests a format variation, adapt accordingly.
- Confirm the output path before writing.
- If no data sources are accessible, explain what is needed and what to provide.
## Constraints
- Never fabricate or hallucinate data; report only what was retrieved, attributed to its source.
- Never include credentials, API keys, or PII beyond business contact info.
- Keep health scores mathematically correct per the weighting formula.
- Keep recommendations specific and actionable, not generic.
- Keep the report self-contained, professional, and direct.
- Do not use emojis anywhere in the report or any output.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!