Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
ncklrs avatar

Customer Health Analyst

  • 130 installs
  • 37 repo stars
  • Updated February 26, 2026
  • ncklrs/startup-os-skills

Customer Health Analyst is an agent skill that structures health scoring, churn prediction, and CS reporting for solo builders retaining B2B customers.

About

Customer Health Analyst is an agent skill package for solo and indie operators running subscription or usage-based products who must spot churn before invoices lapse. It walks through health-score design—components, weights, thresholds, and validation—then separates predictive leading signals from lagging revenue metrics so interventions fire early. Churn prediction covers feature engineering, risk scoring, and early-warning cadence; usage analytics tracks engagement and feature adoption against benchmarks. Risk identification adds escalation playbooks and stakeholder communication for at-risk accounts, while cohort analysis compares segment retention over time. Data enrichment frames how to stitch product, billing, and support data into a governed customer view, and executive reporting selects KPIs and dashboard layouts founders can share with investors or a first CS hire. Use it when you have paying customers and need a repeatable health model instead of reactive support tickets.

  • 8 capability areas from health-score architecture through executive reporting
  • Churn prediction, leading vs lagging indicators, and intervention timing
  • Usage analytics, cohort retention curves, and adoption benchmarking
  • Risk identification with escalation frameworks and save strategies
  • Data enrichment and 360-degree customer view governance

Customer Health Analyst by the numbers

  • 130 all-time installs (skills.sh)
  • +2 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #410 of 853 Sales & Marketing skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/ncklrs/startup-os-skills --skill customer-health-analyst

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs130
repo stars37
Security audit2 / 3 scanners passed
Last updatedFebruary 26, 2026
Repositoryncklrs/startup-os-skills

What it does

Design health scores, churn signals, and executive CS dashboards when you need to retain and expand B2B customers without a full data team.

Who is it for?

Best when you have early paid accounts and need churn early-warning and lifecycle playbooks without hiring customer success first.

Skip if: Pre-revenue ideas with no customers to score, or teams that only need one-off SQL charts without a retention framework.

When should I use this skill?

You have paying customers and need structured health scoring, churn prediction, cohort views, or CS executive reporting—not ad-hoc spreadsheet patches.

What you get

You leave with component-weighted health scores, indicator priorities, risk playbooks, and executive-ready KPI narratives you can wire to your analytics stack.

  • Health score architecture with weights and thresholds
  • Churn risk signals and intervention playbook outline
  • Executive KPI and dashboard narrative

By the numbers

  • 8 section areas covering health design through executive reporting
  • Multiple areas marked CRITICAL impact (health, indicators, churn, risk)

Files

SKILL.mdMarkdownGitHub ↗

Customer Health Analyst

Expert guidance for customer health scoring, predictive analytics, and data-driven customer success strategies. Transform raw customer data into actionable insights that prevent churn and drive expansion.

Philosophy

Customer health is not a single metric — it's a predictive system:

1. Measure what matters — Health scores should predict outcomes, not just track activity 2. Lead, don't lag — Focus on indicators that predict churn before it's too late 3. Segment for action — Different customers need different interventions 4. Automate detection — Scale health monitoring across your entire customer base 5. Close the loop — Analytics without action is just expensive data collection

How This Skill Works

When invoked, apply the guidelines in rules/ organized by:

  • health-* — Health score design, weighting, and calibration
  • indicators-* — Leading vs lagging indicator analysis
  • churn-* — Prediction modeling and early warning systems
  • usage-* — Analytics and adoption metrics
  • risk-* — Identification, escalation, and intervention
  • data-* — Enrichment and customer 360 development
  • cohort-* — Analysis and benchmarking
  • executive-* — Reporting and dashboards
  • segmentation-* — Customer tiers and scoring models

Core Frameworks

The Health Score Hierarchy

┌─────────────────────────────────────────────────────────────────┐
│                    COMPOSITE HEALTH SCORE                       │
│                         (0-100)                                 │
├─────────────────────────────────────────────────────────────────┤
│                                                                 │
│  ┌──────────┐  ┌──────────┐  ┌──────────┐  ┌──────────┐       │
│  │ PRODUCT  │  │ENGAGEMENT│  │ GROWTH   │  │ SUPPORT  │       │
│  │  USAGE   │  │          │  │ SIGNALS  │  │ HEALTH   │       │
│  │  (35%)   │  │  (25%)   │  │  (20%)   │  │  (20%)   │       │
│  └──────────┘  └──────────┘  └──────────┘  └──────────┘       │
│                                                                 │
├─────────────────────────────────────────────────────────────────┤
│                    COMPONENT METRICS                            │
│                                                                 │
│  Usage:        Engagement:    Growth:        Support:          │
│  - DAU/MAU     - NPS score    - Seat trend   - Ticket volume   │
│  - Features    - CSM meetings - Usage trend  - Resolution time │
│  - Depth       - Email opens  - Expansion    - Sentiment       │
│  - Breadth     - Logins       - Contract     - Escalations     │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Leading vs Lagging Indicators

