Menu

Individual skill

follow-up-chaser

0upvotes

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.

plugins/pm-cowork/skills/follow-up-chaser/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,539
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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:
Back to top