Menu
Compose professional emails from brief instructions, bullet points, or context
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/kmavrodis/kratos-agent --skill email-draftThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Showing SKILL.md
Based on SOC occupation classification
| name | email-draft |
| description | Compose professional emails from brief instructions, bullet points, or context |
| enabled | true |
When the user asks you to write, draft, or compose an email, follow these guidelines:
Before drafting, identify:
If the user provides bullet points or rough notes, expand them into polished prose. If context is vague, ask one clarifying question — do not over-ask.
Always produce a complete email with:
Subject: <concise, actionable subject line>
<Greeting>,
<Opening — context or purpose in 1-2 sentences>
<Body — organized paragraphs or bullet list covering all key points>
<Closing — clear next step or call to action>
<Sign-off>,
<Name placeholder>
| Audience | Tone | Example greeting |
|---|---|---|
| Executive / C-suite | Formal, concise, results-focused | "Dear [Name]," |
| Colleague / team | Professional-friendly | "Hi [Name]," |
| External client | Warm but professional | "Dear [Name]," |
| Support / vendor | Direct and clear | "Hello [Team]," |
If the user asks for multiple options, provide 2-3 versions with different tones (e.g. formal vs. friendly) and let them pick.
If the user asks to revise, adjust tone, shorten, or expand — iterate on the previous draft rather than starting from scratch.
If the user wants the email saved as a file:
code_interpreter to write the email to /tmp/email_draft.txt (or .md)[placeholder] markers[Your Name]User: "Write an email to my manager asking for time off next week"
Output:
Subject: PTO Request — [Date Range]
Hi [Manager Name],
I'd like to request paid time off from [Start Date] through [End Date]. I've ensured my current deliverables are on track and will hand off any pending items to [Colleague Name] before I leave.
Please let me know if you need any additional details or if this timing works for the team.
Thanks,
[Your Name]
User: "Draft a client follow-up after our demo yesterday, mention the pricing proposal"
Output:
Subject: Great Connecting Yesterday — Next Steps on Pricing
Dear [Client Name],
Thank you for taking the time to join yesterday's demo. It was great to walk through the platform with your team, and I appreciated the thoughtful questions.
As discussed, I've attached our pricing proposal for your review. Here's a quick summary:
- **Starter tier**: [details]
- **Enterprise tier**: [details]
- **Custom options**: Available based on your team's requirements
I'd love to schedule a follow-up call next week to discuss any questions. Would [Day] at [Time] work for you?
Looking forward to hearing from you.
Best regards,
[Your Name]