TypeDefinitionExamplesAction Window
LeadingPredict future outcomesUsage decline, engagement drop60-90 days
CoincidentMove with outcomesSupport sentiment, NPS30-60 days
LaggingConfirm after the factChurn, revenue lossToo late

Customer Health States

┌─────────────────────────────────────────────────────────────────┐
│                                                                 │
│  THRIVING ──→ HEALTHY ──→ NEUTRAL ──→ AT-RISK ──→ CRITICAL    │
│    (85+)      (70-84)     (50-69)     (30-49)      (<30)       │
│                                                                 │
│  Expand       Monitor     Engage      Intervene    Escalate    │
│                                                                 │
└─────────────────────────────────────────────────────────────────┘

Health Score Components

ComponentWeightKey MetricsWhy It Matters
Product Usage30-40%DAU/MAU, feature adoption, depthUsage predicts value realization
Engagement20-25%NPS, CSM contact, responsivenessRelationship strength indicator
Growth Signals15-20%Seat expansion, usage trendInvestment signals commitment
Support Health15-20%Ticket volume, sentiment, resolutionFrustration predicts churn
Financial5-10%Payment history, contract lengthFinancial commitment level

Churn Risk Factors

FactorRisk WeightDetection Method
Champion departureCriticalContact tracking, LinkedIn
Usage decline >30%HighProduct analytics
Negative NPS (0-6)HighSurvey responses
Support escalationsHighTicket analysis
Missed renewal meetingHighCSM activity tracking
Contract downgradeVery HighBilling data
Competitor mentionsHighCall transcripts, tickets
Budget review mentionsMediumCSM notes

The Analytics Stack

LayerPurposeTools/Methods
CollectionGather raw dataProduct events, CRM, support
ProcessingClean and transformETL, data pipelines
CalculationCompute scoresScoring algorithms
StorageHistorical trackingData warehouse
VisualizationPresent insightsDashboards, reports
ActionTrigger interventionsAlerting, automation

Key Metrics

MetricFormulaTarget
Health Score AccuracyChurn predicted / Actual churn>70%
Leading Indicator CorrelationCorrelation to outcomes>0.6
Score Distribution% in each health tierBell curve
Intervention Success RateSaved / Intervened>40%
Time to DetectionDays before risk → action<14 days
False Positive RateFalse alerts / Total alerts<20%

Executive Dashboard KPIs

KPIDefinitionBenchmark
Gross Revenue RetentionRetained ARR / Starting ARR85-95%
Net Revenue Retention(Retained + Expansion) / Starting100-130%
Logo RetentionRetained customers / Starting90-95%
Health Score AverageMean across customer base65-75
At-Risk RevenueARR with health <50<15%
Expansion RateCustomers expanded / Total15-30%

Cohort Analysis Framework

Cohort TypeSegments ByUse Case
Time-basedSign-up month/quarterRetention trends
BehavioralFeature usage patternsActivation success
Value-basedARR tierSegment economics
IndustryVerticalProduct-market fit
AcquisitionChannel/sourceMarketing efficiency

Anti-Patterns

  • Vanity health scores — Scores that look good but don't predict outcomes
  • Over-weighted product usage — Ignoring relationship and sentiment signals
  • Lagging indicator focus — Measuring what already happened
  • One-size-fits-all thresholds — Same scores mean different things for different segments
  • Manual-only health tracking — Can't scale without automation
  • Score without action — Calculating risk without intervention playbooks
  • Annual calibration only — Health models need continuous refinement
  • Ignoring data quality — Garbage in, garbage out

Related skills

How it compares

Use for customer-success methodology and score design, not a plug-in monitoring agent or generic SQL assistant.

FAQ

Who is customer-health-analyst for?

Developers on subscription or usage-based SaaS who own retention, expansion, and save motions while still shipping product.

When should I use customer-health-analyst?

In Grow when you define lifecycle dashboards and save triggers; in Operate when production usage patterns feed risk signals; in Validate when pricing and scope assumptions need cohort proof from pilot customers.

Is customer-health-analyst safe to install?

Treat it as advisory playbooks—review the Security Audits panel on this page before pointing an agent at production CRM or billing credentials.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.