email-voice
Skill3 starsChanged 58 days agoMITView on GitHub
Write emails in the current user's voice for replies and drafts. Use whenever drafting an email from this OS.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- competitive/CLAUDE.mdCLAUDE.md
- customers/CLAUDE.mdCLAUDE.md
- delivery/CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- engineering/CLAUDE.mdCLAUDE.md
- product/CLAUDE.mdCLAUDE.md
- quality/CLAUDE.mdCLAUDE.md
- team/CLAUDE.mdCLAUDE.md
- call-summarySkill
- dsu-digestSkill
- linkedin-voiceSkill
- os-builderSkill
- person-noteSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 25
Never invent commitments, dates, or data - if unknown, leave a [bracket] for the user to fill.
- Distinctive: line 27
Always produce a DRAFT for the user's review.
- Distinctive: line 29
No em dashes (-) ever: Use commas, periods, or parentheses.
- Distinctive: line 31
Reply-all by default: Keep everyone who was on the thread: To = sender + original To, Cc = original Cc, minus the current user's own …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Email Voice
Whose voice: the current user's. Resolve their name, role and email from me.local.md first - never assume, never default to any teammate. If they have a personal voice guide (<private_root>/voice/email.md or personal-brand/voice/guide.md), it overrides the house defaults below.
House defaults (until a personal guide exists):
Tone: clear, concise, warm-professional, direct. Lead with the answer/ask. No filler.
Structure: brief greeting → the point → any specifics (tight) → clear next step.
Signature (from me.local.md):
Best Regards,
<name>
<role> | <company>Rules:
- Match the recipient: crisper for the boss (your boss), relationship-aware for customers, supportive+specific for teammates.
- Never invent commitments, dates, or data - if unknown, leave a [bracket] for the user to fill.
- Customer emails: no internal-only details; mind confidentiality.
- Always produce a DRAFT for the user's review; never auto-send.
- No em dashes (-) ever. Use commas, periods, or parentheses; "to" for ranges. This is a hard rule.
- Reply-all by default. Keep everyone who was on the thread: To = sender + original To, Cc = original Cc, minus the current user's own address. Do not drop recipients.
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.

