reply
Skill121 starsChanged 6 months agoMITView on GitHub
Generate 3 reply options + a recommendation for any incoming message thread. The user picks; /draft sends.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- derogab/agent-kittheir own version, first seen Oct 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
- derogab/agent-kit★ 4same 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.
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 56
If the message clearly has only one reasonable response (e.g., a simple yes/no logistical question), just give the one reply and a note …
≈ “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
User shows you a thread. You return three plausible replies and a recommendation. They pick.
Recipe
- Read the thread. Last 10–20 messages.
- Identify the actual question or ask. Strip pleasantries. What does this message actually want from the user?
- Read memory/people.md and memory/commitments.md for relevant context (e.g., have they already promised something here?).
Draft three options that span the strategy space:
- Option A — Direct yes/agreement: shortest path forward.
- Option B — Push back or qualify: where the user has constraints, hesitation, or a different read.
- Option C — Buy time or redirect: defer, ask a clarifying question, change the venue.
- Recommend one based on:
- User's stated priorities in life.md
- The relationship's pattern (from people.md)
- Open commitments that might be affected
- Format the output as:
**They said:** <one-line restatement of the ask>
**Option A — <flavor>**
<draft text>
**Option B — <flavor>**
<draft text>
**Option C — <flavor>**
<draft text>
**Recommendation: <A/B/C>.** <One sentence why.>
**Wildcard:** <one contrarian take they might not have considered>- Wait for user to pick. "Send A" → invoke /draft to send Option A.
Voice rules
Match the recipient's tone. See /draft for full voice rules.
When NOT to give 3 options
If the message clearly has only one reasonable response (e.g., a simple yes/no logistical question), just give the one reply and a note about why options aren't useful here.
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.