Email Draft

Overview

Compose a clean email draft from intent and caller-supplied nuances, then save it to Gmail Drafts for review before sending.

When to Use

• Any time an email body needs drafting and saving to Gmail Drafts
• Called by other skills after they resolve the target thread/recipient

Default Style

• No greetings or sign-offs unless caller explicitly requests them
• Open directly with the substance; no preamble or filler
• Prefer bullets over prose for structured information
• No references to Obsidian, vault paths, or internal tools
• Keep it brief — say only what the recipient needs
• Use Markdown freely — the gmail CLI renders it to HTML (bold, lists, headers, links all display in Gmail)

Inputs from Caller

The invoking skill must provide:

• Content/intent: what the email communicates (summaries, decisions, amounts, etc.)