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
/plugin marketplace add Jakeschincariol/whale-skill
/plugin install whale-skill@whale-skillWhat 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-pierdeal. - 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-skillThis installs the whole whale-skill plugin with all its skills
2Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill follow-up -a claude-code3Manually: put the files in place
~/.claude/skills/follow-up/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/follow-up/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill follow-up -a codex2Manually: put the files in place
.agents/skills/follow-up/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill follow-up -a cursor2Manually: put the files in place
.cursor/skills/follow-up/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Jakeschincariol/whale-skill follow-up2Manually: put the files in place
.github/skills/follow-up/SKILL.md1Skills CLI (Vercel)
npx skills add Jakeschincariol/whale-skill --skill follow-up -a gemini-cli2Platform CLI
gemini skills install https://github.com/Jakeschincariol/whale-skill --path follow-upManually: put the files in place
.devin/skills/follow-up/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 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.