email-drafting
Skill2 starsChanged 56 days agoMITView on GitHub
Use when drafting or editing the user's emails.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- z-Zihan/Evirtheir own version, first seen Oct 13, 2026
- mr-fumanchu/claude-skillstheir own version, first seen Jul 17, 2026
- yiweiwan/skillstheir own version, first seen May 12, 2026
- Solonnikov/agent-skillstheir own version, first seen Apr 23, 2026
- emaduneme/communications-skills-claudetheir own version, first seen Apr 1, 2026
- mgonto/executive-assistant-skillstheir own version, first seen Mar 11, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- mgonto/executive-assistant-skills★ 118same name
- z-Zihan/Evir★ 11same name
- emaduneme/communications-skills-claude★ 3same name
- Solonnikov/agent-skills★ 2same name
- mr-fumanchu/claude-skills★ 1same name
- yiweiwan/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 repository16 other files it gives its agents.
- canvas-course-syncSkill
- categorizerSkill
- course-knowledge-baseSkill
- course-study-sessionSkill
- exam-prepSkill
- grade-calculatorSkill
- homework-checklistSkill
- meetings-and-clubsSkill
- note-formatting-rulesSkill
- photos-to-pdfSkill
- roadmapSkill
- school-advisorSkill
- study-notes-workflowSkill
- suite-updateSkill
- verification-before-completionSkill
- writing-for-agentsSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
2
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 19
Write for a human, human-sounding voice: natural, approachable, not stiff.
- Distinctive: line 25
When he says "sent," open Outlook → Sent Items → the email, and DIFF his sent text against my draft — extend these lessons.
“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
Config: resolve
<PLACEHOLDER>tokens from~/.hermes/school-config.md(seecanvas-course-sync→ School config). Never edit SKILL.md with real values.
Email Drafting
Email drafting (<USER_NAME>'s style — learn from every sent draft)
There is NO reliable "type into Outlook compose" automation (the preview-pane compose field mapping is broken — typing got routed to To/Cc/body wrongly, twice). Always deliver emails as text in chat for copy-paste; reading Outlook (Sent folder) for diffing IS reliable.
<USER_NAME>'s style fingerprint (learned from his sent Chem-lecture-miss apology 9/9/26 — update as he edits more):
- Apologize directly first, zero preamble ("I apologize for..." not "I'm writing to apologize for...")
- Short declarative sentences, one idea each
- Own the mistake fully — NO defensive hedging. But: do NOT be overly apologetic or personal; stay professional and brief (competent student, not begging)
- NO em dashes — ever. They read as AI-generated. Use commas/periods instead.
- Write for a human, human-sounding voice: natural, approachable, not stiff. Easier to build trust.
- End forward-positive: next steps / readiness, not deficit ("so I don't fall behind and am ready for next week's content")
- Close: "Best," + full name + student ID (<STUDENT_ID>)
- Concise — every sentence earns its place
- Professor email subject: COURSE-SECTION: topic (e.g. "<COURSE_CODE>-B: Missed September 9 Lecture")
When he says "sent," open Outlook → Sent Items → the email, and DIFF his sent text against my draft — extend these lessons.
Inbox catch-up ("catch me up on mail")
Reliable: open https://outlook.cloud.microsoft/mail/inbox, read the sidebar (desktop_preview read) to enumerate unread + previews. The MAIL READING PANE is flaky for sequential click-through: it re-pins to the first opened message and refs go stale (same compose/pane bug class).
Workflow: 1) read inbox list = headers + previews of everything unread; 2) report catch-up with priorities; 3) if user wants full body of any, they click it and I read the open pane (reading THAT is reliable). Don't burn turns retrying stale refs.
Archived mail context: keep transcripts of important emails in Classes/Announcements/-style files or notes when relevant.
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.