--- name: message description: >- Create and edit rich text message drafts for Gmail, Outlook, and WhatsApp. Writes small HTML fragments and assembles full preview via build script. Use when writing emails, drafting emails, composing replies, sending messages, writing WhatsApp messages, sending Gmail messages, replying via email, or when user mentions Gmail, Outlook, WhatsApp, email client, "email to", "reply to", "draft an email", "write an email", "send a message", "message to", "WhatsApp to", or professional correspondence. argument-hint: "[optional: path to existing .fragment.html for editing]" allowed-tools: - Bash - Write - Read - Edit --- # Message Drafts Create rich text messages that paste perfectly into Gmail, Outlook, or convert to WhatsApp-formatted text. Uses a fragment architecture - write only the dynamic content, a build script handles the rest. ## Architecture ``` Claude writes Build script assembles Output (separate file) name.fragment.html ---> shell.html + fragment ---> name.html (12-85 lines) (never seen by Claude) (self-contained preview) ``` The fragment is the source of truth. The assembled HTML is a derived output. Never edit the `.html` output directly. ## Create Workflow 1. Draft email content in conversation 2. Write a `.fragment.html` file to `data/writing/email_drafts/` 3. Run the assembler to produce the full preview HTML 4. Launch the preview server ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/message/scripts/assemble.py /path/to/name.fragment.html --serve ``` This single command assembles the fragment into a full HTML preview and launches the server. Run with `run_in_background: true`. ## Edit Workflow When editing an existing email (argument provided, or user asks to change something): 1. Read the small `.fragment.html` file 2. Use the Edit tool to make targeted changes 3. Re-run the assembler to rebuild the preview ```bash python3 ${CLAUDE_PLUGIN_ROOT}/skills/message/scripts/assemble.py /path/to/name.fragment.html --serve ``` This is cheap - read a small file, make a small edit, one bash call. ## Fragment Format ```html

Hi Veronika,

Content here...

Cheers,
Henrik

``` ### Meta Tags | Tag | Required | Default | Notes | |-----|----------|---------|-------| | `to` | Yes | - | Primary recipient(s), comma-separated | | `subject` | Yes | - | Email subject line | | `cc` | No | empty | Hidden in preview if empty | | `bcc` | No | empty | Hidden in preview if empty | | `title` | No | "HTML Email Preview" | Page title shown in preview | Special characters in meta `content` use standard HTML entity encoding (e.g., `&` for &, `"` for quotes). ## File Naming ``` data/writing/email_drafts/YYYY-MM-DD_recipient_subject.fragment.html <-- source (Claude writes/edits) data/writing/email_drafts/YYYY-MM-DD_recipient_subject.html <-- output (build script writes) ``` Examples: - `2026-02-12_veronika_audit-proposal.fragment.html` - `2026-02-12_danielle_project-update.fragment.html` ## Generation Format: Outlook-Native HTML **Always generate Outlook-native HTML** for the fragment body. This is the single generation format because: - Outlook-native HTML degrades gracefully in Gmail (preserves semantic structure) - Gmail HTML breaks in Outlook (no inline styles = broken rendering) ### Essential Formatting Rules **All styles must be inline.** Outlook strips `

email

Scan your own AI components