Client follow-up — install without GitHub

Draft the right follow-up for a client or prospect—after a call, after a quiet proposal, after delivery, or when reconnecting with a past client. Never sends email; writes a draft and logs it.

Skill name: client-follow-up. Personal install path: ~/.claude/skills/client-follow-up/SKILL.md (available in all your projects on this machine). See the Claude Code skills docs.

One-line install

mkdir -p ~/.claude/skills/client-follow-up && curl -fsSL https://solostackkits.netlify.app/skills/client-follow-up/SKILL.md -o ~/.claude/skills/client-follow-up/SKILL.md

Then start Claude Code (claude) and either type /client-follow-up or ask in plain language that matches the description.

What the description says (for triggering)

Write the right follow-up email for a client or prospect based on where the relationship stands (after a call, after a proposal with no reply, after delivery, or reconnecting with a past client). Use when the user says "follow up with", "nudge", "they went quiet", or "check in with".

Preview the file

/skills/client-follow-up/SKILL.md — raw markdown, curl-friendly.

---
name: client-follow-up
description: Write the right follow-up email for a client or prospect based on where the relationship stands (after a call, after a proposal with no reply, after delivery, or reconnecting with a past client). Use when the user says "follow up with", "nudge", "they went quiet", or "check in with".
---

# Client follow-up

## Step 1 - Figure out the situation
Read `clients/<client>/log.md` (create it if missing) and the latest files in that folder. Classify:
| Situation | Signal | Goal of email |
|---|---|---|
| A. Post-call | Call in last 3 days, nothing sent | Recap + next step |
| B. Proposal silence | Proposal sent, no reply 4+ days | Get a yes/no, not a "just checking in" |
| C. Post-delivery | Project delivered | Confirm value, ask for testimonial/referral |
| D. Dormant past client | No contact 60+ days | Offer something useful, open a door |
State which one you chose and why. If unclear, ask.

## Step 2 - Write it
- Subject line under 6 words, specific to them.
- Under 120 words. One ask only.
- A: bullet recap of what THEY said (3 max), then the agreed next step with a date.
- B: "Nudge ladder" by count of prior nudges in log.md:
  1st: add one new useful thing (insight, example) + "Does option B still fit?"
  2nd: make it easy to say no: "Should I close this out for now?"
  3rd: none; tell the user to stop and mark the deal lost in log.md.
- C: name the concrete result, ask one testimonial question ("What changed since we started?") and, separately, whether anyone else should hear about it.
- D: reference something specific from their past project; offer a resource or 20-minute check-in.
- Banned openers: "just checking in", "touching base", "hope this finds you well", "circling back".

## Step 3 - Save
Write the draft to `clients/<client>/drafts/followup-YYYY-MM-DD.md` and append one line to `log.md`: `YYYY-MM-DD | drafted follow-up (<situation>) | not sent`. Never send email yourself.

Related free tools

Skill description tester — will this description trigger?
SKILL.md validator — lint name, description and frontmatter
How to install a skill from a URL

Want the zip with all three plus setup notes? Free 3-skill sample on Gumroad. The full Solo Consultant Kit is $29.