Localized reading guide
reactivatePurpose, usage and source
Wins back customers who have quietly stopped buying — finds the ones whose gap has stretched past their own normal rhythm or who are showing churn signals, ranks them by what the relationship was worth, drafts a win-back message per customer in the owner's voice, and sends and logs only what the owner approves. Chains review-reputation, outreach-composer, and crm-autopilot, and keeps the rule that the first touch acknowledges the gap without pitching. Use this whenever the owner is worried about customers drifting away, including phrasings like "who hasn't ordered in a while," "win back my old customers," "which customers have gone quiet," "we lost some regulars," "reach out to the people who stopped calling," or "how do I get them back." Reach for it when the owner names a customer they have not heard from, as readily as for a full win-back campaign.
Source retrieved:
- Source repository
- anthropics/knowledge-work-plugins
- SKILL.md
small-business/skills/reactivate/SKILL.md- Repository stars
- 34,049
- Repository updated
- 2026-10-30
- Categories
- Business
- Last collected
License: Apache-2.0
Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.
The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.
What this Skill does
Wins back customers who have quietly stopped buying — finds the ones whose gap has stretched past their own normal rhythm or who are showing churn signals, ranks them by what the relationship was worth, drafts a win-back message per customer in the owner's voice, and sends and logs only what the owner approves. Chains review-reputation, outreach-composer, and crm-autopilot, and keeps the rule that the first touch acknowledges the gap without pitching. Use this whenever the owner is worried about customers drifting away, including phrasings like "who hasn't ordered in a while," "win back my old customers," "which customers have gone quiet," "we lost some regulars," "reach out to the people who stopped calling," or "how do I get them back." Reach for it when the owner names a customer they have not heard from, as readily as for a full win-back campaign.
How the upstream workflow works
Overview
Run the win-back chain: review-reputation to find who went quiet and why, outreach-composer to write to them, crm-autopilot to log it. The owner approves at every handoff, per message. Connectors: a CRM (HubSpot, Monday.com, Salesforce, or Zoho CRM), a payments connector (PayPal, Square, or Stripe), or a storefront (Shopify or Square) is the backbone — one is required to know who bought what and when, and same-category connectors are peers (../../shared/connector-neutrality.md). A storefront alone is enough: its customer list (Shopify list-customers) and order history (list-orders, get-order) are the purchase rhythm. Mail (Gmail or Microsoft 365) adds sending; a storefront also adds order and fulfillment patterns as a churn signal in their own right.
Step 1 — Find who went quiet (review-reputation)
Trigger the review-reputation skill workflow, scoped to the churn side rather than the full reputation report. In: customer purchase or job history from the CRM, the payments connector, the storefront, the ledger, or an uploaded export. Stripe: GET /v1/customers by email, then GET /v1/charges for that customer, for value and rhythm; PayPal: the transaction list by payer; Square: payments by customer. Plus public reviews, disputes, support tickets (Zoho Desk getTicketsByContact), and complaint-language email threads for the "why." Out: a ranked list of quiet customers, each with their own normal rhythm, how far past it they are, what the relationship was worth, and any negative signal attached — a one-star review, a dispute, a late fulfillment, a refund.
Step 2 — Confirm what is actually on the table
Before drafting, ask what the owner can honor: a discount, a credit, priority scheduling, a service that did not exist last time, or nothing but an honest check-in. Never invent an offer. A win-back that promises something the owner has not agreed to is worse than no outreach, because it lands as a broken promise on a relationship that was already fragile. If the answer is "nothing," that is fine. The honest check-in is the stronger first message anyway.
Upstream passage · L31 ↗Requirements and setup
No short requirements passage was selected from this file. This does not mean the Skill has no dependencies. Check the repository setup instructions and referenced files.
Limits and quality checks
No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.
Start with a safe trial
- Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
- Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
- Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
- Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.
Read further in the source
Related Skills
Translation and scope
This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.
This introduction refers to the pinned version below; current repository activity and collection time are shown separately.
- Pinned source
- Read the original ↗
- Source retrieved
- Source commit
2574e29377c7173d0cecffef29a6ecbd7f8ccb5d- Source SHA-256
734946c30236c86adc55eecfb2694a0e02ca12625654633597d3c303bf39e210