win-back — Claude Code skill: what it does and how to install
The win-back Claude Code skill finds deals ready for another contact and drafts a brief check-in. It runs on request about old or silent leads, or once a week.
MIT ★ 83 updated 2026-11-01
/plugin marketplace add Jakeschincariol/closer-skill
/plugin install closer-skill@closer-skillWhat win-back does
The skill selects lost deals marked for timing, budget, indecision or no decision, along with open deals that stopped responding after three follow-ups. For most lost deals, it waits 60 days or uses the requested return date; deals won by a competitor wait at least 180 days and get only a friendly check-in. Open deals enter the list after 30 inactive days once follow-ups are exhausted.
Run list to see ready and later deals, then draft to create a message under 60 words. The agent asks for approval of each specific message before sending. Approval creates a Gmail draft for the user to send, or the message can go through the Gmail connector. The script requires python3.
The skill skips people who declined, unsubscribed or opted out of contact. It does not send another win-back after an unanswered attempt. Replies move into regular follow-up with /follow-up reply and /scheduler.
What it helps with
- find lost deals that are ready for another contact
- draft a check-in based on why a deal stalled
- surface open deals that went quiet after follow-ups
- exclude contacts who declined or unsubscribed
Example prompts for the agent
- List the deals that are ready for another check-in.
- Draft a message for deal
lakeline-website. - Find leads that went quiet after all follow-ups.
How to install win-back
1Plugin marketplace
/plugin marketplace add Jakeschincariol/closer-skill/plugin install closer-skill@closer-skillThis installs the whole closer-skill plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/closer-skill --skill win-back -a claude-code3Manually: put the files in place
~/.claude/skills/win-back/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/win-back/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/closer-skill --skill win-back -a codex2Manually: put the files in place
.agents/skills/win-back/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/closer-skill --skill win-back -a cursor2Manually: put the files in place
.cursor/skills/win-back/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/closer-skill win-back2Manually: put the files in place
.github/skills/win-back/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/closer-skill --skill win-back -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/closer-skill --path win-backManually: put the files in place
.devin/skills/win-back/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about win-back
How do I install win-back in Claude Code?
Add the marketplace with /plugin marketplace add Jakeschincariol/closer-skill, then install the skill with /plugin install closer-skill@closer-skill.
What does win-back do?
It finds deals due for another contact and drafts a short message based on the reason they stalled or were lost. Each message needs separate approval before sending.
What does win-back need to run?
The script requires python3. Sending uses a Gmail draft in the user's account or the Gmail connector.
Source text
SKILL.md · MIT
---
name: win-back
description: >-
Win-Back. Brings back the deals that went quiet. Finds lost deals worth one more try (bad timing,
budget, still thinking, no decision) once enough time has passed or on the date they asked you to
come back, plus open deals that went silent after every follow-up, and writes one short, honest
check-in from the reason it was lost. One win-back per deal, never to anyone who said no or
unsubscribed. Use when the user says "win back", "revive old deals", "follow up on lost deals",
"who went quiet", "re-engage", "dead leads", or once a week.
argument-hint: "[list | draft <deal>]"
---
# win-back
"Not now" is not "no". The Win-Back skill remembers who said not now and comes back once, at the right
time, with a reason to talk. It never chases anyone who said no.
`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).
```bash
python3 "${CLAUDE_SKILL_DIR}/winback.py" list --today 2026-10-29
python3 "${CLAUDE_SKILL_DIR}/winback.py" draft --deal lakeline-website --today 2026-10-29
python3 "${CLAUDE_SKILL_DIR}/winback.py" record --deal lakeline-website --text-file /tmp/w.txt \
--approval "yes" --at 2026-10-29T10:00
```
## Who it tries, and when
- **Lost for timing, budget, "let me think" or no decision:** 60 days after it was lost, or on the deal's
own `revisit` date if they named one ("ask again in the fall": set `revisit` on the deal).
- **Lost to someone else:** not before 180 days, and only a friendly "how's it going".
- **Open but silent:** no activity for 30 days after `/follow-up` used all 3 follow-ups.
- **Never:** anyone who said no, unsubscribed or is do-not-contact. Never twice: one win-back per deal,
and if there is no reply, that is the end. Another try only after they write back, and 90 days later.
## Steps, once a week
1. `winback.py list`. Read the READY ones to the user with why, biggest first. Mention LATER ones with their date.
2. For each the user wants, `winback.py draft`. Make it more specific with one true, new thing if you have
one (a new plan, a result for a similar business). Keep it under 60 words, and keep the easy out:
"If not, no problem at all, just say so and I'll leave it."
3. Ask: "Send this to Tom at Lakeline Roofing? Reply yes or no."
4. On a yes: a Gmail draft from the user's account, which the user sends (or sent through the Gmail
connector right after that yes). Then `winback.py record --approval "<their yes>"`. The deal opens again.
5. If they reply, it is a conversation: `/follow-up reply`, then `/scheduler`.
## Example
Tom Becker at Lakeline Roofing liked the idea in July but said it was roofing season: "ask again in the
fall." Lost on Aug 10 for timing. On Oct 29 `list` shows READY, and the draft reads: "Hi Tom, when we spoke
you said the timing wasn't right until the fall. Is now any better for website + reviews widget? If not,
no problem at all, just say so and I'll leave it." Elena Ruiz at Mesa Verde Med Spa asked to be removed, so
she shows as NEVER. (Illustrative: both businesses are fictional.)
## What it never does
- Never emails anyone who said no, unsubscribed or is do-not-contact.
- Never sends a second win-back after an unanswered first one.
- Never invents a reason to write ("just saw your post", "my colleague mentioned you") that is not true.
## Consent and truth
- Nothing is sent, booked or signed without the user's explicit yes for that exact message, invite or
document. Claude drafts, the user says "yes", then it goes out from the user's own accounts.
One yes per message. Never "yes to all".
- Stop at the first "no" or any sign of disinterest. A request to stop is honoured forever, across every skill.
- Every email is honest about who is writing and keeps a plain way to opt out. Opt-outs are honoured forever.
- Never invent a number, a result, a client, a review or a deadline.
© Jake Schincariol · MIT · Jakeschincariol/closer-skill