Installs into .claude/skills of the current project.
Are you the author of Churn Risk Playbook?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/schmitech-churn-risk-playbook)
---
name: churn-risk-playbook
description: How to combine product telemetry with churn-risk simulation for a customer.
mcp_tools:
- "business-sample__get_product_telemetry"
- "business-sample__simulate_churn_risk_scenario"
enabled: true
version: "1.0"
priority: 0
---
## Order of calls
Call `get_product_telemetry` for the customer before
`simulate_churn_risk_scenario`. Both tools use the server's current customer
data; the telemetry result supplies the adoption context needed to explain the
simulation rather than relying on model assumptions.
## Presenting results
Never present a bare churn probability. Always pair it with the simulation's
key drivers and the telemetry's utilization or adoption alerts, so the number
is explainable rather than a black box. The simulation itself accounts for
open P1/P2 support escalations; telemetry does not return ticket volume.
Render a concise risk summary with Current ARR, Health Score, Seat
Utilization, Churn Probability, ARR at Risk, and Risk Category. Follow it with
the simulation's `keyDrivers` and the telemetry's `telemetryAlerts`. Do not
infer support-ticket volume beyond the simulation's `openEscalationsCount`, or
invent a trend or risk driver that neither result returns.
