Write the follow-up messages that keep a candidate on the radar without being annoying. Use when asked to write a post-interview thank-you, a follow-up after no reply, a nudge on a stalled application, or a check-in sequence during a job search. Produces a timed sequence — what to send, when, and the exact wording — that adds value or shows interest at each step rather than just 'checking in'.
Scanned 9/3/2026
Install to Claude Code
npx -y skills add mohitagw15856/pm-claude-skills --skill follow-up-sequence --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Follow Up Sequence?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mohitagw15856-follow-up-sequence-8a965295)More formats (shields.io, HTML) on the badges page.
---
name: follow-up-sequence
description: "Write the follow-up messages that keep a candidate on the radar without being annoying. Use when asked to write a post-interview thank-you, a follow-up after no reply, a nudge on a stalled application, or a check-in sequence during a job search. Produces a timed sequence — what to send, when, and the exact wording — that adds value or shows interest at each step rather than just 'checking in'."
---
# Follow-Up Sequence Skill
Most candidates either ghost after an interview or pester with "just checking in" — both hurt. The right
follow-up is *timed* and *adds something* each time: a genuine thank-you, a useful thought, a graceful
nudge. This skill builds the sequence — what to send, when, and the wording — so you stay top-of-mind
and look like someone people want to work with.
## Required Inputs
Ask for these only if they aren't already provided:
- **The situation** — post-interview thank-you, after-no-reply nudge, stalled application, or an offer-timeline check.
- **The details** — who you spoke with (name/role), the role/company, when, and 1–2 specifics from the conversation to reference.
- **Any deadline** — a competing offer or a stated timeline that changes the cadence.
## Output Format
### Follow-Up Sequence: [situation] — [role] at [company]
A **timed sequence** — each step says *when*, *why*, and the exact message:
| When | Step | Goal |
|---|---|---|
| Within 24h | Thank-you | reinforce interest + one specific takeaway |
| ~1 week | Value-add nudge | stay visible by adding something, not just asking |
| ~2 weeks | Graceful status check | one polite ask, with an easy out |
For each step, the **full message** (subject + body), kept short:
- **Thank-you (24h):** specific to the conversation — reference a real moment, restate fit in one line, no generic "thanks for your time."
- **Value-add (≈1 week):** share a relevant article, a thought on something discussed, or a quick portfolio link — a reason to reappear that isn't "any update?".
- **Status check (≈2 weeks):** a short, warm ask about timeline, with a graceful out and (if real) a mention of your timeline/competing offer.
End with a **stop rule** — when to let it go (and how to leave the door open).
## Quality Checks
- [ ] The thank-you references something specific from the actual conversation
- [ ] Each follow-up adds value or interest — not a bare "checking in"
- [ ] The cadence is sensible (24h → ~1wk → ~2wk), adjusted for any real deadline
- [ ] Messages are short and give an easy, graceful out
- [ ] There's an explicit stop rule so it never tips into pestering
## Anti-Patterns
- [ ] Do not send a generic "thank you for your time" — reference a real moment or skip it
- [ ] Do not "just check in" — every touch should add something or it reads as needy
- [ ] Do not follow up too fast or too often — respect the cadence; desperation repels
- [ ] Do not issue ultimatums — mention a real competing timeline gracefully, never as a threat
- [ ] Do not follow up forever — define when to stop and leave the relationship intact
## Based On
Post-interview and job-search follow-up practice — timed, value-adding touches with a stop rule.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!