Skip to main content
skill CX Codex

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

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.

MIT ★ 92 updated 2026-11-06

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

What follow-up does

The skill tracks outreach after a pitch or offer, drafts the next email, and records replies. It runs followup.py with Python 3. It never sends on its own: after approval, the user sends the message or creates a Gmail draft in the existing thread.

The sequence ends when someone declines or books a demo, after the third follow-up, or after 30 days without a reply. A reply hands the conversation back to the user. The second follow-up needs a specific detail supplied through --hook; without one, the skill will not draft it. Dates that land on weekends move to Monday.

What it helps with

  • find deals due for follow-up after a pitch
  • draft the next message for a deal
  • record a reply and hand the conversation back
  • stop outreach after a decline or a booked demo

Example prompts for the agent

  • Show me which deals are due for follow-up today.
  • Draft the next email for the north-pier deal.
  • Record this reply for north-pier: they asked to see a demo tomorrow.

How to install follow-up

1Plugin marketplace

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

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

2Skills CLI (Vercel)

npx skills add Jakeschincariol/whale-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?

Run these commands in order: /plugin marketplace add Jakeschincariol/whale-skill, then /plugin install whale-skill@whale-skill.

What does follow-up do?

It tracks outreach after a pitch or offer, drafts follow-up emails, and logs replies. Messages are not sent without the user's approval.

What does follow-up need to run?

The script requires Python 3. After approval, the user can send the email themselves or use the Gmail connector.

Source text

SKILL.md · MIT
---
name: follow-up
description: >-
  Follow-Up. Keeps the deal moving. Tells you who is due today after a pitch or an offer, drafts the next
  note (a bump, something useful, a last note), waits for your yes, logs it, and stops at the first "no",
  the moment a demo is booked, after 3 follow-ups or after 30 days. Logs their replies and knows when it's
  your turn. 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", "they said no", or every morning.
argument-hint: "[due | draft <deal> | reply <deal> | stop <deal>]"
---

# follow-up

Big deals are lost to silence more often than to "no". Busy people don't answer the first email. 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-28
python3 "${CLAUDE_SKILL_DIR}/followup.py" draft --deal north-pier --today 2026-10-28
python3 "${CLAUDE_SKILL_DIR}/followup.py" draft --deal north-pier --today 2026-10-30 \
    --hook "here's what the demo looks like with a freight company's invoices."
python3 "${CLAUDE_SKILL_DIR}/followup.py" record --deal north-pier --text-file /tmp/f.txt --approval "yes" --at 2026-10-28T09:00
python3 "${CLAUDE_SKILL_DIR}/followup.py" reply --deal north-pier --text "Interesting. Can you show me tomorrow?" --at 2026-10-28T14:20
python3 "${CLAUDE_SKILL_DIR}/followup.py" stop --deal north-pier --said "Please remove me from your list." --at 2026-10-30
```

## 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 demo is booked.** That is the job.
3. **A reply is your turn.** Answering them is a conversation, never a follow-up.
4. **At most 3 follow-ups** after a pitch or an offer, and the third one says it's the last.
5. **Nothing after 30 days** without a reply.

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

## The cadence

Follow-up 1 is two days after the pitch or offer, follow-up 2 two days after that, follow-up 3 four days after that. A date on a weekend
moves to Monday.

1. **The bump.** Short: "just bumping this up in case it got buried."
2. **Give something.** One new, true, specific thing for them (`--hook`). Without a hook there is no follow-up 2.
3. **The last note.** Ask for a day, and say it's the last email. Either answer is fine.

## Steps, every morning

1. Check the inbox first, so replies are on the board: `followup.py reply` for each.
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 Renee? 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: if they want a demo, book it and `board.py move --stage demo-booked`. If they pushed back, `/objection-handler`. If they
   said no, `followup.py stop` 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's board

Renee Alvarez doesn't answer the pitch on Mon Oct 26. Follow-up 1 on Wed Oct 28: "Just bumping this up in case it got buried." At 2:20 PM she
replies, "Interesting. Can you show me tomorrow?" The deal moves to YOUR TURN, the demo is booked, and she gets no more follow-ups. Gwen Tate at
Harrow Line replies, "We're all set, thanks." The deal is lost, and she hears nothing else. (Illustrative: everyone here is 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 charged without the user's explicit yes for that exact message. 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 or a deadline.

© Jake Schincariol · MIT · Jakeschincariol/whale-skill

Similar skills

SKILL.md skills catalog →

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-up dates and drafts messages for contacts who have not replied. It runs on request or as part of a morning check. CX Codex +1 ★ 83repo stars follow-the-crypto UseOSINT follow-the-crypto — a skill for tracing cryptocurrency addresses and transactions across public blockchains through block explorers. CX Codex +1 1,800installs follow-through-overlapping dylantarre follow-through-overlapping teaches your coding agent how to handle momentum, drag, and staggered settling. Useful for UI micro-interactions, character movement, and kinetic typography. CX Codex +1 618installs signals-scout-pr-follow-up PostHog signals-scout-pr-follow-up — a Claude Code skill checks merged pull requests against post-deploy telemetry. It looks for the promised effect and regressions tied to a specific change. CX Codex +1 122installs follow-up-on-pr Factory-AI follow-up-on-pr takes an open pull request, rebases on the target branch, resolves reviewer comments, runs local verification, and pushes updates. CX Codex +1 117installs Follow Up Boss mindwear-capitian Connects Follow Up Boss to an MCP-compatible agent for CRM work. It can change or delete account data, so choose an access mode carefully. CX Codex +1 ★ 34repo stars follow-up-prompt-1 zhtyyx follow-up-prompt-1 is an SEO prompt for Claude Code that turns supplied evidence into a structured working document. It separates observations, assumptions, action items, and claims to verify. GP ChatGPT ★ 159repo stars

From the same set12

The whole set →
case-study A skill for Claude Code drafts a customer case study from real figures and the customer's own words. It runs when asked for a testimonial or customer story after delivery. CX Codex +1 ★ 92repo stars requirements The requirements Claude Code skill turns paying customers’ requests into a ranked feature list. It activates after a customer pays or when the conversation turns to scope, specs, or feature requests. CX Codex +1 ★ 92repo stars launch-planner The launch-planner Claude Code skill schedules a product launch after a customer pays. It works back from the promised delivery date and holds the public release until customer orders are fulfilled. CX Codex +1 ★ 92repo stars objection-handler The objection-handler Claude Code skill drafts replies to sales objections using the terms of your deal. It activates when someone pushes back, asks a question, or sends a message you’re unsure how to answer. CX Codex +1 ★ 92repo stars market-researcher The market-researcher Claude Code skill finds business problems that already have a budget. It responds to requests for product ideas, market research, and idea validation. CX Codex +1 ★ 92repo stars whale-hunter The whale-hunter Claude Code skill finds company decision-makers and drafts a tailored pitch. It starts when asked to identify a buyer, locate a CFO, or write a cold email. CX Codex +1 ★ 92repo stars pre-sale This Claude Code skill manages presales before a product is built and captures buyer requirements. It tracks payments and promised delivery dates. CX Codex +1 ★ 92repo stars whale-skill The whale-skill Claude Code plugin helps test demand before a product launch, from market research through launch planning. Its skills prepare demos, offers, and pre-sales. ★ 92repo stars

Project sponsors

Companies that keep this analytics open