follow-ups
Skill1 starsChanged 3 months agoMITView on GitHub
Find outreach that has gone cold and draft one nudge each - reads Contacts.xlsx for messages sent more than a week ago with no reply. Use when asked about follow-ups, who to chase, what has gone quiet, or which messages need a nudge.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- theam/claude-dev-kittheir own version, first seen Nov 1, 2026
- SuperMailOS/plugintheir own version, first seen Oct 25, 2026
- WireCatLabs/cli-coretheir own version, first seen Oct 20, 2026
- GuiBayma/skillstheir own version, first seen Oct 17, 2026
- youdcode/open-companytheir own version, first seen Sep 21, 2026
- automatewithuday/gtm-prospecting-systemtheir own version, first seen Sep 18, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- theam/claude-dev-kit★ 17same name
- WireCatLabs/cli-core★ 2same name
- youdcode/open-company★ 2same name
- automatewithuday/gtm-prospecting-system★ 1same name
- GuiBayma/skills★ 1same name
- SuperMailOS/plugin★ 1same name
- samsam007b/carriere-kit★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- apply-to-jobSkill
- filter-jobsSkill
- find-jobsSkill
- setupSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Read profile.md for the user's name and voice before drafting anything.
- Very specific: line 15
Read Contacts.xlsx at the repo root.
- Distinctive: line 26
If nothing is due, say so plainly and stop.
- Distinctive: line 42
Never guilt-trip, never mention that they did not reply, never re-send the original message with a new greeting stapled on.
- Very specific: line 53
Do not change Status — the user has not sent it yet.
- Distinctive: line 55
If a contact has already been nudged once and is still quiet, do not draft a second one.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Chase what has gone quiet
The unglamorous half of outreach, and the half most people skip. One nudge after about a week roughly doubles reply rates. A second nudge does not, and a third makes an enemy.
Read profile.md for the user's name and voice before drafting anything.
Step 1 — Find what is due
Read Contacts.xlsx at the repo root. A row needs chasing when all of these hold:
StatusisRequest sentorConnectedDate sentis more than 7 days ago (theFollow-up duecolumn computes this, but compute it yourself too — the formula only evaluates once Excel has opened the file, so it reads asNoneto openpyxl on a freshly written workbook)Notesdoes not already record a nudge
Skip anything at Replied, No reply, or Not sent. No reply means the user has already
decided it is dead; do not resurrect it.
If nothing is due, say so plainly and stop. Do not invent work.
Step 2 — Draft one nudge each
Short. Shorter than the original — under 60 words. The whole message is: I am still interested, here is one new thing, no pressure.
Structure:
Hi <Name>, just following up on this.— or a variant that does not sound automated- One sentence of genuinely new information: the application has progressed, they shipped something relevant, the user published something. If there is nothing new, say the nudge is a nudge — that is more honest than manufacturing a reason
- Repeat the ask once, smaller than before. "Even 10 minutes" beats re-asking for 15
- An explicit way out: something like "happy to leave it if the timing is wrong"
Never guilt-trip, never mention that they did not reply, never re-send the original message with a new greeting stapled on. No metrics — the same rule as first contact.
The way out in point 4 is not politeness padding. It gives a busy person permission to answer at all, and it means the user hears back either way.
Step 3 — Report and record
Show each draft in chat, grouped by company, with how many days it has been.
Then update Contacts.xlsx: append Nudged <date> to Notes for each row you drafted for.
Do not change Status — the user has not sent it yet. Preserve every other cell.
If a contact has already been nudged once and is still quiet, do not draft a second one. List them under a short "leave these" heading instead, and say why: two unanswered messages is the point where persistence stops reading as interest.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

