followup
Skill1 starsChanged 2 months agoMITView on GitHub
Draft the single follow-up to an unanswered cold email, or draft the reply to a company that has responded. Use when a follow-up comes due, when a reply arrives, or to see across both trackers what is owed. Enforces the one-follow-up-only rule.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- emingo/claude-skillstheir own version, first seen Nov 16, 2026
- eklavyagoyal/wingmantheir own version, first seen Sep 10, 2026
- aksheyw/career-command-center-templatetheir own version, first seen Jul 16, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- aksheyw/career-command-center-template★ 1same name
- eklavyagoyal/wingman★ 0same name
- emingo/claude-skills★ 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 repository37 other files it gives its agents.
- wsb-data-pipelineSkill
- docx-exportSkill
- harvard-mdxSkill
- humanise-docx-reportSkill
- make-pdfSkill
- bom-builderSkill
- ring-testSkill
- batch-draftSkill
- cold-emailSkill
- cv-intakeSkill
- cv-upgradeSkill
- find-contactSkill
- humanize-emailSkill
- log-outreachSkill
- outreach-statusSkill
- target-researchSkill
- erc-statusSkill
- log-sessionSkill
- score-auditSkill
- submission-checkSkill
- sumo-statusSkill
- trial-runSkill
- vr-statusSkill
- academic-registerSkill
- aviation-data-sourcesSkill
- business-frameworksSkill
- consultancy-registerSkill
- excel-deliverablesSkill
- forecasting-methodsSkill
- operations-frameworksSkill
- secondary-data-sourcesSkill
- archive-indexSkill
- event-proposalSkill
- meeting-minutesSkill
- read-boxnoteSkill
- captureSkill
- new-scriptSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
Run send_qa on it
- Distinctive: line 69
Follow-ups stay under 60 words and add no new argument.
- Distinctive: line 70
Never chase a reply less than 24 hours old.
- Distinctive: line 71
Avoid Friday afternoons and weekends.
- Distinctive: line 72
Never send. Drafts go to the folder for a human.
- Distinctive: line 73
Keep both trackers in step.
“Common” is measured: kept by at least 6 in 10 of the 3 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
/followup, the one nudge and the replies
Usage: /followup (everything due) · /followup "<Person Name>" Space42 · /followup --replies
Steps
- Read both trackers and both
sent/folders. The folders are ground truth; the tracker is the summary. When they disagree, fix the tracker. - Spawn
followup_plannerto compute what is due against today. - Handle replies before anything else. A reply is worth more than a week of cold outreach. If one is waiting, draft that answer first.
- For each follow-up due (day 6–7, no reply):
- Confirm no follow-up has already gone. If one has, the answer is
no-replyand the company is finished for this cycle. There is no second nudge - Draft it: under 60 words,
Re:plus the exact original subject so it threads, the single strongest link restated, the referral fallback, no attachment, no new argument - Save to
<person>/sent/YYYY-MM-DD-<company>-followup.md, statusready - Run
send_qaon it
- Confirm no follow-up has already gone. If one has, the answer is
For each reply:
Reply Response Interested, wants a call Confirm within 24 hours. Offer concrete times. Attach the CV now Asks for the CV or portfolio Send it. At most two files. Never a company its own recommendation letter "Not this cycle" Short thanks, ask when to check back, park it with a diary date Rejection Short thanks, plus the one question: is there someone else worth talking to. This converts Forwarded internally Thank them, and treat the new person as a warm contact rather than a cold one Out of office No action. Push the follow-up date to after their return - Close out anything past day 14 with no reply after a follow-up: status
no-reply. Do not re-contact for three weeks, and then only a different person. - Push outcomes to the vault. A replying contact becomes a
04 People/note via/obsidian-person— name, company, role, context, and no contact details. An interview becomes a line in09 Reference/Planned Events.md. - Update both trackers.
Output format
## Follow-up run — <date>
### Drafted
| Person | Company | Type | Words | Status |
|---|---|---|---|---|
### Replies needing an answer
| Person | Company | What they said | Waiting | Drafted? |
|---|---|---|---|---|
### Closed out
| Person | Company | Reason | Status |
|---|---|---|---|
### Due later
| Person | Company | Due |
|---|---|---|
## Next action
<one thing>Rules
- One follow-up per company, ever. The single rule most likely to be broken with good intentions. A second nudge converts almost nothing and turns a neutral non-answer into a bad impression.
- Follow-ups stay under 60 words and add no new argument. If the first email did not work, a longer second one will not either.
- Never chase a reply less than 24 hours old.
- Avoid Friday afternoons and weekends. Tuesday to Thursday morning gets opened. The UAE week runs Monday to Friday, so a Sunday send lands before anyone is reading.
- Never send. Drafts go to the folder for a human.
- Keep both trackers in step. Updating one and not the other leaves the next session with a wrong picture.
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.

