A Claude Skill that runs each morning, pulls every account that crossed a churn-risk threshold in the last 24 hours, and posts a one-page summary to a Slack channel: account, ARR at risk, what changed, owner, and the recommended first action. Replaces the noisy Gainsight digest no one reads.

What you’ll need

Gainsight with risk-score history and a defined churn-risk threshold
Slack workspace and a destination channel
Claude Code or Claude.ai with the Skill installed
A daily run cadence (cron, n8n, or a Claude scheduled task)

Setup

Define the threshold. Decide what “crossed into risk” means — for example, health score dropped below 50, or risk-score moved from medium to high, or ARR-weighted risk exceeded a band.
Install the Skill. Drop churn-risk-summary.skill into ~/.claude/skills/. Set GAINSIGHT_TOKEN and SLACK_WEBHOOK.
Configure scope. Edit references/scope.md with which segments to include (some teams only want enterprise; others want all). Define the reasonable stop-loss for “actionable” — accounts above $X ARR.
Schedule the run. Run at 7am local time. Claude posts to #csm-daily-risk.
Iterate on signal-to-noise. First two weeks, expect the digest to be noisy. Tune the threshold and segment scope until the digest contains only accounts a human should look at today.

How it works

The Skill queries Gainsight for risk-score deltas in the last 24 hours and filters to accounts that crossed the threshold. For each, it pulls the most recent timeline events that explain the change: a usage drop, a support escalation, a sponsor change, a missed QBR.

Claude writes the digest in a tight format: one line per account, with ARR, owner, the change driver, and one suggested action. Accounts are sorted by ARR at risk descending. The digest is capped at 15 accounts; if more crossed, it links to the full list and shows a count.

The recommended action is concrete: “Call the CFO this week before the renewal kickoff,” not “engage stakeholder.” Specificity is the value.

Watch-outs

Threshold sensitivity. Set it too tight, the digest is empty. Set it too loose, the digest is ignored. Aim for 5-15 accounts per day.
Owner accuracy. If account ownership is stale, the digest pings the wrong CSM. Include a self-serve fix link in the post.
Action quality. A vague suggested action is worse than none. If Claude can’t recommend something specific, return “needs human review” instead.

Stack

Gainsight — risk-score source and account context
Claude — synthesis and Slack-ready formatting