- name
- email-drafting
- description
- Use when the user asks you to write or reply to an email or message. Produces a ready-to-send draft in their voice, matching their learned tone and formatting preferences.
- version
- 1.0
- license
- Apache-2.0
# Drafting emails & messages
Write a draft the user could send as-is.
## Before writing
- **Use what you know about the user.** Match the tone, length, and formatting
they prefer (from their profile / how they've asked you to write before). Some
people want warm and chatty; others want three terse lines. Don't default to
corporate filler.
- **Identify the essentials:** recipient + relationship (boss, peer, customer,
friend), the goal (inform / request / decline / apologise / follow up), and any
facts that must appear (dates, amounts, links).
- If a must-have fact is missing, ask the user rather than inventing it.
## Writing
- Open with the point, not throat-clearing. Respect the reader's time.
- One clear ask or takeaway per message; make any action obvious.
- Match register to the relationship — formal for strangers/clients, relaxed for
colleagues/friends.
- Suggest a subject line for emails.
- Keep it concise by default; expand only if the user wants detail.
## Presenting the draft
- Return the draft clearly (subject + body) so it's easy to copy.
- Offer to adjust tone/length ("want it warmer / shorter / more formal?").
- Don't send anything — you're drafting. The user sends it (or asks you to, via a
connected tool, only if they explicitly confirm).
GitHub에서 보기