Close the books faster — then tell the story behind the numbers
Orchestrate the close, explain the variances, and turn the numbers into a story — with five skills.
Churn is cheaper to prevent than to win back. Five free Agent Skills — churn analysis, QBRs, onboarding, returns prevention, and support resolution — form a retention stack that catches at-risk customers early. Learn the frameworks and run them in Claude.
Free to try. One click loads the skill into Claude or ChatGPT, with no account and no setup.
Every business obsesses over acquiring customers; far fewer systematically keep them. That’s backwards. Acquiring a new customer costs several times more than retaining an existing one, existing customers spend more over time, and — crucially — churn compounds against you: every point of monthly churn is a leak that grows as you scale. A retention program is often the cheapest growth you can buy.
The reason teams under-invest is that retention feels reactive — you find out a customer is leaving when they tell you. The shift these skills enable is proactive: watch health signals, intervene early, and design the onboarding, reviews, and support experiences that keep customers by default. Retention stops being a fire drill and becomes a system.
The skill isn’t magic. It encodes proven frameworks anyone can learn. Here’s the method itself, so you understand what it’s doing for you.
You can’t save a customer you don’t know is leaving. The core of proactive retention is a taxonomy of early-warning signals across three types. Usage signals: a >30% usage drop, key-feature abandonment, or the admin not logging in for two weeks. Engagement signals: no response to your CSM for 21 days, a declined QBR, a falling CSAT trend. Business signals — the most severe: the champion left, layoffs announced, an acquisition in the news.
Each signal carries a risk level (medium → high → critical), and combined they produce a risk score you can act on. The point is to move retention from reactive firefighting — noticing when the cancellation email arrives — to proactive health management, where you intervene weeks earlier, when a save is still possible.
For e-commerce, returns are a retention problem in disguise — a bad return experience is a churned customer. The fix starts by classifying why returns happen: fit/size (30–40% of returns — the biggest bucket, solved with size guides), not as expected (20–30% — better images and descriptions), quality (10–15%), wrong item (fulfillment), and changed mind (impulse). Each reason has a prevention strategy — and the insight is that you cut returns with better information, not restrictive policies (which just cut sales too).
Benchmarks make it concrete: apparel runs 25–30% returns (excellent is under 15%), footwear 30–35% (under 20%), electronics 10–15% (under 5%). Knowing your category’s benchmark tells you how much headroom there is.
Use any one on its own, or chain them. Each hands its output to the next. Every one is free in the public library.
Spots at-risk customers from early-warning signals, then deploys the right save motion or win-back — the anchor of proactive retention.
Gets new customers to value fast with milestones and health scoring — because most churn is decided in the first 90 days.
Builds quarterly business reviews that prove value and surface expansion — the relationship ritual that pre-empts churn at renewal.
The e-commerce edge of retention — cuts returns (and the churn they cause) through better pre-purchase information, not restrictive policies.
Resolves support inquiries with the right tone and authority, so a bad service moment doesn’t become a lost customer.
Any time keeping customers matters more than it’s getting attention — which, for most subscription and e-commerce businesses, is always. Especially when churn is creeping up, onboarding is inconsistent, or renewals feel like a scramble.
It turns retention from something you react to into something you run. The stack catches at-risk customers early (churn-prevention-analyst), gets new ones to value before they can churn (customer-onboarding-playbook), proves value at the renewal ritual (qbr-architect), and — on the e-commerce side — cuts the returns and support failures that quietly lose customers (returns-prevention-strategist, customer-inquiry-resolver).
Retention is the highest-leverage growth lever most teams under-invest in: keeping a customer is far cheaper than acquiring one, and a small churn improvement compounds. These five free skills give you the frameworks to do it systematically instead of by gut feel.

Real prompts, and what the skill hands back.
“This account’s usage dropped 40% and they declined our last QBR. What’s the churn risk, and what save motion should we run?”
A risk assessment flagging the high-risk usage and engagement signals, plus a recommended save motion and offer framework from the intervention playbook.
“Our apparel return rate is 32%. Break down the likely reasons and give me the highest-impact prevention moves.”
A return-reason breakdown against the taxonomy and category benchmark, with prevention strategies ranked by impact (starting with sizing).
A risk-signal taxonomy catches churn weeks before the cancellation, while a save is still possible.
Milestone onboarding with health scoring — most churn is decided before month three.
QBRs prove value and surface expansion, so renewal isn’t a surprise.
Returns fall when you inform buyers better, not when you make returns harder.
Resolving inquiries well keeps a bad day from becoming a lost customer.
They cover the customer lifecycle: onboard to value → monitor health and catch risk → review value at renewal → and, for commerce, prevent the returns and support failures that leak customers. Run the whole stack, or start with the one leak that’s costing you most.
Retention data also feeds the top of the funnel: what makes customers stay tells you who to acquire — pairs naturally with synthetic-persona research.
Run the skills in Claude and customize each with your product, signals, and thresholds:
Already connected your library to Claude? Tell it: “Use the churn-prevention-analyst skill (and the others above) from the agentman_skills MCP server.”
Not connected yet? The Try in Claude / ChatGPT button loads the first one from the public library, with no setup. Or connect your library.
Click “Try in Claude / ChatGPT” above, or — if you’ve connected your library — tell Claude: “Use the churn-prevention-analyst skill from the agentman_skills MCP server.” Add the others by slug as you go.
Run churn-prevention-analyst against your customer data — it maps the usage, engagement, and business signals into a risk score and recommends a save motion.
Use customer-onboarding-playbook to design milestone-based onboarding with health scoring, so new customers reach value before they can churn.
Run qbr-architect to build value-proving quarterly reviews that surface expansion and defuse renewal risk early.
On the e-commerce side, run returns-prevention-strategist to attack your biggest return reasons, and customer-inquiry-resolver so support resolves issues without losing the customer.
That’s a customer-success and CX function most teams staff up for — assembled from five free skills you keep and tune.
One click loads the skill into Claude or ChatGPT. No account, no setup.
No. Run just churn-prevention-analyst to triage at-risk accounts, or returns-prevention-strategist for an e-commerce returns push. Chained, they cover the whole retention lifecycle, but each works on its own.
The churn-prevention skill encodes a taxonomy of early-warning signals — usage drops, engagement declines, and business events like a champion leaving — each with a risk level. Together they produce a risk score, so you intervene weeks before the cancellation instead of after.
No — that’s the key insight. Returns fall when you give buyers better information (accurate sizing, images, descriptions), not when you make returns harder. Better information actually improves conversion while cutting returns.
No. Click “Try in Claude / ChatGPT” above and the first skill loads from our public library — no setup. Clone the skills to customize the signals and thresholds and share them.