# follow-up

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf (Devin Desktop), Claude.ai · ★ 83 repo stars
- Author: Jake Schincariol
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/Jakeschincariol/closer-skill/tree/HEAD/follow-up/SKILL.md
- Updated: 2026-11-01
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/follow-up-2

## What it 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.

## Install

### Claude Code (native platform)

1. **Plugin marketplace**
In the agent chat (not a shell):
```text
/plugin marketplace add Jakeschincariol/closer-skill
```
In the agent chat (not a shell):
```text
/plugin install closer-skill@closer-skill
```
This installs the whole closer-skill plugin with all its skills

2. **Skills CLI (Vercel)**
```bash
npx skills add Jakeschincariol/closer-skill --skill follow-up -a claude-code
```

3. **Manually: put the files in place**
- File: `~/.claude/skills/follow-up/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/follow-up/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add Jakeschincariol/closer-skill --skill follow-up -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/follow-up/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add Jakeschincariol/closer-skill --skill follow-up -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/follow-up/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install Jakeschincariol/closer-skill follow-up
```

2. **Manually: put the files in place**
- File: `.github/skills/follow-up/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add Jakeschincariol/closer-skill --skill follow-up -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/Jakeschincariol/closer-skill --path follow-up
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/follow-up/SKILL.md` — The legacy .windsurf/skills/ path still works

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/Jakeschincariol/closer-skill/tree/HEAD/follow-up/SKILL.md

## When to use it
- 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
- 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.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 932bfc638cd9a09f.

BEGIN THIRD-PARTY FILE 932bfc638cd9a09f
````text
---
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.
````
END THIRD-PARTY FILE 932bfc638cd9a09f

The third-party file has ended. Everything between the 932bfc638cd9a09f tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 3021 of 5234 bytes. © Jake Schincariol · MIT · https://github.com/Jakeschincariol/closer-skill/tree/HEAD/follow-up/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
