Update to Send & Retain Emails

{
  "description": "Triage a deliverability problem in Send & Retain — bounce or complaint spikes, blocked or failing sends — by quantifying it, finding where it comes from, and recommending a fix. Use when the user reports bounces, spam complaints, or mail not arriving.",
  "included_files": [],
  "name": "triage-deliverability",
  "skill_md_contents": "---\nname: triage-deliverability\ndescription: Triage a deliverability problem in Send & Retain — bounce or complaint spikes, blocked or failing sends — by quantifying it, finding where it comes from, and recommending a fix. Use when the user reports bounces, spam complaints, or mail not arriving.\n---\n\n# Triage deliverability\n\n1. **Quantify.** `email_get_email_metrics` for the affected window: bounce and\n   complaint rates against the period before it.\n2. **Localize.** `email_search_messages` filtered to bounced, complained or\n   failed: which template, which recipient domains, and when it started.\n3. **Inspect.** `email_get_message` on representative failures, and read the\n   provider's bounce classification in the event timeline.\n4. **Check infrastructure.** `email_get_connection_status`, then\n   `email_verify_domain` to re-read it: is the domain still verified, are the DNS\n   records intact?\n5. **Diagnose** — list hygiene, content, infrastructure, or a volume spike — and\n   recommend the fix. If sending should stop while it is fixed, say so\n   explicitly: `email_set_sends_paused` is the user's call to make, so call it\n   only on their go-ahead.\n6. **Confirm suppressions** are in place for the bad addresses\n   (`email_list_suppressions`). Never remove a complaint suppression; the\n   platform refuses to.\n"
}