Customer Health Scorer logo

Customer Health Scorer

Organization
Amazon-Quick
customer-health-scorer

Computes multi-dimensional customer health scores across usage, engagement, support, and relationship dimensions. Classifies accounts as Healthy/At-Risk/Critical with segment-aware benchmarking and produces actionable intervention recommendations. Use when asked to 'score customer health', 'account health check', 'which customers are at risk', 'customer health report', 'renewal risk assessment', or 'portfolio health overview'.

Overview

PublisherAmazon-Quick
RepositoryAmazon-Quick-official-catalog
Skill namecustomer-health-scorer
Stars
50
Forks
4
Bundled files
1
LicenseMIT-0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Amazon-Quick on GitHub. Read the source before you install it.

Installation

Install the Customer Health Scorer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/customer-success/customer-health-scorer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Amazon-Quick/Amazon-Quick-official-catalog.git /tmp/Amazon-Quick-official-catalog
mkdir -p .claude/skills
cp -r /tmp/Amazon-Quick-official-catalog/skills/customer-success/customer-health-scorer .claude/skills/customer-health-scorer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Customer Health Scorer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Customer Health Scorer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Customer Health Scorer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Overview

Scores customer accounts across multiple health dimensions, classifies them into risk zones, and generates prioritized intervention recommendations. Produces a visual scorecard with trend indicators and segment-aware benchmarks so teams can act on early warning signals before churn materializes.

Workflow

<Definition - Health Dimensions> The five measurable facets of customer health:

  • Usage: Product adoption depth and breadth. Metrics include DAU/MAU ratio, feature penetration, session frequency, and time-in-product.
  • Engagement: Proactive interaction with the vendor. Metrics include event attendance, content consumption, community participation, and training completion.
  • Support: Ticket volume, severity distribution, resolution satisfaction, and escalation frequency. Lower volume with high satisfaction indicates health; high volume with low satisfaction indicates risk.
  • Relationship: Strength of human connections. Metrics include executive sponsor access, multi-threading depth (number of distinct contacts engaged), meeting cadence, and NPS/CSAT responses.
  • Commercial: Financial trajectory. Metrics include expansion rate, contraction signals, payment timeliness, discount dependency, and renewal pipeline status. </Definition - Health Dimensions>

<Definition - Scoring Zones> Three classification bands applied after dimension scores are computed:

  • Healthy (score above 75): Account shows strong signals across measured dimensions. No immediate intervention required. Monitor for regression.
  • At-Risk (score 40 to 75): Account shows degradation in one or more dimensions. Requires proactive outreach within 2 weeks. Specific risk signals should drive the intervention type.
  • Critical (score below 40): Account shows severe degradation or multi-dimension failure. Requires immediate intervention plan within 48 hours. Escalate to account leadership. </Definition - Scoring Zones>

<Definition - Segment Benchmarks> Baseline expectations vary by customer segment because behavior patterns differ structurally:

  • Enterprise: Higher relationship and engagement expectations. Usage patterns tend toward broad but less frequent. Support tickets skew toward feature requests over break-fix. Benchmark calibration: relationship weight increased to 25%, usage weight reduced to 15%.
  • Mid-Market: Balanced expectations across all dimensions. Usage tends toward moderate depth with consistent frequency. Benchmark calibration: equal 20% weight across all five dimensions.
  • SMB: Higher usage and commercial sensitivity. Relationship depth is naturally limited (fewer contacts). Benchmark calibration: usage weight increased to 30%, relationship weight reduced to 10%.
  • All: Applies mid-market weights as the neutral baseline when segment is unknown or mixed. </Definition - Segment Benchmarks>

