본문으로 건너뛰기
cccskills
무료GitHub에 공개

customer-health-analyst

Expert customer health scoring and analytics guidance. Use when designing health scores, building churn prediction models, analyzing usage metrics, identifying at-risk accounts, creating executive dashboards, or performing cohort analysis. Use for leading indicator development, customer data enrichment, risk escalation frameworks, and retention analytics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

실행 점수 미검증

설치 방법 보기

포함된 파일(12)

  • SKILL.md8.7 KB
  • rules/_sections.md1.7 KB
  • rules/churn-prediction-modeling.md14.8 KB
  • rules/cohort-analysis-benchmarking.md14.0 KB
  • rules/data-enrichment-360.md13.9 KB
  • rules/executive-reporting-dashboards.md13.4 KB
  • rules/health-model-validation.md15.4 KB
  • rules/health-score-design.md8.2 KB
  • rules/indicators-leading-lagging.md10.8 KB
  • rules/risk-identification-escalation.md11.5 KB
  • rules/segmentation-tier-scoring.md14.1 KB
  • rules/usage-analytics-adoption.md12.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Expert full-cycle enterprise sales strategist for B2B SaaS. Use when planning sales strategy, pipeline management, deal progression, account planning, competitive displacement, or territory optimization. Covers multi-threading, executive engagement, champion development, buying committee navigation, and complex deal orchestration. Use for enterprise selling, account expansion, land-and-expand, and quota attainment.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

adr

무료

Expert Architecture Decision Record (ADR) creation and lifecycle management based on Olaf Zimmermann's methodology. Use when creating ADRs, reviewing architectural decisions, evaluating decision readiness, writing MADR templates, assessing decision quality, or managing ADR logs. Covers the full lifecycle from readiness (START criteria) through creation, MADR formatting, completion (ECADR criteria), and ongoing maintenance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

Hand off code review to OpenAI Codex CLI. Use when asked to "review code with codex", "codex review", "get a second opinion on code", "review my changes", "review this PR", or when you want AI-powered code review from a different model perspective.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

Expert community-led growth and community management guidance. Use when building developer communities, Discord/Slack communities, online communities, managing community platforms, designing member onboarding, creating engagement programs, running ambassador programs, measuring community health, setting up moderation systems, or implementing DevRel strategies. Use for community-led growth, member activation, user-generated content programs, and community governance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

Expert competitive intelligence and strategy guidance for B2B/SaaS companies. Use when conducting competitive research, creating battlecards, analyzing win/loss data, building market landscape maps, positioning against alternatives, handling competitive objections, writing comparison pages, or developing sales enablement for competitive situations. Use for competitive monitoring, feature comparisons, and market intelligence gathering.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

Master orchestrator that chains all Remotion video creation skills together in a single automated pipeline. Takes a creative brief and produces a complete, production-ready Remotion video project. Use when starting a new video from scratch, when asked to "create a video", "make a video", "build a complete video", or "video from idea to code".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ncklrs/startup-os-skills522026년 2월 27일 업데이트

ncklrs의 스킬 모두 보기

이 스킬의 문제 신고