Update to MisarMail

{
  "description": "Design and build a MisarMail automation workflow — welcome series, drip sequence, re-engagement, or onboarding. Use for \"automate\", \"drip\", \"welcome series\", \"sequence\", or trigger-based email.",
  "included_files": [],
  "name": "build-email-automation",
  "skill_md_contents": "---\nname: build-email-automation\ndescription: Design and build a MisarMail automation workflow — welcome series, drip sequence, re-engagement, or onboarding. Use for \"automate\", \"drip\", \"welcome series\", \"sequence\", or trigger-based email.\n---\n\n# Build an email automation\n\n## 1. Check what already exists\n\n`list_automations` first. Two automations on the same trigger will both fire,\nand the contact receives duplicate mail — a failure users usually discover from\na complaint rather than from the dashboard.\n\n## 2. Design before building\n\nChoose a trigger: `contact_created`, `tag_added`, `campaign_opened`,\n`link_clicked`, or `date_based`. Then lay out the steps with explicit delays\nand explain each choice to the user.\n\nPractical guidance worth stating:\n- First email within an hour of the trigger; the rest spaced 2–4 days.\n- Keep a welcome series to 3–5 emails. Longer sequences bleed unsubscribes.\n- Include an exit condition (a tag applied on conversion) so a converted\n  contact stops receiving the sequence.\n\n## 3. Build it inactive\n\n`create_automation` with `active: false`. Show the result via `get_automation`\nand let the user read the steps back before anything can fire.\n\nOnly call `toggle_automation` with `active: true` after explicit confirmation.\nActivating starts enrolling live contacts immediately.\n\n## Templates\n\n`list_templates` and `create_template` — use `{{variable}}` placeholders and\npreview substitution with `render_template` before wiring a template into a\nstep. An automation that ships `Hi {{first_name}}` to contacts with no first\nname is a visible, embarrassing failure.\n"
}