What problem does it solve? Sending emails programmatically through SMTP risks accidental sends, invalid recipients, exposed credentials, and unencrypted delivery. This Skill enforces a mandatory draft-review-approve workflow so no email is sent without explicit user approval and validation. ## Core Features & Use Cases - Draft-Review-Approve Workflow: Every email moves through create_draft, review_draft, approve_draft, and send_email stages, with irreversible sends gated behind explicit user confirmation. - Validation and Safety Controls: Recipient address format validation, 25MB attachment limits, TLS/SSL enforcement, and environment-variable-based credential storage. - Template Support: Generate drafts from predefined templates with variable substitution for recurring notifications, reports, and alerts. - Use Case: An operations agent needs to send a daily status report to stakeholders. It creates a draft from a template, presents it for review, waits for approval, then delivers it via SMTP and reports accepted versus rejected recipients. ## Quick Start Ask the agent to draft an email to a recipient with a subject and body, review the draft it presents, then approve it for sending via SMTP.