early-churn-downgrade-signal-detection

Classify churn and downgrade risk into three tiers with Markdown reports.

58|21|Updated May 15, 2026
One-click install
npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill early-churn-downgrade-signal-detection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: early-churn-downgrade-signal-detection
Source: https://github.com/t0ddc3by/claude-for-customer-success/tree/main/rev-ops/skills/early-churn-downgrade-signal-detection
Command: npx skills add https://github.com/t0ddc3by/claude-for-customer-success --skill early-churn-downgrade-signal-detection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Detects early churn and downgrade risk upstream at deal close, then continues identifying behavioral and late-stage pre-renewal signals so CS teams can intervene with more runway.

Core Features & Use Cases

  • Three-tier churn signal model: Tier 1 at deal close (rule-mode or cohort-mode when sufficient history exists), Tier 2 across 30–90 days of onboarding behavior, and Tier 3 across 90–120 days pre-renewal.
  • Actionable risk flag reporting: Produces a Markdown risk-flag assessment including tier classification, confidence, and intervention recommendation.
  • Escalation routing handoff: Ensures every Tier 2 and Tier 3 flag includes an escalation path and named owner, with guidance to hand off to csm:risk-flag.

Quick Start

Ask the skill to run "Tier 1 churn signals for <Account Name>" and include the desired tier1_mode (rule or cohort).

Frequently Asked Questions about early-churn-downgrade-signal-detection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect early churn risk before a renewal cycle begins?

Early churn signals are detected using a three-tier model: Tier 1 at deal close, Tier 2 across 30–90 days of onboarding behavior, and Tier 3 across 90–120 days pre-renewal. This approach flags risk upstream to give CS teams more runway for intervention.

How do I set up Tier 1 churn signals for a specific account?

To set up Tier 1 churn signals, ask the skill to run a Tier 1 assessment for the account and specify the desired tier1_mode as either rule or cohort. Cohort mode requires sufficient historical data for comparative analysis.

What is the best way to route escalation flags for at-risk CS accounts?

The best way to route escalation flags is to generate a Markdown risk-flag assessment with tier classification, confidence levels, and intervention recommendations. Every Tier 2 and Tier 3 flag includes an escalation path and named owner for handoff.

Can I run a portfolio scan for downgrade risk across multiple accounts?

Yes, you can run a portfolio scan for downgrade risk. The skill emits Markdown output in either single-account or portfolio-scan formats and applies optional cohort-mode comparisons when sufficient historical data exists across the portfolio.

What data is needed for cohort-mode comparisons in churn detection?

Cohort-mode comparisons in churn detection require sufficient historical account data to exist for analysis. The skill validates this prerequisite during pre-flight configuration before applying cohort-mode to Tier 1 or subsequent behavioral tiers.

What are the limitations of rule-mode for early churn signal detection?

Rule-mode for early churn signal detection lacks the comparative behavioral context provided by cohort-mode. When sufficient historical data exists, cohort-mode offers deeper analytical framing for Tier 1 classification than rule-mode.