Update to AB

{
  "description": "Draft and — only with explicit confirmation — send follow-up email to a lead in AB Sales (ActionBridge CRM), grounded in the lead's history, then log the outcome. Use when the user wants to follow up with, reply to, email, or reach out to a lead or prospect.",
  "included_files": [],
  "name": "ab-lead-outreach",
  "skill_md_contents": "---\r\nname: ab-lead-outreach\r\ndescription: Draft and — only with explicit confirmation — send follow-up email to a lead in AB Sales (ActionBridge CRM), grounded in the lead's history, then log the outcome. Use when the user wants to follow up with, reply to, email, or reach out to a lead or prospect.\r\n---\r\n\r\n# Lead outreach in AB Sales\r\n\r\nPersonalized follow-up email with a strict confirmation gate: **a real email leaves the building.**\r\n\r\n## Ground the draft\r\n\r\n1. Resolve workspace (`ab_crm_workspaces`) and lead (`ab_crm_list_leads` with `query`, then `ab_crm_get_lead`).\r\n2. Read the history before writing a word: `ab_crm_list_notes` and `ab_crm_list_emails` for the lead, `ab_crm_list_activities` for scheduled touchpoints. The draft must reference something real (their stated need, the last conversation) — never send a generic blast.\r\n\r\n## Draft\r\n\r\nPlain text (the tool does not interpret HTML; line breaks are preserved). Keep it short: 3 short paragraphs at most — context hook, the value/next step, a single clear ask. Subject: specific and small (\"Next step on the pilot\", not \"Following up\"). Show the user the full draft — subject and body — and ask for explicit confirmation to send.\r\n\r\n## Send — the hard rules\r\n\r\n- **Never call `ab_crm_send_email_to_lead` without the user's explicit yes to the exact draft shown.** Any edit means show it again.\r\n- The server enforces its own guardrails and will answer `Refused:` when the lead has opted out, workspace automation is paused, or no outbound mailbox is configured. Relay refusals as-is and stop — do not look for another way to send.\r\n- One send per confirmation. Sending again requires asking again.\r\n\r\nCall with `workspace_id`, `lead_id`, `subject`, `body`. The send is logged on the lead automatically.\r\n\r\n## After sending\r\n\r\nClose the loop: `ab_crm_complete_activity` (with an `outcome`) if this send fulfills a scheduled follow-up, and `ab_crm_create_activity` for the next touchpoint (default ~1 week out) so the thread never dangles. Confirm to the user: sent from which mailbox, to whom, and when the next follow-up is scheduled.\r\n\r\n## If the user only wanted a draft\r\n\r\nDeliver the draft and offer to store it as a note on the lead (`ab_crm_add_note`) — don't leave good writing stranded in chat.\r\n"
}