Update to SMTPing Email Verifier

{
  "description": "Verify email addresses with SMTPing before sending, importing or storing them. Use when the user asks to verify, validate, check or clean one email address or a list (pasted text, CSV, CRM export), wants to know which contacts are safe to email, asks about bounces, disposable, spamtrap, spambot or complainer addresses, or asks for their SMTPing credit balance.",
  "included_files": [],
  "name": "verify-emails",
  "skill_md_contents": "---\nname: verify-emails\ndescription: Verify email addresses with SMTPing before sending, importing or storing them. Use when the user asks to verify, validate, check or clean one email address or a list (pasted text, CSV, CRM export), wants to know which contacts are safe to email, asks about bounces, disposable, spamtrap, spambot or complainer addresses, or asks for their SMTPing credit balance.\n---\n\n# Verify email addresses with SMTPing\n\nVerify addresses with the SMTPing tools and turn the results into a clear decision for the user: send, remove, or review.\n\n## Tools\n\n- `verify_email`: one address.\n- `verify_list`: several addresses as one bulk job (up to 100,000 unique addresses). Lists of 10 or fewer return results directly; larger lists return a `job_id`.\n- `get_bulk_job`: progress and results of a bulk job.\n- `check_threat`: one address against one threat list (spamtrap, disposable, spambot or complainer).\n- `get_credits`: remaining credit balance and plan.\n\n## Before verifying\n\n- Deduplicate the list (lowercase, trim). Skip values that are not email addresses and tell the user how many you skipped.\n- Each verified address uses one credit. Before verifying more than 100 addresses, state the number of unique addresses and ask for confirmation.\n- For a single address, prefer `verify_email`. Use `check_threat` only when the user asks about one specific list.\n\n## Bulk jobs\n\n1. Call `verify_list` once with the deduplicated list.\n2. If it returns a `job_id`, call `get_bulk_job` until the status is `Succeeded`, `Failed` or `Cancelled`.\n3. Large jobs can take minutes. If the user does not want to wait, give them the `job_id` so they can ask for the results later.\n\n## Reading the results\n\nReport by band:\n\n| band | statuses | what to tell the user |\n| --- | --- | --- |\n| safe | valid, alias | Send. |\n| avoid | invalid, spamtrap, disposable, blacklisted, complainer, spambot, inbox_full | Remove before sending. |\n| judgement | catch_all, unknown, role and anything else | Review. Send only to engaged or high-value contacts, in small batches. |\n\nExplain the risky ones in one line each when they appear:\n\n- **spamtrap**: address used to catch senders with poor list hygiene. One hit can damage domain reputation. Always remove.\n- **complainer**: known to mark mail as spam. Remove.\n- **disposable**: throwaway inbox, usually gone within hours. Remove from marketing lists, block at signup.\n- **catch_all**: the domain accepts every address, so the mailbox cannot be confirmed. Judgement call.\n- **role** (info@, sales@): shared inbox, higher complaint rate. Fine for B2B replies, avoid for bulk marketing.\n\n## Output\n\n- One address: the status, the band, and one sentence on what to do.\n- A list: totals per band, the count per status, then the addresses to remove. Offer a table with columns email, status, band when the list is longer than about 20 rows.\n- Never claim an address is \"guaranteed deliverable\". Verification lowers bounce risk; it does not guarantee inbox placement.\n\n## Errors\n\n- Not enough credits: tell the user and stop; do not retry.\n- Temporary errors: retry once, then report the problem.\n\n## Limits\n\n- Only verify addresses the user has a legitimate reason to process. Verification is list hygiene, not a way to find or identify people.\n- Do not send email, find addresses or edit contacts. SMTPing only checks addresses.\n\nVerdict guide: https://smtping.com/13-verdict-types-guide\n"
}