follow-up-chaser
Chase unanswered emails without being annoying — the escalating-gently sequence with timing rules, the re-ask that makes replying easy, and the close-the-loop discipline that ends zombie threads. Use when asked they haven't replied what do I send, write a follow-up that isn't pushy, how long do I wait before chasing, or manage my waiting-on list. Produces the follow-up sequence with dates, drafts per rung, and the give-up-gracefully exit.
Profile →npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Follow-Up Chaser Skill Unanswered email dies in two ways: never chased (the ask silently expires) or chased badly ("just bumping this!" seven times, each one easier to ignore than the last). Good chasing is engineered: each follow-up *lowers the cost of replying* — restating the ask smaller, offering a default, adding a deadline with a reason — and the sequence escalates channel or stakes, not temperature. Three rungs, then a graceful close that converts silence into an answer. ## What This Skill Produces - **The sequence** — 2–3 follow-ups with dates, each drafted, each easier to answer than the last - **The re-ask engineering** — the original request shrunk to its yes/no core with a default attached - **The channel escalation** — when rung 3 moves from email to chat/call, and how to do it without ambush - **The graceful close** — the final note that ends the thread with the relationship intact ## Required Inputs Ask for these if not provided: - **The original ask and its date** — what was requested, how big the ask is (a signature vs. a favor vs. a decision), and any real deadline - **The relationship and power direction** — chasing a report, a peer, a boss, and a customer are
- What This Skill Produces
- Required Inputs
- Framework: The Chase Rules
- Output Format
- The Sequence
- The Drafts
- Waiting-On Hygiene
- Quality Checks
- Anti-Patterns
What does the follow-up-chaser skill do?
Chase unanswered emails without being annoying — the escalating-gently sequence with timing rules, the re-ask that makes replying easy, and the close-the-loop discipline that ends zombie threads. Use when asked they haven't replied what do I send, write a follow-up that isn't pushy, how long do I wait before chasing, or manage my waiting-on list. Produces the follow-up sequence with dates, drafts per rung, and the give-up-gracefully exit.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.