--- name: email-draft description: Use when the user asks to draft, polish, translate, or reply to an email. Produces a clean draft with subject line, greeting, body, and sign-off, plus a pre-send self-check. version: 1.0.0 author: Hope Agent license: MIT metadata: hermes: tags: [office, email, communication, writing, productivity] related_skills: [meeting-notes, status-report] --- # Email Draft ## When to Use Trigger phrases: "draft an email", "reply to this email", "polish this email", "翻译这封邮件", "write an email to ". Don't trigger for: chat messages, Slack DMs, in-app notifications, marketing copy. Those are different formats. ## Output Format Always produce the draft in this layout. Use a fenced code block so the user can copy it cleanly: ``` Subject: Hi , Best, ``` If the language isn't English, adapt greeting and sign-off to the local convention: - 中文: `，你好` / `祝好，` - 日本語: `様` / `よろしくお願いいたします。` - Français: `Bonjour ,` / `Cordialement, ` - 한국어: `님께` / `감사합니다, ` ## Workflow 1. **Clarify minimal essentials** via `ask_user_question` if missing: - Recipient and rough relationship (peer / manager / external client / cold outreach) - One-sentence purpose ("schedule a meeting" / "decline a vendor" / "ask for clarification") - Tone (formal / collegial / brief) - Preferred language - Any constraints to mention (deadline, budget, link to attachment) 2. **Subject line first** — the subject is what gets read. Make it specific and action-oriented: - Bad: "Quick question" - Good: "Q3 budget approval — need sign-off by Friday" - Bad: "Following up" - Good: "Followup on June 12 design review action items" 3. **Body** — three paragraph max: - **Paragraph 1**: context / why you're writing - **Paragraph 2**: the specific request, decision, or information - **Paragraph 3**: clear next step (what you want them to do, by when) 4. **Pre-Send Self-Check** — after producing the draft, run through this checklist out loud (in your reply to the user, before the draft): - [ ] Subject is specific and action-oriented (not "Hi" / "Question") - [ ] Recipient name is correct (no "Hi " placeholder left) - [ ] Purpose stated in the first 2 sentences - [ ] Concrete ask with deadline, not vague - [ ] No internal jargon if recipient is external - [ ] Tone matches relationship (formal vs collegial) - [ ] No accidental "Reply All" implications (if forwarding, mention) - [ ] No PII / secrets that shouldn't be in email - [ ] Attachments mentioned in body if any - [ ] Sign-off matches the user's actual name If any box fails, revise the draft before showing it. ## Common Patterns ### Cold outreach (asking for time) ``` Subject: 15 min on ? Hi , I'm at . We're working on , and I noticed your work on . Would you have 15 minutes in the next two weeks for a quick call? I'm happy to share in return / send a written question if that's easier. Either way, thanks for considering. Best, ``` ### Decline (politely) ``` Subject: Re: Hi , Thanks for thinking of me / sending this. I've decided to pass for now because . Specifically, . Happy to revisit if . Best, ``` ### Status escalation (to manager) ``` Subject: blocked on Hi , Quick heads-up: is blocked on as of . Context: <2 sentences max — what's happening and what's at stake>. I'd recommend