Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type.

MITAuto-check: notesSales & Support

Install Keep Churn

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill keep-churn -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace keep-churn --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn .claude/skills/keep-churn && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
keep-churn
GitHub stars
2.8k
Token cost
~1.6k tokens
SKILL.md length
389 words
Files
1
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type.

  • Works in 5 steps: Gather Health Signal Data → Classify Risk Signals → Classify Each Account → …
  • Asked to find at-risk accounts
  • SKILL.md covers Steps and Delivery
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Keep Churn is an agent skill from jeremylongshore/tons-of-skills-marketplace. Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Sales & Support, covering Customer success and Referral and retention marketing. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to find at-risk accounts
  • Who might churn
  • Build a churn prevention plan
  • Identify churn signals

Example prompts

  • “find at-risk accounts”
  • “who might churn”
  • “build a churn prevention plan”
  • “/keep-churn”

Requirements

  • Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, AskUserQuestion

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather Health Signal Data
  2. Classify Risk Signals
  3. Classify Each Account
  4. Intervention Sequences by Risk Type
  5. Executive Escalation Criteria

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Bash
    • Glob
    • Grep
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Keep Churn loads about 1.6k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~86
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Bash, Glob, Grep, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 389 words, ~1,632 tokens.

Download SKILL.mdSave it as .claude/skills/keep-churn/SKILL.md (or your agent's skills folder).
name
keep-churn
description
Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", "identify churn signals", or "rescue this account".
allowed-tools
Read, Bash, Glob, Grep, AskUserQuestion
version
0.1.0
author
tonone-ai <hello@tonone.ai>
license
MIT

Churn Risk Identification and Intervention

You are Keep — the customer success engineer on the Product Team. Identify at-risk accounts before they churn and produce targeted intervention sequences per risk type.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Steps

Step 0: Gather Health Signal Data

Scan for available health and account data:

bash
find . -name "*.md" -o -name "*.json" -o -name "*.csv" 2>/dev/null | xargs grep -l "churn\|health\|at.risk\|renewal\|cancell\|downgrade\|NPS\|CSAT\|adoption\|usage" 2>/dev/null | head -15
find . -name "*.md" 2>/dev/null | xargs grep -l "account\|customer\|ARR\|MRR\|tier\|segment" 2>/dev/null | head -10

Ask for any missing inputs:

  • What accounts or cohort are we scanning?
  • What health data is available? (usage, support tickets, NPS, login frequency)
  • What is the renewal window? (accounts renewing in 30 / 60 / 90 days)
  • Any known sponsor changes, budget freezes, or competitor evaluations?
Step 1: Classify Risk Signals

Map each account signal to a risk indicator:

SignalRisk TypeSeverity
Usage dropped >40% vs. prior periodLow adoptionHIGH
0 logins in past 30 daysDisengagedCRITICAL
NPS drop of 20+ pointsSatisfaction collapseHIGH
Support tickets up 3x with unresolved escalationProduct frictionHIGH
Economic buyer or champion left the companySponsor changeCRITICAL
"Exploring alternatives" mentioned in any commsCompetitor evalCRITICAL
Budget freeze or cost reduction initiative announcedBudget pressureHIGH
Below 30% seat utilization at 6+ monthsLow adoptionMEDIUM
No champion contact in 60+ daysRelationship gapMEDIUM
Missed 2 consecutive check-in callsDisengagementMEDIUM
Show full SKILL.md (177 more words)Show less
Step 2: Classify Each Account

For each at-risk account, assign a tier:

LevelCriteriaTime to act
CRITICALRenewal in <30 days OR competitor evaluation confirmed OR sponsor leftSame day
HIGH2+ HIGH signals OR renewal in 31-60 daysWithin 48 hours
MEDIUM1 HIGH signal OR 2+ MEDIUM signals OR renewal in 61-90 daysWithin 1 week
## At-Risk Account Register

| Account | ARR | Renewal | Risk Level | Primary Signal |
|---------|-----|---------|------------|----------------|
| [Name]  | $X  | [date]  | CRITICAL   | [signal]       |
| [Name]  | $X  | [date]  | HIGH       | [signal]       |
| [Name]  | $X  | [date]  | MEDIUM     | [signal]       |
Step 3: Intervention Sequences by Risk Type

Produce the intervention playbook for each primary risk type present in the account register.

Risk Type: Low Adoption
Day 0:  CSM calls champion. "We noticed usage has changed — what shifted?"
        Goal: understand root cause (UX, competing priorities, team change)
Day 2:  Send personalized "quick wins" guide for their top 2 unused features.
Day 5:  Offer a 30-min re-onboarding session for the team.
Day 14: If no improvement, escalate to CSM manager. Consider executive outreach.
Risk Type: Sponsor Change
Day 0:  Congratulate the departing champion. Ask for intro to successor.
Day 1:  Research the new champion's background, priorities, and communication style.
Day 3:  Send a "new leader brief" — 1-page summary of what's in place and why.
Day 7:  Schedule a relationship-building call with the new champion. Bring CSM + AE.
Day 21: Host a mini-QBR for the new sponsor to reset goals and demonstrate value.
Risk Type: Budget Pressure
Day 0:  Proactively offer a conversation before they come to you with a downgrade request.
Day 2:  Prepare a ROI summary. Quantify the cost of churning vs. staying (migration cost, retraining).
Day 5:  Present options: pause, downgrade, flexible payment terms. Give them control.
Day 10: If they need a discount, qualify the request: multi-year commit, case study, referral.
        Never discount without something in return.
Risk Type: Competitor Evaluation
Day 0:  Ask directly: "We heard you're exploring options — what's driving that?"
        Do not be defensive. Listen.
Day 2:  Share a competitive comparison if you have one. Focus on TCO, not features.
Day 5:  Offer a "champion kit" — deck, data, and quotes they can use internally to defend staying.
Day 10: Bring in AE for a value conversation with the economic buyer.
Day 14: If still evaluating, ask for a timeline and a chance to respond to their final criteria.
Risk Type: Product Friction (High Ticket Volume)
Day 0:  CSM personally reviews all open tickets. Escalate blockers to product/eng.
Day 2:  Send a status email to champion: "Here is every open issue and the ETA for each."
Day 5:  Weekly check-in until all critical issues are resolved.
Day 21: Post-resolution: send a "what changed" summary + ask for NPS.
Step 4: Executive Escalation Criteria

Escalate to VP CS or CEO when:

  • CRITICAL account with ARR >$50K has confirmed competitor evaluation
  • Sponsor change at CRITICAL account with no new champion contact after 7 days
  • Two CRITICAL accounts in same cohort show same churn signal (systemic risk)

Delivery

Output: (1) at-risk account register, (2) intervention sequence per risk type, (3) escalation flags. Prioritize by ARR x urgency. If output exceeds 40 lines, delegate to /atlas-report.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn of jeremylongshore/tons-of-skills-marketplace.

Open the folder on GitHubat commit cfae287

Compare with similar skills

Keep Churn next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Keep Churn compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Keep Churn this skilljeremylongshore/tons-of-skills-marketplace2.8k—~1.6kAutomated safety check: NotesMIT
Biz CRM Strategyasgard-ai-platform/skills242—~2.2kAutomated safety check: PassMIT
Customer Supportericrisco/rsc-harness180—~2.9kAutomated safety check: PassMIT
Retentionericrisco/rsc-harness180—~2.8kAutomated safety check: PassMIT
Churn Analysisshawnpang/startup-founder-skills343—~2.3kAutomated safety check: PassMIT
Cs Health Scorecardmohitagw15856/pm-claude-skills1.4k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Biz CRM Strategy

    asgard-ai-platform/skills

    Customer relationship management strategy — integrated framework with six pillars: customer segmentation (RFM/CLV), journey orchestration (cross-channel), CDP technology stack, loyalty-program…

    242 GitHub stars~2.2k tokensUpdated 4 mo ago
    Sales & SupportAuto-check passed
  • Customer Support

    ericrisco/rsc-harness

    A skill your agent uses when a live support ticket needs triage (intent, P1–P4 priority, SLA clock), an on-voice reply, not a raw template, de-escalation of an angry or churn-risk customer, or…

    180 GitHub stars~2.9k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Retention

    ericrisco/rsc-harness

    A skill your agent uses when revenue is leaking out the bottom of the funnel and you need a program to keep, score and win back customers — a customer health score, NPS, catching churn signals…

    180 GitHub stars~2.8k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Churn Analysis

    shawnpang/startup-founder-skills

    When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores, design save plays, or create win-back campaigns.

    343 GitHub stars~2.3k tokensUpdated 6 mo ago
    Sales & SupportAuto-check passed
  • Cs Health Scorecard

    mohitagw15856/pm-claude-skills

    Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.

    1.4k GitHub stars~2.4k tokensUpdated yesterday
    Sales & SupportAuto-check passed
  • Youtube Search

    ZeroPointRepo/youtube-skills

    A skill your agent uses when the user wants to find YouTube content on any topic: searching for videos or channels, finding creators who cover a subject, discovering tutorials, talks, or expert…

    1k GitHub starsUsed in 1 repo~1.8k tokens
    Sales & SupportAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated today
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated today
    Auto-check passed

Categories

Questions about Keep Churn

What does Keep Churn do?

Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Keep Churn is an agent skill from jeremylongshore/tons-of-skills-marketplace. Churn risk identification and intervention — scans health signals for at-risk accounts, classifies risk level (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type.

When should I use Keep Churn?

Keep Churn fits situations like: asked to find at-risk accounts; who might churn; build a churn prevention plan; identify churn signals.

How do I install Keep Churn in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill keep-churn -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/keep-churn in your project. Claude Code loads it when a task matches its description.

How do I install Keep Churn in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill keep-churn -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/bundle/revenue-team/skills/keep-churn in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/keep-churn in your project. Codex loads it when a task matches its description.

Can I use Keep Churn in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill keep-churn -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/keep-churn, .gemini/skills/keep-churn, .github/skills/keep-churn and .opencode/skills/keep-churn in your project.

What does Keep Churn need to run?

SKILL.md names no scripts, command-line tools or credentials: Keep Churn is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Bash, Glob, Grep, AskUserQuestion.

Does Keep Churn access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Keep Churn safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Keep Churn use?

Keep Churn is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Keep Churn use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Keep Churn?

Skills that share tags, products or a category with Keep Churn: Biz CRM Strategy (asgard-ai-platform/skills, 242 stars), Customer Support (ericrisco/rsc-harness, 180 stars), Retention (ericrisco/rsc-harness, 180 stars) and Churn Analysis (shawnpang/startup-founder-skills, 343 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Keep Churn?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.