Skip to main content
skill CX Codex

client-health-dashboard — Claude Code skill: use and install

client-health-dashboard builds a client health view from CRM and engagement data, then produces a risk-ranked report with scores, trends, and next actions.

MIT 276 installs ★ 440 updated 2026-10-20

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add OneWave-AI/claude-skills --skill client-health-dashboard -a claude-code
Open on GitHub

What client-health-dashboard does

This skill pulls account signals from CRM records, support tickets, usage metrics, billing data, and engagement logs. It scores five dimensions from 0 to 100, applies the weighting model, calculates a composite result, and assigns both RAG status and trend direction.

The report is written to client-health-report.md and ordered by risk. Each client gets attributed data, visible gaps, and 2-4 recommendations aimed at the weakest dimensions. The workflow can filter to named clients, prioritize a requested source, and use CSV or Excel files as the primary input.

Its tool set covers CRM, HubSpot, Slack, and Gmail access together with local file operations. When only part of the data is reachable, missing dimensions receive a neutral score of 50 and the gaps are marked. With no accessible source, the workflow needs connected data before it can produce the report.

What it helps with

  • create a health snapshot for every client
  • calculate weighted scores across five dimensions
  • rank accounts by current risk
  • surface weak account signals and assign next actions
  • assess expansion potential for healthy accounts

Example prompts for the agent

  • Create a client health report for every account and save it as client-health-report.md.
  • Filter the report to these clients, rank them by risk, and explain the main risk factors.
  • Use this CSV file as the primary source, calculate the scores, and mark every data gap.

How to install client-health-dashboard

1Skills CLI (Vercel)

npx skills add OneWave-AI/claude-skills --skill client-health-dashboard -a claude-code

2Manually: put the files in place

~/.claude/skills/client-health-dashboard/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/client-health-dashboard/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about client-health-dashboard

How do I install client-health-dashboard in Claude Code?

Run npx skills add OneWave-AI/claude-skills --skill client-health-dashboard -a claude-code, then check ~/.claude/skills/client-health-dashboard/SKILL.md.

What does client-health-dashboard do?

It gathers client signals from CRM and communication sources, computes health scores, assigns RAG status and trend direction, and writes a risk-ranked client-health-report.md with recommended actions.

How does the skill handle missing data?

It continues with partial data, marks the gaps, and gives missing dimensions a neutral score of 50. If no source can be reached, data must be connected or supplied before the report can be generated.

Source text

SKILL.md · MIT
---
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.

© OneWave-AI · MIT · OneWave-AI/claude-skills

Similar skills

All skills for Data and databases →

From the same set185

The whole set →
workflow-automator The workflow-automator skill turns a description of a manual business process into an automation plan. It produces a Markdown document with diagrams, tool suggestions, and implementation steps. CX Codex +1 285installs sow-generator sow-generator turns a project brief into a Statement of Work with scope, deliverables, milestones, and payment terms. Use it to prepare a consulting engagement document. CX Codex +1 284installs brand-voice-analyzer brand-voice-analyzer extracts tone, vocabulary, and structure from company copy to build a style guide and audit drafts against it. CX Codex +1 281installs weekly-business-report weekly-business-report is a Claude Code skill that collects weekly KPIs from enabled sources, compares them with targets and prior weeks, and saves a report. It brings business figures into a shared weekly view. CX Codex +1 276installs hiring-scorecard Builds a structured hiring scorecard for any role with weighted competencies, interview questions, evaluation matrix, red/green flags, and reference check questions. CX Codex +1 268installs sub-agent-orchestrator sub-agent-orchestrator chains different agents so each step feeds the next, with the flow defined in YAML. Handles retries, timeouts and parallel branches. CX Codex +1 267installs database-migrator database-migrator moves schemas, data, and database logic across PostgreSQL, MySQL, Supabase, PlanetScale, and MongoDB. Useful when a migration needs checks and a rollback plan. CX Codex +1 267installs agent-to-agent agent-to-agent coordinates multi-agent workflows across Claude agents using shared context files, structured handoffs, and predefined orchestration patterns. CX Codex +1 263installs

Project sponsors

Companies that keep this analytics open