followups
Skill0 starsChanged 2 months agoMITView on GitHub
Find outreach that is due for a follow-up, check Gmail for replies first, and draft the follow-up message
3 other projects use a version of this.
Adopted by
Most recently taken up by
- agentydragon/ducktapetheir own version, first seen Oct 9, 2026
- EdenGibson/claude-skillstheir own version, first seen Jul 3, 2026
- roie9876/clawpilot-skillstheir own version, first seen Apr 29, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- agentydragon/ducktape★ 11same name
- roie9876/clawpilot-skills★ 4same name
- EdenGibson/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 repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- dailySkill
- draft-outreachSkill
- find-contactsSkill
- find-jobsSkill
- research-companySkill
- send-emailSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
0
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 8
Read pipeline/outreach.csv.
“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
Follow-ups
- Read
pipeline/outreach.csv. Find rows with statussentwherefollowup_dueis today or earlier andtouchis less than 3. - For email rows, search Gmail for a reply from that contact since
sent_date. If one exists, set statusreplied, paste a one-line summary of the reply intoreply, and skip drafting. Flag it to Alex at the top of your output; replies are the priority. - For LinkedIn rows, ask Alex whether they replied. He's the only one who can see that.
- For rows still unanswered, draft the next touch:
- Touch 2 (5 days after touch 1): 2 to 3 sentences. Reply in the same thread. Add one new piece of value: a relevant thing Alex built, a link to something they'd find useful, or a sharper version of the ask. Never "just following up" or "bumping this".
- Touch 3 (12 days after touch 1): 2 sentences. Close the loop politely, leave the door open, no ask. This is the last message.
- Save each draft to the contact's existing draft file under a "Follow-up N" heading. Append a new row to
outreach.csvwith the next touch number and statusdraft. Set the original row tono_replyonce touch 3 has been sent. - Print: replies found, follow-ups drafted, threads closed.
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.

