Token导航 LogoToken导航

Agent Skill · 研究检索

churn-predictor(流失预测器)

churn-predictor 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

churn-predictor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 15,432。

总安装 7,856周安装 334GitHub Stars 3下载 3,832核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:churn-predictor(流失预测器)
来源仓库:https://github.com/jmsktm/claude-settings
仓库路径:skills/churn-predictor
安装命令:
npx skills add https://github.com/jmsktm/claude-settings --skill 'Churn Predictor'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/jmsktm/claude-settings --skill 'Churn Predictor'

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

churn-predictor 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中快速定位候选结果。适用于需要根据关键词或任务场景进行信息整理的场景,如客户流失预测。通过 npx skills add 命令从 GitHub 仓库安装,需指定技能名称和仓库地址。

安装前建议确认权限范围和维护状态,避免触发不必要的联网或文件操作。可结合原始 README 进一步核验具体用法和功能边界。

来源仓库内路径:skills/churn-predictor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/jmsktm/claude-settings --skill 'Churn Predicto…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

churn-predictor 怎么安装?

在终端执行 npx skills add https://github.com/jmsktm/claude-settings --skill 'Churn Predictor'。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

churn-predictor 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

churn-predictor 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

churn-predictor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

churn-predictor 用的人多吗?

公开数据是累计安装 7,856 次,近一周安装 334 次,下载 3,832 次,GitHub 3 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

churn-predictor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
churn-predictor

流失预测器 · 本页

7,8563需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Churn Predictor

Expert churn prediction system that identifies at-risk customers before they leave using behavioral signals, engagement patterns, and predictive analytics. This skill provides structured workflows for building churn models, monitoring risk signals, and executing retention interventions.

Churn is the silent killer of growth. By the time a customer announces they're leaving, it's often too late. This skill helps you identify churn risk early when intervention can still make a difference, prioritize retention efforts, and systematically reduce churn.

Built on data science best practices and customer success methodologies, this skill combines leading indicator analysis, risk scoring, and intervention playbooks to predict and prevent churn before it happens.

Core Workflows

Workflow 1: Churn Signal Identification

Map the behaviors that predict churn

  1. Behavioral Signals Signal Type Examples Risk Level Usage Decline 30%+ drop in logins, sessions, actions High Feature Abandonment Stopped using key features Medium-High Engagement Drop No response to emails, missed meetings Medium Support Patterns Spike in tickets, negative sentiment High Billing Issues Failed payments, downgrade requests High
  2. Account Signals

- Champion departure (key user leaves) - Company layoffs or restructuring - Merger/acquisition announcements - Budget cuts affecting your category - Competitor evaluation signals - Contract not renewed on auto-renew

  1. Relationship Signals

- NPS score decline (9-10 → 7 or below) - Missed QBRs or check-ins - Unresponsive to outreach - Escalated support issues - Negative sentiment in communications

  1. Time-Based Signals

- Approaching renewal (90/60/30 days) - End of trial or pilot - Anniversary of bad experience - Post-implementation plateau - Seasonal usage patterns

Workflow 2: Risk Scoring Model

Build a composite churn risk score

  1. Score Components Churn Risk Score = (Usage Score × 0.30) + (Engagement Score × 0.25) + (Support Score × 0.20) + (Relationship Score × 0.15) + (Account Score × 0.10) Scale: 0-100 (higher = more at risk)
  2. Usage Score Factors

- Login frequency vs. baseline - Feature adoption breadth - Active users vs. licensed seats - Time in product - Core action completion

  1. Engagement Score Factors

- Email open/click rates - Meeting attendance - Resource downloads - Training completion - Community participation

  1. Risk Categories Score Risk Level Action 0-20 Low Standard monitoring 21-40 Moderate Proactive outreach 41-60 Elevated Intervention needed 61-80 High Urgent save attempt 81-100 Critical Executive escalation

Workflow 3: Cohort & Trend Analysis

Understand churn patterns across customer segments

  1. Cohort Analysis

- Analyze by signup month/quarter - Track retention curves over time - Identify cohorts with worse retention - Correlate with product/market changes - Find patterns in successful cohorts

  1. Segment Analysis

- By customer size (SMB/Mid/Enterprise) - By industry vertical - By use case/persona - By acquisition source - By pricing tier

  1. Churn Timing Patterns

- When in customer lifecycle does churn occur? - Renewal vs. mid-contract churn - Time from warning signs to churn - Seasonal patterns - Correlation with contract length

  1. Leading Indicator Validation

- Track signals → churn correlation - Calculate signal lead time - Measure false positive rate - Refine scoring weights - A/B test interventions

Workflow 4: Alert & Escalation System

Surface risk at the right time to the right people

  1. Alert Triggers

- Score crosses threshold (e.g., into "elevated") - Rapid score increase (10+ points in 7 days) - Critical signal detected (payment failed, champion left) - Renewal approaching with elevated risk - Multiple signals converging

  1. Escalation Matrix Risk Level Owner Escalation Response SLA Moderate CSM None 5 days Elevated CSM Manager copy 48 hours High CSM + Manager VP briefed 24 hours Critical Manager VP/Exec sponsor Same day
  2. Alert Content

- Customer name and risk score - Specific signals triggering alert - Score trend (improving/declining) - Renewal date and ARR at risk - Recommended actions

  1. Alert Channels

- Slack/Teams notifications - Email digests - CRM dashboards - Weekly risk reports - Executive summaries

Workflow 5: Intervention Playbooks

