Triggered when user wants to write, draft, reply to, or compose an email. Matches: "reply to [sender]", "draft an email", "write a reply", "respond to this email", "compose email to [name]", "help me write an email", "draft a follow-up", "email [name] about [topic]", "send a response". Also triggered by email-triage when user selects "Draft replies to Urgent emails". Do NOT use for non-email messaging (Slack messages, Teams replies, SMS, WhatsApp), setting follow-up reminders or tracking reply status (use email-followup), or reviewing/categorizing inbox contents (use email-triage). Do NOT use for "follow up" requests that lack explicit drafting intent (no email address, recipient, or message content) — those route to email-followup first.
From tandemnpx claudepluginhub binatrixai/tandem-marketplace --plugin tandemThis skill is limited to using the following tools:
evals/evals.jsonexamples/tone-samples.mdreferences/examples/tone-samples.mdVerifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Draft email replies or new emails matching the user's preferred tone and communication style.
Detect the user's preferred language from Personal Preferences. By default, match the language of the original email being replied to. If composing a new email, use the user's preferred language.
If language is ambiguous:
AskUserQuestion: "What language should this email be in?"
Options: ["English", "עברית", "Русский", "Same as original"]
This skill requires a connected email tool for sending. Drafts can be created without a connector (user copies/pastes).
If replying to a specific email (from triage or user request):
If composing a new email:
AskUserQuestion: "What type of email are you writing?"
Options: ["Reply to an email", "New email", "Follow-up on a previous email", "Forward with notes"]
Then gather: recipient, subject, key points to cover.
Check Personal Preferences for communication style. If not set or if user wants something different:
AskUserQuestion: "What tone should this email have?"
Options: ["Formal", "Casual", "Follow-up (polite nudge)", "Friendly professional"]
Tone guidelines:
| Tone | Characteristics |
|---|---|
| Formal | Full sentences, proper salutation/closing, no contractions, professional vocabulary |
| Casual | Conversational, first-name basis, contractions OK, brief and direct |
| Follow-up | Polite but assertive, references previous communication, clear ask |
| Friendly professional | Warm but competent, balanced formality, personable without being too casual |
Use the right structure based on the email type:
| Type | Key Elements |
|---|---|
| Cold outreach | Lead with value/relevance, not yourself. Why should they care? One clear CTA |
| Follow-up | Reference the previous interaction specifically. Add new value — never just "checking in" |
| Negotiation | State position clearly with "I'd like to propose" — not "I was wondering if maybe" |
| Update / status | Lead with the headline. Details below. End with next steps |
| Saying no | Be direct and kind. Give a brief reason. Offer an alternative if possible |
| Introduction | Who you are (1 sentence), why reaching out (1 sentence), what you're asking (1 sentence) |
| Thank you | Be specific about what you're thanking them for. Generic thanks = forgettable |
| Apology | Acknowledge what happened, take responsibility, state what you're doing about it. No excuses |
| Request | State the ask upfront. Explain why briefly. Make it easy to say yes |
Generate the draft following these rules:
Hebrew-specific:
Russian-specific:
Show the draft with clear formatting:
**To:** [recipient]
**Subject:** [subject line]
---
[Draft body]
---
Then:
AskUserQuestion: "How does this draft look?"
Options: ["Send as-is", "Edit — I'll tell you what to change", "Change tone", "Shorter", "Longer", "More formal", "More casual", "Try a different angle", "Draft a follow-up version", "Discard"]
If "Edit": Ask what to change, revise, and present again If "Change tone": Show tone options again, redraft If "Shorter"/"Longer": Adjust length and present again If "Send as-is": Send via connected email tool (or confirm copy/paste if no connector)
After sending or finalizing:
~/Tandem/email/MEMORY.md under Session Log| Rule | Why |
|---|---|
| Subject line must be specific | "Q1 Budget Proposal — Review by Friday" not "Following up" or "Quick question" |
| First sentence must earn the second | If the opening is boring, they stop reading |
| Max 5 sentences per paragraph | Walls of text don't get read on any device |
| One clear call to action | Don't make them guess what you want next |
| Match their energy | If they wrote 3 sentences, don't write 3 paragraphs |
| Proofread as the recipient | Read it from their perspective — does it sound pushy? Passive? Unclear? |
Always remove these padding phrases — they add words without adding meaning:
After completing a draft, suggest 1-2 of these:
Memory is user-triggered only. Offer to remember:
See examples/tone-samples.md for drafts in each tone style.