email-senderlisted

Send, or preview and show, email delivery of a vault note (digest or research) to your distribution list. Delivery is deterministic — Markdown rendered to styled HTML with the raw `.md` attached, via a committed `render_and_send.py` (no AI call). Scheduled digests auto-send to everyone on the list; research notes prompt `[y/n]` first. A `show_list` action loads and prints the distribution list — who would receive the next send — without sending anything. Recipients come from a plain-Markdown list at `vault/_config/email-distribution.md`. Use when the user asks to email, send, forward, or distribute a digest or research note to their list, OR to show, list, view, preview, check, or validate their email distribution list (who's on it, who would get the next digest) — and immediately after `vault-writer.write_digest` or `vault-writer.write_research` succeeds. Not for composing an ad-hoc personal email or answering a generic SMTP question.
themarmack/research-bot · ★ 0 · AI & Automation · score 68

Install: claude install-skill themarmack/research-bot

# email-sender The post-write distribution hook. Every vault write worth surfacing beyond the local Obsidian copy goes through here. Scheduled digests fire-and-forget to the distribution list; ad-hoc research notes prompt the user `[y/n]` before sending. The vault note remains the canonical record; email is a delivery channel, not a replacement. ## When to use - Immediately after `vault-writer.write_digest()` succeeds — invoked from `scheduled-agent-runner` step 11. - Immediately after `vault-writer.write_research()` succeeds in any Category 1 researcher — researcher invokes `prompt_then_send`. - User explicitly asks: "email this", "send the latest weekly digest to my distribution list", "show me my distribution list". ## When NOT to use - Writes to `facts/`, `events/`, `decisions/`, `insights/`, `people/`, `projects/`, `_inbox/` — durable knowledge, not distribution targets. (`auto_send` no-ops on these surfaces.) - Non-interactive context AND surface is `research` — `prompt_then_send` requires a user; degrade gracefully by skipping. - Mid-stream (vault write hasn't completed yet — wait for the write). ## Prerequisites Two pieces of config: 1. **Gmail credentials** at `~/.config/research-bot/env`: ``` GMAIL_SEND_ADDRESS=you@gmail.com GMAIL_APP_PASSWORD=xxxxxxxxxxxxxxxx ``` Requires 2-Step Verification enabled on the account. Generate at https://myaccount.google.com/apppasswords ("Mail" → "Other / research-bot"). Use the helper script: `scripts/set-gmai