Systematic approaches to save at-risk customers

  1. Intervention Matching Root Cause Intervention Low adoption Training, onboarding redo Technical issues Engineering escalation, workarounds Value unclear ROI analysis, executive alignment Champion left Relationship rebuild with new stakeholders Pricing concerns Discount, plan adjustment, payment terms Competitive Feature comparison, roadmap preview
  2. Save Play Execution

- Diagnose root cause (don't assume) - Match intervention to cause - Assign owner and resources - Set clear timeline and milestones - Track outcome (saved, lost, reason)

  1. Intervention Tactics

- Urgent Call: Same-day executive outreach - Health Check: Comprehensive account review - Training Blitz: Intensive enablement sessions - Success Sprint: Focused value delivery - Executive Alignment: VP/C-level engagement - Commercial Discussion: Pricing/terms adjustment

  1. Outcome Tracking

- Save rate by risk level - Save rate by intervention type - Time from intervention to resolution - Reasons for unsuccessful saves - Long-term retention of saved accounts

Quick Reference

ActionCommand/Trigger
Check risk score"Show churn risk for [Customer]"
List at-risk accounts"Show accounts above [X] risk score"
Analyze churn patterns"Analyze churn patterns by [segment]"
Review alerts"Show churn alerts this week"
Create save plan"Create intervention plan for [Customer]"
Score validation"Validate churn model accuracy"
Cohort analysis"Analyze retention by cohort"
Signal analysis"Find leading churn indicators"
Trend report"Show risk score trends"
Intervention report"Report on save play outcomes"

Best Practices

Signal Selection

  • Focus on behaviors you can observe
  • Validate correlation with actual churn
  • Use leading indicators (not lagging)
  • Combine multiple signal types
  • Weight by predictive power

Scoring Model

  • Start simple, add complexity gradually
  • Calibrate weights with historical data
  • Validate with blind holdout testing
  • Recalibrate quarterly
  • Document methodology

Alert Design

  • Don't alert on every score change
  • Focus on actionable thresholds
  • Include context in alerts
  • Route to right person
  • Avoid alert fatigue

Intervention

  • Diagnose before prescribing
  • Match intervention to root cause
  • Set clear success criteria
  • Track outcomes rigorously
  • Learn from failures

Model Maintenance

  • Review accuracy monthly
  • Retrain with new churn data
  • Adjust for product changes
  • Update as customer base evolves
  • Document false positives/negatives

Churn Signals Library

Usage Signals

SignalCalculationWarning Threshold
Login decline% change week-over-week-30% for 2+ weeks
DAU/MAU ratioDaily active / Monthly activeBelow 0.2
Feature breadth# features used / availableBelow 30%
Seat utilizationActive users / licensed seatsBelow 50%
Session depthActions per sessionBelow baseline by 40%

Engagement Signals

SignalCalculationWarning Threshold
Email engagementOpen rate × Click rateBelow 5%
Meeting attendanceAttended / ScheduledBelow 60%
Response timeAvg days to respondAbove 5 days
QBR participationAttended / ScheduledMiss 2+ in row
Training completionCompleted / AvailableBelow 25%

Support Signals

SignalCalculationWarning Threshold
Ticket volumeTickets / month3× baseline
Sentiment scoreNegative / TotalAbove 30%
Escalation rateEscalated / TotalAbove 20%
Resolution satisfactionCSAT on resolvedBelow 3/5
Open ticket ageAvg days openAbove 7 days

Relationship Signals

SignalCalculationWarning Threshold
NPS changeCurrent - PreviousDrop of 3+ points
Health scoreComposite scoreBelow 60
Champion riskChampion activity declineBelow 50% of baseline
Executive accessExec meetings / quarter0 in 2+ quarters
Renewal confidenceCSM assessmentBelow 70%

Risk Report Template

Weekly At-Risk Summary

# Churn Risk Report: Week of [Date]

## Summary
- Accounts at elevated risk or above: [X]
- Total ARR at risk: $[Amount]
- New alerts this week: [X]
- Risk trending up: [X accounts]
- Risk trending down: [X accounts]

## Critical Risk (81-100)
| Account | ARR | Score | Key Signals | Owner | Action |
|---------|-----|-------|-------------|-------|--------|
| [Name] | $X | 87 | [Signals] | [CSM] | [Status] |

## High Risk (61-80)
[Same format]

## Elevated Risk (41-60)
[Same format]

## Interventions in Progress
| Account | Started | Intervention | Progress |
|---------|---------|--------------|----------|
| [Name] | [Date] | [Type] | [Status] |

## Outcomes This Week
- Saved: [X accounts, $ARR]
- Lost: [X accounts, $ARR, reasons]
- De-escalated: [X accounts]

Red Flags

  • Model overfit: Perfect on training data, poor on new data
  • Signal lag: Indicators trigger too late for intervention
  • False positive fatigue: Too many alerts that aren't real risk
  • Missing signals: Key churn predictors not tracked
  • Score opacity: Team doesn't understand why scores change
  • Intervention mismatch: Same playbook for different problems
  • No feedback loop: Not learning from save attempts
  • Data quality: Missing or stale underlying data

Model Validation Metrics

MetricWhat It MeasuresTarget
AccuracyOverall correct predictions80%+
PrecisionTrue positives / All predicted positives70%+
RecallTrue positives / All actual churns85%+
Lead TimeDays from high risk to actual churn60+ days
False Positive RateFalse alarms / All high-risk alerts< 30%
Save RateSaved / Attempted saves40%+
AUC-ROCModel discrimination ability0.75+

平台分布

Codex

34.96%
按下载量换算1,340

Claude

30.87%
按下载量换算1,183

Cursor

20.65%
按下载量换算791

Gemini CLI

10.36%
按下载量换算397

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills