Skip to main content
skill CX Codex

follow-up · jakeschincariol/closer-skill — Claude Code skill: what it does, how to install

This Claude Code skill tracks follow-up dates and drafts messages for contacts who have not replied. It runs on request or as part of a morning check.

MIT ★ 83 updated 2026-11-01

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add Jakeschincariol/closer-skill
/plugin install closer-skill@closer-skill
Open on GitHub

What follow-up does

The skill reads closer/pipeline.json and groups contacts by status: due for a follow-up, waiting on your reply, booked, or stopped. It drafts each message and waits for approval before recording a sent email.

The followup.py script stops after a refusal or booked call, after three follow-ups, or 30 days without a reply. The second message needs a new, specific reason to write. A contact's reply moves the conversation to YOUR TURN. The script never sends email by itself.

The morning routine starts with a reply sync through /record-keeper. Python 3 and closer/pipeline.json are required; creating a Gmail draft uses the Gmail connector.

What it helps with

  • find contacts due for a follow-up
  • draft a message with a specific new reason
  • stop outreach after a refusal or booked call
  • sort replies into the next action

Example prompts for the agent

  • Show me who needs a follow-up today.
  • Draft a follow-up for Dana with a specific new reason to write.
  • Dana replied that Thursday at two works. Process her reply.

How to install follow-up

1Plugin marketplace

/plugin marketplace add Jakeschincariol/closer-skill
/plugin install closer-skill@closer-skill

This installs the whole closer-skill plugin with all its skills

2Skills CLI (Vercel)

npx skills add Jakeschincariol/closer-skill --skill follow-up -a claude-code

3Manually: put the files in place

~/.claude/skills/follow-up/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/follow-up/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about follow-up

How do I install follow-up in Claude Code?

Add the marketplace with /plugin marketplace add Jakeschincariol/closer-skill, then install it with /plugin install closer-skill@closer-skill.

What does follow-up do?

It tracks follow-up dates, drafts messages, and records them after approval. It stops after a refusal, a booked call, three follow-ups, or 30 days without a reply.

What does follow-up need to run?

It requires Python 3 and closer/pipeline.json. The morning reply sync uses /record-keeper, and creating Gmail drafts uses the Gmail connector.

Source text

SKILL.md · MIT
---
name: follow-up
description: >-
  Follow-Up. Keeps following up until a call is booked, then stops. Every morning it reads
  closer/pipeline.json and says who is due a follow-up today, who replied and is waiting on you,
  who booked, and who is stopped and why. Drafts each follow-up (a bump, then something useful,
  then a polite last note), waits for your yes, logs it, and stops at the first "no", the moment
  a call is booked, after 3 follow-ups or 30 days. Use when the user says "follow up",
  "who do I need to follow up with", "they haven't replied", "chase", "nudge", "bump this",
  "they replied", or every morning.
argument-hint: "[due | draft <contact> | reply <contact>]"
---

# follow-up

Most deals are lost to silence, not to "no". This skill makes sure nobody is forgotten and nobody
is pestered. It drafts; it never sends by itself.

`${CLAUDE_SKILL_DIR}` below is this skill's folder (where this SKILL.md lives).

```bash
python3 "${CLAUDE_SKILL_DIR}/followup.py" due --today 2026-10-21
python3 "${CLAUDE_SKILL_DIR}/followup.py" draft --contact dana-harbor-lane --today 2026-10-21
python3 "${CLAUDE_SKILL_DIR}/followup.py" draft --contact dana-harbor-lane --today 2026-10-23 \
    --hook "here's a 1-minute mockup of what online booking could look like for Harbor Lane."
python3 "${CLAUDE_SKILL_DIR}/followup.py" record --contact dana-harbor-lane --text-file /tmp/f.txt \
    --approval "yes" --at 2026-10-21T09:00
python3 "${CLAUDE_SKILL_DIR}/followup.py" reply --contact dana-harbor-lane \
    --text "Sorry, crazy week! Thursday at 2 works." --at 2026-10-27T11:48
python3 "${CLAUDE_SKILL_DIR}/followup.py" stop --contact <id> --said "Please remove me from your list."
```

## The rules (per person, across every channel)

1. **Stop at the first "no"** or any sign of disinterest ("not interested", "no thanks", "we're all
   set", "please remove me"). An unsubscribe goes on the suppression list, and no skill emails them again.
2. **Stop the moment a call is booked.** That is the job. `/scheduler` and `/sales-coach` take over.
3. **A reply is your turn.** Answering them is a conversation, never a "follow-up".
4. **At most 3 follow-ups** after the opening, and the third one says it is the last.
5. **Nothing after 30 days** from the opening without a reply. `/win-back` may try once, much later.

`draft` refuses to draft and `record` refuses to log anything that breaks a rule.

## The cadence

Follow-up 1 is two days after the opening, follow-up 2 two days after that, follow-up 3 four days after
that. A date on a weekend moves to Monday. The reel's thread: Mon Oct 19 (opening), Wed Oct 21, Fri Oct 23,
Tue Oct 27.

1. **Follow-up 1, the bump.** One line: "just bumping this up in case it got buried."
2. **Follow-up 2, give something.** A mockup, a number, a short idea for them. `--hook` is that one new,
   true, specific thing. Without a hook there is no follow-up 2.
3. **Follow-up 3, the last note.** Offer a day for a call and say it is the last email. Either answer is fine.

## Steps, every morning

1. Run `/record-keeper` sync first so replies are on the board.
2. `followup.py due`. Read it to the user grouped as it prints: DUE NOW, YOUR TURN, WAITING, BOOKED, STOPPED.
3. For each DUE NOW, `followup.py draft`. Fill every `[fill: ...]`. Show it: "Send this follow-up to Dana?
   Reply yes or no." One message per question.
4. On a yes: a Gmail draft in the same thread from the user's account, which the user sends (or sent through
   the Gmail connector right after that yes). Then `followup.py record --approval "<their yes, word for word>"`.
5. For each YOUR TURN: when they gave a time, hand it to `/scheduler` (`slots.py parse`), confirm with the
   `confirm-time` template, and book. When they said no, `followup.py reply` with their words: it stops
   everything and marks the deal lost.

A scheduled morning run may list and draft. It never sends: nobody is there to say yes.

## Example from the reel

Dana Ortiz never answered the opening. Follow-up 1 on Wed Oct 21: "just bumping this up in case it got
buried." Follow-up 2 on Fri Oct 23: the 1-minute mockup. Follow-up 3 on Tue Oct 27: "should I close the loop
on this, or is Thursday good for a quick call?" At 11:48 AM she replied, "Sorry, crazy week! Thursday at 2
works." `reply` moved her to YOUR TURN; the call was booked, and from then on she got no more follow-ups.
(Illustrative: Dana and Harbor Lane Dental are fictional.)

## What it never does

- Never sends, and never records a message that did not go out.
- Never follows up after a no, after a booking, after 3 follow-ups or after 30 days.
- Never uses guilt, fake urgency, a fake "Re:" or a made-up reason to write.

## 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 keeps the opt-out line from the opening thread. Opt-outs are honoured forever.
- Never invent a number, a result, a client, a review or a deadline.

© Jake Schincariol · MIT · Jakeschincariol/closer-skill

Similar skills

All skills for Marketing and content →

follow-up by other authors comes first.

follow-up humanizerai follow-up is a Claude Code skill that drafts emails to people who did not reply to an earlier message. Give it the original context, elapsed days, and follow-up number. CX Codex +1 522installs follow-up Jake Schincariol This Claude Code skill tracks follow-ups after a pitch or offer. It lists deals due for a message, drafts one, then waits for approval before sending. CX Codex +1 ★ 92repo stars sales-meeting-recap Maya-Beth Finotti sales-meeting-recap turns your sales call notes into a recap email: next steps with owners and dates, the buyer's pain in their own words. Nothing gets invented along the way. CX Codex +1 33,600installs spark-persona-sales-rep readdle spark-persona-sales-rep is a Claude Code skill that tracks client threads, flags unreplied emails and pulls context before a call. CX Codex +1 320installs sales official Anthropic sales is a sales plugin for Claude Code that prepares calls, reviews deals, and builds forecasts. Skills run from a matching request or by name, such as /sales:call-summary. ★ 36,654repo stars lead-triage ilyautov lead-triage scores incoming CRM leads by engagement, ICP fit and urgency, then returns a ranked who-to-call-today list with talking points. Triggers on prompts like "triage the leads" or "who do I call first". CX Codex +1 ★ 38repo stars sales-pipeline-coverage-modeling Maya-Beth Finotti sales-pipeline-coverage-modeling models pipeline coverage ratios against sales quota using historical conversion rates. Helps RevOps and sales leaders identify pipeline gaps and plan deals. CX Codex +1 34,600installs outreach-specialist ognjengt outreach-specialist builds a personalized outreach sequence for cold email, LinkedIn DMs and follow-ups. Useful when you need a stranger to reply and book a call. CX Codex +1 1,400installs

From the same set12

The whole set →
researcher The researcher Claude Code skill gathers public business details and prepares a call brief. It activates when asked to research a contact or before a scheduled call. CX Codex +1 ★ 83repo stars scheduler The scheduler Claude Code skill schedules calls and checks calendar availability. It activates when a reply suggests a time or someone asks for open slots. CX Codex +1 ★ 83repo stars win-back 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. CX Codex +1 ★ 83repo stars record-keeper The record-keeper Claude Code skill logs emails and calls against CRM contacts. It responds to requests to sync an inbox, save call notes, or show a contact’s history. CX Codex +1 ★ 83repo stars contract-writer The contract-writer skill for Claude Code turns call notes and a proposal into a services agreement, then drafts an email to send it. After approval, it creates a PDF and records a returned signed copy as a won deal. CX Codex +1 ★ 83repo stars pipeline The pipeline Claude Code skill tracks deals on a shared CRM board. It displays stages and deal history, updates stages, and validates the data file after changes. CX Codex +1 ★ 83repo stars prospector The prospector Claude Code skill finds local businesses with gaps your offer could address and drafts tailored outreach. It responds to requests to find leads, build a prospect list, or write a cold email. CX Codex +1 ★ 83repo stars sales-coach The sales-coach Claude Code skill suggests responses to sales objections from call captions. It also flags buying signals and reviews the conversation afterward. CX Codex +1 ★ 83repo stars

Project sponsors

Companies that keep this analytics open