reply-assistant
Skill8 starsChanged 5 months agoMITView on GitHub
Drafts and refines replies for email, chat, Slack, comments, support tickets, and follow-up messages — adjusting tone and formality, summarizing prior context, and addressing every open question. Use when the user asks to reply to, respond to, or draft a response for a message, email, comment, or support thread.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- BryceYuuu/open-workflow-skillstheir own version, first seen Sep 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- BryceYuuu/open-workflow-skills★ 1same 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 repository46 other files it gives its agents.
- answerSkill
- api-to-exampleSkill
- bilingual-readerSkill
- calendar-prepSkill
- caption-assistantSkill
- chart-explainerSkill
- code-translatorSkill
- competitor-snapshotSkill
- coupon-hunterSkill
- course-fit-checkSkill
- cover-letter-builderSkill
- deal-checkerSkill
- draft-from-notesSkill
- explainSkill
- fact-checkSkill
- fix-grammarSkill
- hook-generatorSkill
- improve-writingSkill
- interview-prepSkill
- job-application-assistantSkill
- job-fit-reviewSkill
- job-offer-compareSkill
- landing-page-critiqueSkill
- linkedin-outreachSkill
- localize-textSkill
- meeting-follow-upSkill
- outline-builderSkill
- paper-readerSkill
- portfolio-project-reviewSkill
- product-review-summarizerSkill
- pronunciation-and-usageSkill
- regex-decoderSkill
- repo-onboarderSkill
- rewrite-longerSkill
- rewrite-shorterSkill
- social-post-generatorSkill
- source-finderSkill
- source-listSkill
- study-planSkill
- style-matchSkill
- summarizeSkill
- table-to-csvSkill
- term-explainerSkill
- terminology-keeperSkill
- tone-rewriterSkill
- translateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
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 20
Keep the reply actionable, concise, and ready to send.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Reply Assistant
Draft a reply that fits the conversation and the user's goal, whether it's an email, chat, comment, or support thread. Offer tone variants when the right register could reasonably go several ways.
- Infer the user's likely goal from the thread and request. State your assumptions when the goal is unclear, or ask if a wrong guess would waste the user's time.
- Match the tone and formality to the recipient and channel (a support ticket reads differently from a Slack reply).
- Address every concrete question or request in the thread — check the reply against each before finishing.
- Preserve names, numbers, links, code, formatting, dates, currencies, and any user constraints exactly.
- Keep the reply actionable, concise, and ready to send. Offer a shorter version or alternate tone only when the user would benefit from choosing.
Return the Recommended reply first, then an Optional shorter version and Notes or assumptions only when they add value. If the visible context is missing something you need, say what is missing and provide the best supported next step. Respond in the same language as the user's request.
Example
Incoming thread (selected text):
From: Priya (customer) Hi — your last invoice charged us for 12 seats but we only have 9 active users. Can you explain the difference and adjust it? Also, is the annual discount still available if we resize now?
User: "reply, friendly but professional"
Recommended reply:
Hi Priya,
Thanks for flagging this. You're right — the invoice billed 12 seats while 9 are active. The extra 3 are seats that were provisioned but never assigned; I've removed them and a corrected invoice for 9 seats is on its way.
The annual discount does still apply at your new seat count, so resizing now keeps it in place. Want me to switch you to annual billing as part of this change?
Best, [your name]
Optional shorter version:
Hi Priya — you're right, those 3 extra seats were provisioned but unassigned. I've removed them and a corrected 9-seat invoice is on its way. The annual discount still applies at the new count — want me to switch you to annual billing too?
Notes: assumed the 3 seats were unassigned rather than a billing error — confirm before sending if that's not the case.
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.