follow-up
Skill38 starsChanged 8 months agoApache-2.0View on GitHub
Find emails needing follow-up -- unanswered sent emails, flagged unreplied, draft contextual responses
25 other projects use a version of this.
Adopted by
Most recently taken up by
- bjoern621/claude-skillstheir own version, first seen Nov 16, 2026
- pantheon-org/tekhnetheir own version, first seen Nov 15, 2026
- Celorus/celorus-plugintheir own version, first seen Nov 15, 2026
- Jakeschincariol/whale-skilltheir own version, first seen Nov 8, 2026
- Jakeschincariol/closer-skilltheir own version, first seen Nov 8, 2026
- digitalgym/aipathway-standardstheir own version, first seen Nov 4, 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 versions25 projects use a version of this.
Word for word · 1
- n24q02m/better-email-mcp★ 38100% same
Edited · 0
None found.
Wrote their own version · 24
- Jakeschincariol/closer-skill★ 33same name
- etrebels/claude-code-growth-os★ 23same name
- alejopijuan/Claude-Code-Agency-Co-Founder★ 19same name
- Jakeschincariol/whale-skill★ 15same name
- pantheon-org/tekhne★ 10same name
- zime-skills/global★ 8same name
- zime-skills/zime-skills★ 8same name
- noticedso/skills★ 2same name
- palashjain95/jobhunter★ 2same name
- s1vanov/follow-up★ 2same name
14 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 repository3 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- inbox-reviewSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 4 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If no matching reply found, this email needs follow-up
- Very specific: line 50
If original was your sent email with no reply: draft a gentle follow-up referencing the original
- Distinctive: line 51
If original was received and you haven't replied: draft a response to their message
- Distinctive: line 52
Use reply (not new message): when following up on existing threads:
- Very specific: line 56
Use messages(action="new") for new conversations.
- Distinctive: line 65
Check all accounts, same as inbox-review:
- Distinctive: line 75
Before meetings -- check if pending items got responses
- Very specific: line 76
When a specific sent email seems to have been ignored
“Common” is measured: kept by at least 6 in 10 of the 20 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-Up
Find emails that need follow-up and draft contextual responses.
Unanswered Sent Emails
Find emails you sent that received no reply after N days:
- Search Sent folder for emails sent N+ days ago:
messages(action="search", query="SINCE 2026-03-16 BEFORE 2026-03-20", folder="Sent", account="...") - Cross-reference Inbox for replies:
- For each sent email, search Inbox for matching Subject (with
Re:prefix):messages(action="search", query="SUBJECT \"Re: <original subject>\" FROM <recipient>") - If no matching reply found, this email needs follow-up
- For each sent email, search Inbox for matching Subject (with
- Present candidates with context:
No reply after 5 days: 1. "API Integration Proposal" to partner@company.com (sent Mar 18) Original: Asked about timeline for API access 2. "Invoice #2024-003" to client@business.com (sent Mar 16) Original: Sent invoice, requested payment confirmation
Flagged but Unreplied
Find received emails you flagged/starred but never responded to:
messages(action="search", query="FLAGGED", account="...")Then for each flagged email, check Sent folder for a reply with matching subject. If none found, it needs attention.
Drafting Follow-Up Messages
For each follow-up candidate:
- Read the original thread to get full context
- Decide reply type:
- If original was your sent email with no reply: draft a gentle follow-up referencing the original
- If original was received and you haven't replied: draft a response to their message
- Use reply (not new message) when following up on existing threads:
Usemessages(action="reply", uid="<original_uid>", body="<follow-up text>")messages(action="new")for new conversations. - Follow-up tone guidelines:
- First follow-up (3-5 days): "Just checking in on this..."
- Second follow-up (7-10 days): "Wanted to circle back on..."
- Final follow-up (14+ days): Direct ask with deadline: "Could you confirm by Friday?"
Multi-Account Handling
Check all accounts, same as inbox-review:
folders(action="list")
# Iterate each account's Sent folderWhen to Use
- Weekly follow-up review (e.g., Friday afternoon)
- Before meetings -- check if pending items got responses
- When a specific sent email seems to have been ignored
- Clearing out flagged emails that accumulated
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.

