follow-up
Skill0 starsChanged 26 days agoMITView on GitHub
Draft follow-up messages for people in the user's ConnectMachine network, using where and when they met.
23 other projects use a version of this.
Adopted by
Most recently taken up by
- Jakeschincariol/whale-skilltheir own version, first seen Nov 8, 2026
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- Celorus/celorus-plugintheir own version, first seen Nov 6, 2026
- digitalgym/aipathway-standardstheir own version, first seen Nov 4, 2026
- burnoutscript/sales-skillstheir own version, first seen Nov 1, 2026
- aya-taleb/biz-boost-skillstheir own version, first seen Nov 1, 2026
Used with
Projects with it also use call-prep, mock-interview and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillcall-prep
Prepare for a customer or prospect call using Common Room signals. Triggers on 'prep me for my call with [company]', 'prepare for a meeting with [company]', 'what should I know before talking to [company]', or any call preparation request.
Also in 3 projects that use this
aslavchevSkillmock-interview
Simulate a real job interview for any role. Use when user says "mock interview", "interview me", "interview prep", "practice interview", or wants to rehearse for a specific company or position. Adapts rounds and questions to the role — technical, managerial, creative, or any other.
Also in 3 projects that use this
jwilgerSkillpipeline
Autonomous build-phase orchestrator with 8-stage per-slice pipeline (decompose, slice readiness review, implement via TDD pairs, three-stage code review, address feedback, mutation testing, push/CI, merge/flag). Manages slice queue (walking skeleton first, dependency ordering), dispatches TDD pairs with capability detection, enforces 5 binary quality gates with 3-cycle rework budgets and human escalation, maintains audit trail, and respects strict controller boundaries (never writes code, delegates all creative work). Supports three autonomy levels (conservative/standard/full). Use when running factory mode, orchestrating build phases, managing slice queues, or coordinating TDD pairs with review gates. Triggers on: "run the pipeline", "factory mode", "build phase", "slice queue", "quality gates", "autonomous build". NOT for: individual TDD (use tdd), standalone code reviews (use code-review), CI-only workflows (use ci-integration).
Also in 3 projects that use this
Other versions23 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 23
- n24q02m/better-email-mcp★ 37same name
- n24q02m/email★ 37same name
- Jakeschincariol/closer-skill★ 33same name
- etrebels/claude-code-growth-os★ 21same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- Jakeschincariol/whale-skill★ 15same name
- zime-skills/global★ 8same name
- zime-skills/zime-skills★ 8same name
- noticedso/skills★ 2same name
- palashjain95/jobhunter★ 2same name
13 more not listed
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 repository2 other files it gives its agents.
- connectmachineSkill
- save-contactSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
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 9
Read each person's details with get_contact: where and when they met, notes, company and role.
- Distinctive: line 10
Write one short, personal draft per person that refers to how they met.
“Common” is measured: kept by at least 6 in 10 of the 19 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
Draft follow-ups for: $ARGUMENTS
- Find the people. For a name, use
find_contact. For an event or a description, usesearch_contactsorlist_contactswithsearch. If nothing was given, ask who to follow up with. - Read each person's details with
get_contact: where and when they met, notes, company and role. - Write one short, personal draft per person that refers to how they met. Keep each under 100 words.
- Show the drafts to the user. Don't send anything. Offer to adjust the tone or add a next step.
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.