<Workflow - Score Customer Health description="End-to-end customer health scoring from raw data to actionable scorecard." tools=[file_read, file_write, run_python, open_in_session_tab] triggers=["score customer health", "account health check", "which customers are at risk", "customer health report", "renewal risk assessment", "portfolio health overview"]

  1. [Decide] Determine the input type:

    • File path provided: Read using file_read (CSV/JSON) or run_python with pandas (Excel). Inspect the first 10 rows, all column names, data types, row count, and missing value percentages per column.

    • Pasted data: Parse the tabular data from the conversation. Normalize into a structured format for analysis.

    • Description only: Ask the user what system their data lives in (CRM like Salesforce/HubSpot, analytics like Mixpanel/Amplitude, spreadsheet, data warehouse) and guide them on which fields to export. Provide a template CSV structure showing the columns needed for each selected dimension.

  2. [Ask user] Present the discovered file structure: column names, row count, sample values. Propose a column-to-metric mapping for each selected health dimension. Ask the user to confirm or correct the mappings. Flag any dimensions where fewer than 2 input metrics are available and recommend marking those as low confidence per Rule 6.

  3. [Agent] Determine the segment benchmark weights to apply based on the user's segment selection. If "all" was selected, apply the neutral mid-market weights. Log the weight distribution: which percentage each dimension contributes to the composite score.

  4. [Think] Evaluate data quality across the mapped columns. Identify accounts with excessive missing values (more than 50% of mapped metrics absent). Identify potential new customers (accounts with creation dates under 90 days if that field exists). Determine if historical periods are available for trend computation. Decide whether to flag any dimensions as low confidence.

  5. [Agent] Execute the scoring computation in a single Python script:

    • Normalize each metric to a 0-100 scale using min-max normalization within the dataset (or against segment benchmarks if prior benchmark data is provided).
    • Compute per-dimension scores as the weighted average of normalized metrics within that dimension.
    • Compute the composite health score as the segment-weighted sum of dimension scores.
    • Classify each account into Healthy, At-Risk, or Critical zones.
    • Compute trend direction for each dimension if multiple time periods exist.
    • Flag low-confidence dimensions and new-customer exclusions. Save the scoring script to the artifacts folder for reproducibility.
  6. [Agent] Generate intervention recommendations for every At-Risk and Critical account. For each flagged account:

    • Identify the weakest dimension(s) driving the classification.
    • Map the specific degraded metrics to a concrete recommended action.
    • Assign urgency (immediate for Critical, within 2 weeks for At-Risk).
    • Note any compounding risk factors (multiple dimensions declining simultaneously).
  7. [Agent] Build the health scorecard output using the Health Scorecard template. Write the scorecard as an HTML file with sortable tables, color-coded risk zones, and dimension breakdowns. Save to artifacts and open in the session tab using open_in_session_tab.

  8. [Ask user] Present the summary statistics: total accounts scored, distribution across zones, top 5 most critical accounts with their primary risk drivers. Ask if the user wants to drill into specific accounts, adjust weights, or export the results in a different format.

</Workflow - Score Customer Health>

<Template - Health Scorecard>

markdown
# Customer Health Scorecard

**Generated:** {{date}}
**Segment:** {{segment}} | **Benchmark weights:** {{weight_distribution}}
**Accounts scored:** {{total_accounts}} | **Excluded (new/insufficient data):** {{excluded_count}}

## Portfolio Summary

| Zone | Count | Percentage |
|------|-------|------------|
| Critical (below 40) | {{critical_count}} | {{critical_pct}}% |
| At-Risk (40-75) | {{at_risk_count}} | {{at_risk_pct}}% |
| Healthy (above 75) | {{healthy_count}} | {{healthy_pct}}% |

## Critical Accounts (Immediate Action Required)

For each critical account:

| Account | Composite Score | Weakest Dimension | Key Signal | Trend | Recommended Action |
|---------|----------------|-------------------|------------|-------|-------------------|
| {{account_name}} | {{score}} | {{weakest_dim}} | {{signal_detail}} | {{trend_direction}} | {{recommendation}} |

## At-Risk Accounts (Action Within 2 Weeks)

Same table structure as Critical, sorted by composite score ascending.

## Dimension Breakdown (All Accounts)

For each account, show individual dimension scores:

| Account | Usage | Engagement | Support | Relationship | Commercial | Composite | Zone |
|---------|-------|------------|---------|--------------|------------|-----------|------|
| {{account_name}} | {{usage_score}} | {{engagement_score}} | {{support_score}} | {{relationship_score}} | {{commercial_score}} | {{composite}} | {{zone}} |

## Data Quality Notes

- Dimensions marked low confidence: {{low_confidence_dims}}
- Accounts excluded (under 90 days): {{new_accounts_list}}
- Metrics with high missing rates: {{missing_metrics}}

## Methodology

- Normalization: Min-max within dataset, scaled 0-100
- Dimension weights ({{segment}}): Usage {{usage_wt}}%, Engagement {{engagement_wt}}%, Support {{support_wt}}%, Relationship {{relationship_wt}}%, Commercial {{commercial_wt}}%
- Classification thresholds: Healthy above 75, At-Risk 40-75, Critical below 40
- Trend calculation: Period-over-period comparison where historical data exists

</Template - Health Scorecard>

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Customer Health Scorer AI skill do?

Computes multi-dimensional customer health scores across usage, engagement, support, and relationship dimensions. Classifies accounts as Healthy/At-Risk/Critical with segment-aware benchmarking and produces actionable intervention recommendations. Use when asked to 'score customer health', 'account health check', 'which customers are at risk', 'customer health report', 'renewal risk assessment', or 'portfolio health overview'.

Why use Customer Health Scorer on TypingMind?

Because you install it once and use it with any model. Customer Health Scorer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Customer Health Scorer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Amazon-Quick/Amazon-Quick-official-catalog/tree/main/skills/customer-success/customer-health-scorer. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Customer Health Scorer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Customer Health Scorer?

As many as you like. As long as a model supports skills, you can use Customer Health Scorer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Customer Health Scorer AI skill free?

Yes. It is published on GitHub by Amazon-Quick under the MIT-0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