Agent skill

churn-risk-detector

Scan support tickets, Slack channels, NPS scores, and usage patterns to flag accounts showing early churn indicators. Produces a weekly risk scorecard with severity tiers, root cause hypotheses, and suggested save plays per account. Designed for seed/Series A teams where the founder or a single CSM manages all accounts manually.

gooseworks-aigithub.com/gooseworks-aiGitHub ↗
claude-codecodexcursorMIT
Install
npx skills add gooseworks-ai/goose-skills --skill churn-risk-detector --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 8 KB
Bundled scripts: none
Path: skills/research/composites/churn-risk-detector/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,091
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Churn Risk Detector Surface accounts at risk of churning before it's too late. Aggregates signals from support, communication, and usage patterns into a scored risk report with specific save actions. **Built for:** Early-stage teams with no CS platform (no Gainsight, no ChurnZero). You have a spreadsheet of customers, a Slack channel, and a support inbox. This skill turns those raw signals into an actionable churn risk list. ## When to Use - "Which customers are at risk of churning?" - "Run the weekly churn risk scan" - "Flag accounts I should worry about" - "Who haven't we heard from in a while?" - "Produce a customer health report" ## Phase 0: Intake ### Account Data 1. **Customer list** — CSV or sheet with: company name, primary contact email, contract value (MRR/ARR), contract start date, renewal date (if known) 2. **Product/service type** — What are they paying for? (Helps calibrate expected engagement) ### Signal Sources (provide what you have) 3. **Support tickets** — Export from Intercom, Zendesk, or email (CSV with: customer, date, subject, status, resolution time) 4. **Slack channel history** — Customer Slack channel or shared channel messages 5. **NPS/CSAT scores** — R

What's inside
Steps it walks through
  1. When to Use
  2. Phase 0: Intake
  3. Account Data
  4. Signal Sources (provide what you have)
  5. Calibration
  6. Phase 1: Signal Extraction
  7. 1A: Support Signal Analysis
  8. 1B: Communication Signal Analysis
  9. 1C: Usage Signal Analysis (if data available)
  10. 1D: Commercial Signal Analysis
  11. Phase 2: Risk Scoring
  12. Scoring Model
  13. Risk Tiers
  14. Phase 3: Save Play Generation
Ships with 1 file
  • skill.meta.json
More from goose-skills
All skills →
About this skill
What does the churn-risk-detector skill do?

Scan support tickets, Slack channels, NPS scores, and usage patterns to flag accounts showing early churn indicators. Produces a weekly risk scorecard with severity tiers, root cause hypotheses, and suggested save plays per account. Designed for seed/Series A teams where the founder or a single CSM manages all accounts manually.

How do I install it?

Run `npx skills add gooseworks-ai/goose-skills --skill churn-risk-detector --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going