client-health-dashboard

client-health-dashboard is a skill for Claude Code, Codex from OneWave-AI/claude-skills. It costs 54 tokens per session (894 once invoked), scanned A, original, MIT.

A report that summarizes the health of every client account. It combines customer relationship records, support activity, product usage, billing, and engagement into risk ratings and trends.

In plain words
What is it for?
Use it to calculate health scores, assign red-amber-green status, identify declining accounts, and organize recommended retention or expansion actions.
Why use it?
It brings account information into one prioritized view, making it easier to spot clients who may be at risk. It records missing data instead of pretending incomplete information is complete.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: model in frontmatter.

Good fit Use it to calculate health scores, assign red-amber-green status, identify declining accounts, and organize recommended retention or expansion actions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/onewave-ai/claude-skills/client-health-dashboard
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add OneWave-AI/claude-skills --skill client-health-dashboard
Clone the repo
git clone --depth 1 https://github.com/OneWave-AI/claude-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for client-health-dashboard

README.md
[![agentmods](https://agentmods.dev/badge/skills/onewave-ai/claude-skills/client-health-dashboard/github.svg)](https://agentmods.dev/skills/onewave-ai/claude-skills/client-health-dashboard)
Your own site
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/client-health-dashboard"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/client-health-dashboard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for client-health-dashboard

Your own site · 80×15
<a href="https://agentmods.dev/skills/onewave-ai/claude-skills/client-health-dashboard"><img src="https://agentmods.dev/badge/skills/onewave-ai/claude-skills/client-health-dashboard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 894 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.00894
Opus 5 $0.00027 $0.00447
Sonnet 5 $0.00011 $0.00179
Haiku 4.5 $0.00005 $0.00089

Measured 13d ago against content hash 659a7b34ac92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

client-health-dashboard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

client-health-dashboard/SKILL.md · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Read the full file on GitHub · 50 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 13d ago First seen · 50 lines · 54 tokens per session scan A 659a7b34ac92

Subscribe to this mod's changes

client-health-dashboard is a skill published in the GitHub repository OneWave-AI/claude-skills (291 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 894 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

analytics-strategy

Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement.…

rampstackco/claude-skills · 126 tokens

content-strategy

Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…

rampstackco/claude-skills · 120 tokens

incident-response

Manage active production incidents through detection, triage, mitigation, communication, and resolution with structured roles and decision-making. Use this skill whenever the user has an active incident, a production issue, a service outage, a security incident, or needs to plan incident response procedures. Triggers…

rampstackco/claude-skills · 117 tokens

stakeholder-communication

Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…

rampstackco/claude-skills · 103 tokens

review-work

Post-implementation gate review: run manual QA on the real surface yourself, then launch ONE gate reviewer (never a panel) to audit goal, constraints, code quality, security, missed context, and QA evidence. Use before a PR handoff or when the user explicitly asks to review completed work.

code-yeongyu/oh-my-openagent · 63 tokens

agb-begriff-vorformuliert-305

Für AGB Begriff Vorformuliert 305: ordnet Norm, Beweislast und Gegenargument; Ergebnis: Prüfprodukt mit Risiko und nächstem Schritt. Fachgebiet: AGB-Recht-Prüfer. Route: agb-begriff-vorformuliert-305.

Klotzkette/claude-fuer-deutsches-recht · 68 tokens