Update to Emailit

{
  "description": "This skill should be used when the user asks \"why did my email bounce\", \"why are my emails going to spam\", \"was this email delivered\", \"check my DMARC reports\", \"clean my email list\", \"remove a suppression\", \"lower my bounce rate\", or \"improve deliverability\" in Emailit. Covers investigating delivery status, bounces, complaints, suppressions, DMARC data, list verification, and sending practices.",
  "included_files": [
    {
      "relative_path": "references/dmarc.md",
      "size_in_bytes": 1916
    },
    {
      "relative_path": "references/statuses.md",
      "size_in_bytes": 2422
    }
  ],
  "name": "emailit-deliverability",
  "skill_md_contents": "---\nname: emailit-deliverability\ndescription: This skill should be used when the user asks \"why did my email bounce\", \"why are my emails going to spam\", \"was this email delivered\", \"check my DMARC reports\", \"clean my email list\", \"remove a suppression\", \"lower my bounce rate\", or \"improve deliverability\" in Emailit. Covers investigating delivery status, bounces, complaints, suppressions, DMARC data, list verification, and sending practices.\n---\n\n# Emailit deliverability\n\nAnswer with evidence from the account, not general advice. Pull the data first, then explain the cause and the fix.\n\n## Investigate one email\n\n1. Find it: `list-emails` with `rcpt_to`, `subject`, or `mail_from`, plus `date_from` and `date_to`. Use `status` to narrow to `bounced`, `failed`, `rejected`, `suppressed`, `complained`, or `held`.\n2. Open it: `get-email` with the ID. Read:\n   - `status`: the current state. Meanings are in `references/statuses.md`.\n   - `deliveries[]`: each delivery attempt with `status`, `output` (the receiving server's SMTP reply), and `details`. The SMTP reply is the most useful evidence for a bounce.\n   - `spam_score` and `spam_checks`: Emailit's own content scan.\n   - `sending_domain`: the SPF, DKIM, DMARC, and return path status of the domain it was sent from.\n3. Explain the cause in plain words, quoting the SMTP reply. Then give one concrete fix.\n\nCommon SMTP replies:\n\n| Reply contains | Meaning | Fix |\n| --- | --- | --- |\n| `550 5.1.1`, \"user unknown\", \"does not exist\" | Hard bounce: the mailbox does not exist | Remove the address. Emailit suppresses it automatically if auto suppression is on |\n| `552`, \"mailbox full\", \"over quota\" | Mailbox full | Retry later with `retry-email`; remove if it repeats |\n| `421`, `451`, \"try again later\", \"rate limited\" | Temporary deferral | Nothing; Emailit retries. Status stays `attempted` meanwhile |\n| `550 5.7.1`, \"spam\", \"policy\", \"blocked\" | Content or reputation block | Check DMARC alignment, spam score, links, and recent complaint rate |\n| \"SPF\", \"DKIM\", \"DMARC\", \"authentication\" | Authentication failed | Fix the domain records (`emailit-domain-setup`) |\n\n## Investigate a trend\n\n- Volume and outcomes: `list-emails` with `status` and a date range; compare counts for `delivered`, `bounced`, and `complained`.\n- Workspace events: `list-events` with `type` such as `email.bounced` or `email.complained` and `include_data: true`.\n- Per domain authentication: `get-dmarc-stats`, `list-dmarc-sources`, and `list-dmarc-reporters` for the domain. See `references/dmarc.md`.\n\nBenchmarks to compare against: bounce rate under 2 percent, complaint rate under 0.1 percent. Higher numbers put the account's reputation at risk and can pause sending.\n\n## Suppressions\n\nWhat a suppression blocks depends on its type and on how the email is sent:\n\n- **API and SMTP sends** are blocked only by a `recipient` suppression. The email gets status `suppressed`. `bounce`, `complaint`, and `unsubscribe` entries do not stop them.\n- **Campaigns** skip every address with a suppression of any type, plus unsubscribed contacts and subscribers.\n- A suppression whose `keep_until` has passed no longer blocks anything.\n\nManaging them:\n\n- Automatic suppression (a workspace setting) adds a `recipient` suppression after bounces and a `complaint` suppression after a spam complaint. Pro and Business can limit it to one of the two or turn it off; other plans always have both on.\n- Find one: `list-suppressions` with `search`. Read it with `get-suppression`.\n- Add one: `create-suppression` with `email`, an optional `type` (default `recipient`, the only type that also stops API and SMTP sends), an optional `reason`, and optional `keep_until`.\n- Remove one: `delete-suppression`. Only do this when the user confirms the address is valid and the person wants the email. Never remove a `complaint` or `unsubscribe` suppression just to get a campaign out; that breaks consent rules and hurts reputation.\n\n## Verify addresses before sending\n\n- One address: `verify-email` with `mode: \"fast\"` (syntax, MX, disposable, role) or `\"full\"` (adds an SMTP mailbox check). Both use verification credits; tell the user before running them.\n- A list: `create-verification-list`, then poll `get-verification-list` until it finishes, then `get-verification-list-results`. Results are `safe`, `invalid`, `disposable`, `disabled`, `inbox_full`, `role`, or `unknown`. Suggest removing `invalid`, `disabled`, and `disposable` addresses, and reviewing `role`, `inbox_full`, and `unknown` ones before mailing them.\n\n## Checklist for \"my emails go to spam\"\n\nWork through these with real data and report each one:\n\n1. **Authentication**: `get-domain` shows SPF, DKIM, and return path `ok`. A DMARC record exists.\n2. **Alignment**: DMARC stats show passing alignment for Emailit sources. Unknown sources sending as the domain point to spoofing or a forgotten service.\n3. **List quality**: recent bounce rate under 2 percent. Run list verification on old or imported lists.\n4. **Complaints**: complaint rate under 0.1 percent. Every marketing email needs a working unsubscribe; campaign emails get a List-Unsubscribe header automatically.\n5. **Content**: `spam_score` on recent emails. Avoid link shorteners, image only emails, and mismatched link text.\n6. **Consistency**: a recognizable from name and address, and a steady sending volume. Warm up new domains by starting small.\n7. **Separation**: transactional and marketing mail on different subdomains.\n\n## Retrying\n\n`retry-email` works only for `bounced`, `failed`, `suppressed`, or `held` emails less than 30 days old. It sends a new copy to the recipient with a new email ID, and a `recipient` suppression still blocks it. Confirm with the user, and do not retry hard bounces to addresses that do not exist.\n"
}