asgeirtj/system_prompts_leaks
Read or triage email, clean up an inbox, draft or send messages, and check delivery.
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.
MITAuto-check passed
Install Follow Up Chaser
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaser --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/follow-up-chaser .claude/skills/follow-up-chaser && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .claude/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaserType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaser --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/follow-up-chaser .agents/skills/follow-up-chaser && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .agents/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaser --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/follow-up-chaser .cursor/skills/follow-up-chaser && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .cursor/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mohitagw15856/pm-claude-skills.git --path skills/follow-up-chaser--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaser --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/follow-up-chaser .gemini/skills/follow-up-chaser && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .gemini/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaserInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/follow-up-chaser .github/skills/follow-up-chaser && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .github/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mohitagw15856/pm-claude-skills follow-up-chaser --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/follow-up-chaser .opencode/skills/follow-up-chaser && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "follow-up-chaser" agent skill from https://github.com/mohitagw15856/pm-claude-skills/tree/main/skills/follow-up-chaser into .opencode/skills/follow-up-chaser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "follow-up-chaser", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
follow-up-chaser- GitHub stars
- 1.4k
- Token cost
- ~1.1k tokens
- SKILL.md length
- 608 words
- Files
- 1
- Skills in repo
- 1,348
- Repo updated
- First seen
- Licence
- MIT
At a glance
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.
- Works in 5 steps: Wait right: internal asks get 2–3… → Rung 1 — reduce the ask: don't "bump" —… → Rung 2 — add legitimate urgency: the… → …
- Asked they havent replied what do I send
- SKILL.md covers What This Skill Produces, Required Inputs, Framework: The Chase Rules and Output Format, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Follow Up Chaser is an agent skill from mohitagw15856/pm-claude-skills. 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.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: 1255 professional Agent Skills for Claude, ChatGPT, Gemini, Cursor & Codex — PRDs, postmortems, leases, medical bills, layoffs, go-bags, new countries. Plain markdown, MIT, in… The licence is MIT.
When your agent uses it
- Asked they havent replied what do I send
- Write a follow-up that isnt pushy
- How long do I wait before chasing
- Manage my waiting-on list
Example prompts
- “t replied what do I send, write a follow-up that isn”
- “/follow-up-chaser”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Wait right: internal asks get 2–3 business days before rung one; external/senior get 4–5; anything with a stated deadline gets chased at…
- Rung 1 — reduce the ask: don't "bump" — shrink. Restate in one line, convert to yes/no where possible, attach a default: "If I don't hear…
- Rung 2 — add legitimate urgency: the reason the timing matters, stated plainly ("the vendor quote expires Thursday"), plus the smallest…
- Rung 3 — change channel, kindly: "Sending a quick ping here in case email got buried" — chat or a 2-minute call ask. Channel escalation…
- The close: after rung 3, silence is the answer — close explicitly: "Haven't heard back, so I'll [default/drop it]. Reopen anytime."…
What it can do on your machine
Read from SKILL.md and the folder at commit 1cbf1f0. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Follow Up Chaser loads about 1.1k tokens when it runs. Until then it costs about 115 tokens; SKILL.md has 608 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from mohitagw15856/pm-claude-skills at commit 1cbf1f0, republished under its MIT licence (© mohitagw15856). 608 words, ~1,131 tokens.
Download SKILL.mdSave it as
.claude/skills/follow-up-chaser/SKILL.md (or your agent's skills folder).- name
- follow-up-chaser
- description
- 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.
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 four different cadences
- The stakes — blocking your work? Nice-to-have? The sequence's pace and the close's shape follow
Framework: The Chase Rules
- Wait right: internal asks get 2–3 business days before rung one; external/senior get 4–5; anything with a stated deadline gets chased at deadline-minus-buffer regardless. Chasing at 24 hours reads as pressure; at two weeks the thread is cold and the chase restarts from context.
- Rung 1 — reduce the ask: don't "bump" — shrink. Restate in one line, convert to yes/no where possible, attach a default: "If I don't hear by Friday I'll go with option A — flag if that's wrong." Defaults convert silence into a decision, which is the whole trick.
- Rung 2 — add legitimate urgency: the reason the timing matters, stated plainly ("the vendor quote expires Thursday"), plus the smallest possible version of the ask ("even a one-word yes works"). Never manufactured urgency — one fake deadline poisons all future real ones.
- Rung 3 — change channel, kindly: "Sending a quick ping here in case email got buried" — chat or a 2-minute call ask. Channel escalation reads as helpful persistence; a third identical email reads as nagging.
- The close: after rung 3, silence is the answer — close explicitly: "Haven't heard back, so I'll [default/drop it]. Reopen anytime." Closing converts a zombie thread into a decision, protects the relationship, and — often — finally triggers the reply.
Show full SKILL.md (188 more words)Show less
Output Format
Chase Plan: [the ask] — sent [date]
The Sequence
| Rung | Send date | Channel | The move |
|---|
The Drafts
[Rung 1: the shrunk ask + default, verbatim · Rung 2: urgency + smallest ask · Rung 3: the channel ping · The close]
Waiting-On Hygiene
[The @waiting entry: what, who, next rung date — reviewed weekly]
Quality Checks
- Rung 1 shrinks the ask rather than bumping it
- Every deadline cited is real, with its reason
- The default-on-silence appears wherever a default legitimately exists
- Channel escalation happens once, framed as buried-email courtesy
- The close is drafted before the sequence starts — silence has a planned meaning
Anti-Patterns
- Do not send "just bumping this" — a bump adds nothing and costs attention
- Do not escalate temperature (guilt, passive aggression) — escalate channel and clarity instead
- Do not chase without a waiting-list entry — untracked chases become the zombie threads
- Do not fake urgency — the first discovered fake deadline devalues every future real one
- Do not let threads die unclosed — an explicit close beats an awkward silence in every relationship that matters
Example Trigger Phrases
- "Write a follow-up that isn't pushy."
- "How long do I wait before chasing?"
- "Manage my waiting-on list."
© mohitagw15856, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/follow-up-chaser of mohitagw15856/pm-claude-skills.
Open the folder on GitHubat commit 1cbf1f0
Compare with similar skills
Follow Up Chaser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Follow Up Chaser this skillmohitagw15856/pm-claude-skills | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Emailasgeirtj/system_prompts_leaks | 69k | — | ~3.5k | Automated safety check: Pass | CC0-1.0 | |
| Emailscoreyhaines31/marketingskills | 54k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Mailtrap Email Integrationaffaan-m/ECC | 277k | 1 repos | ~955 | Automated safety check: Pass | MIT | |
| Email Marketing Biblesickn33/agentic-awesome-skills | 47k | — | ~8.7k | Automated safety check: Pass | MIT | |
| Email Systemsdavila7/claude-code-templates | 33k | 2 repos | ~548 | Automated safety check: Pass | MIT |
Similar skills
Email
Emails
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program.
Mailtrap Email Integration
affaan-m/ECC
Guides agents through integrating transactional email sending via Mailtrap's Email API, including sandbox testing, domain verification, and API authentication.
Email Marketing Bible
sickn33/agentic-awesome-skills
Data-backed email marketing for AI agents: automation flows, deliverability triage, copy de-slopping, AI email design, ESP control via MCP with send gates and compliance.
Email Systems
davila7/claude-code-templates
Email has the highest ROI of any marketing channel. An agent skill from davila7/claude-code-templates.
Email Manager
LeoYeAI/openclaw-master-skills
When user asks to write email, draft reply, manage inbox, email template, follow up email, cold email, professional email, email subject line, thank you email, apology email, meeting request email…
More from mohitagw15856/pm-claude-skills
All 1,348 skills in this repoCar Tco
mohitagw15856/pm-claude-skills
Compare the total cost of car ownership across buy-new, buy-used, lease, and keep-your-current-car — depreciation, insurance, maintenance ramp, and fuel over a real horizon, not just the monthly…
Cs Health Scorecard
mohitagw15856/pm-claude-skills
Build a customer health scorecard for a specific account. An agent skill from mohitagw15856/pm-claude-skills.
Exit Waterfall
mohitagw15856/pm-claude-skills
Compute who gets what at each exit price from a cap table — liquidation preferences, conversion points, and where the founders' share collapses.
Feature Prioritisation
mohitagw15856/pm-claude-skills
Apply prioritisation frameworks (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) to rank features and backlog items.
Fire Number
mohitagw15856/pm-claude-skills
Compute a financial-independence (FIRE) target and years-to-reach with every assumption labeled as an assumption — plus a sensitivity table instead of a single false-precision answer.
Freelance Rate
mohitagw15856/pm-claude-skills
Derive a freelance day/hourly rate backwards from target income, honest billable utilization, overhead, and the self-employment tax premium — the arithmetic that proves a rate is not salary÷2000.
Questions about Follow Up Chaser
What does Follow Up Chaser 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. Follow Up Chaser is an agent skill from mohitagw15856/pm-claude-skills. 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.
When should I use Follow Up Chaser?
Follow Up Chaser fits situations like: asked they havent replied what do I send; write a follow-up that isnt pushy; how long do I wait before chasing; manage my waiting-on list.
How do I install Follow Up Chaser in Claude Code?
Run `npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a claude-code`. Or copy the skill folder (skills/follow-up-chaser in mohitagw15856/pm-claude-skills) into .claude/skills/follow-up-chaser in your project. Claude Code loads it when a task matches its description.
How do I install Follow Up Chaser in Codex?
Run `npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a codex`. Or copy the skill folder (skills/follow-up-chaser in mohitagw15856/pm-claude-skills) into .agents/skills/follow-up-chaser in your project. Codex loads it when a task matches its description.
Can I use Follow Up Chaser in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mohitagw15856/pm-claude-skills --skill follow-up-chaser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/follow-up-chaser, .gemini/skills/follow-up-chaser, .github/skills/follow-up-chaser and .opencode/skills/follow-up-chaser in your project.
What does Follow Up Chaser need to run?
SKILL.md names no scripts, command-line tools or credentials: Follow Up Chaser is instructions for the agent only.
Does Follow Up Chaser access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Follow Up Chaser safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Follow Up Chaser use?
Follow Up Chaser is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Follow Up Chaser use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Follow Up Chaser?
Skills that share tags, products or a category with Follow Up Chaser: Email (asgeirtj/system_prompts_leaks, 69k stars), Emails (coreyhaines31/marketingskills, 54k stars), Mailtrap Email Integration (affaan-m/ECC, 277k stars) and Email Marketing Bible (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Follow Up Chaser?
mohitagw15856 (a GitHub user) maintains it in mohitagw15856/pm-claude-skills, which has 1,434 GitHub stars. The repository holds 1,348 skills in this directory. The repository was last updated on October 9, 2026.
Source: mohitagw15856/pm-claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.