draft-reply
Skill1 starsChanged 3 months agoMITView on GitHub
Write a reply to a specific email or message in the user's own voice and save it as a draft — never send. Use when the user says "reply to X", "draft a response to that", "answer this email", or "tell them yes/no" about a specific message.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- MaguiSella/second-brain-startertheir own version, first seen Nov 8, 2026
- MaximeGaudin/second-brain-startertheir own version, first seen Sep 21, 2026
- priyanshu-arya/LinkedIn_Automationtheir own version, first seen Sep 17, 2026
- TrustPager/Business_Operating_Systemtheir own version, first seen Jun 30, 2026
- composio-community/support-skillstheir own version, first seen Apr 10, 2026
- Joshua-Palamuttam/workbench-templatetheir own version, first seen Mar 7, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- composio-community/support-skills★ 18same name
- MaximeGaudin/second-brain-starter★ 8same name
- TrustPager/Business_Operating_System★ 8same name
- Joshua-Palamuttam/workbench-template★ 3same name
- MaguiSella/second-brain-starter★ 0same name
- priyanshu-arya/LinkedIn_Automation★ 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 repository8 other files it gives its agents.
- daily-briefSkill
- inbox-triageSkill
- lead-campaignSkill
- meal-plannerSkill
- quick-researchSkill
- subscription-auditSkill
- trip-plannerSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write the reply the user would write, and leave it in drafts for them to send.
- Distinctive: line 15
Match the user's voice: If you can see their past sent mail, mirror it: greeting style, length, sign-off, how formal.
- Distinctive: line 30
Don't add claims, numbers, commitments, or dates the user didn't give you.
- Distinctive: line 31
No filler openers. No "I hope you're well" unless that's genuinely their style.
- Distinctive: line 32
If the message is asking for something sensitive (money, credentials, personal data), draft nothing and flag it to the user instead.
“Common” is measured: kept by at least 6 in 10 of the 6 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 a Reply
Write the reply the user would write, and leave it in drafts for them to send.
Steps
- Find the message. Confirm which one if it's ambiguous — sender + subject.
- Read the whole thread, not just the last message, so the reply fits the context and doesn't repeat what's already been said.
- Match the user's voice. If you can see their past sent mail, mirror it: greeting style, length, sign-off, how formal. When in doubt, go shorter and plainer.
- Write the reply. Answer what was actually asked. If the user gave you a direction ("say yes but push the date to Friday"), follow it exactly.
- Save it as a draft on the existing thread. Report that it's drafted.
Then
Show the user the draft in full and tell them where it is. Offer one line: "Change anything, or is it good to send?" — but do not send it yourself.
Rules
- Never send. The user sends. Always.
- Don't add claims, numbers, commitments, or dates the user didn't give you.
- No filler openers. No "I hope you're well" unless that's genuinely their style.
- If the message is asking for something sensitive (money, credentials, personal data), draft nothing and flag it to the user instead.
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.