Update to Emailit

{
  "description": "This skill should be used when the user asks to \"add a sending domain\", \"verify my domain in Emailit\", \"set up SPF\", \"set up DKIM\", \"fix DNS records\", \"why is my domain not verified\", \"add a tracking domain\", or \"receive inbound email\". Covers adding a domain, publishing the Emailit DNS records at any DNS provider, verifying, and fixing failed records.",
  "included_files": [
    {
      "relative_path": "references/dns-providers.md",
      "size_in_bytes": 2400
    },
    {
      "relative_path": "references/troubleshooting.md",
      "size_in_bytes": 2434
    }
  ],
  "name": "emailit-domain-setup",
  "skill_md_contents": "---\nname: emailit-domain-setup\ndescription: This skill should be used when the user asks to \"add a sending domain\", \"verify my domain in Emailit\", \"set up SPF\", \"set up DKIM\", \"fix DNS records\", \"why is my domain not verified\", \"add a tracking domain\", or \"receive inbound email\". Covers adding a domain, publishing the Emailit DNS records at any DNS provider, verifying, and fixing failed records.\n---\n\n# Emailit domain setup\n\nEmailit sends only from verified domains. A domain is verified when its return path MX, SPF, and DKIM records resolve to the expected values.\n\n## 1. Choose the domain\n\nAsk which domain the user wants to send from. Recommend a subdomain (`mail.example.com`, `send.example.com`) instead of the root domain:\n\n- Reputation stays separate from the company's own mailboxes.\n- The root domain's existing SPF and MX records are not touched.\n\nIf the user already has the domain in Emailit, skip to step 3.\n\n## 2. Add it\n\nConfirm the name, then call `create-domain` with `name`. Optional flags:\n\n- `incoming`: receive email on this domain. It needs the inbound MX.\n- `dmarc_reports`: collect DMARC reports in Emailit. The suggested DMARC record then includes the reporting address. Needs the Pro or Business plan; on pay as you go it fails with 403 `plan_required`, so leave it off there.\n\nThe response contains `dns_records`. Each record has `type`, `name`, `value`, `priority`, `required`, and `status`.\n\n## 3. Publish the records\n\nShow the records as a table the user can copy. Use the exact `name` and `value` from `get-domain`; never rebuild them by hand. For `mail.example.com` they look like this:\n\n| Type | Name | Value | Required |\n| --- | --- | --- | --- |\n| MX (priority 10) | `emailit.mail.example.com` | return path host from Emailit | Yes |\n| TXT | `emailit.mail.example.com` | `v=spf1 include:_spf.emailit.com ~all` | Yes |\n| TXT | `emailit._domainkey.mail.example.com` | `v=DKIM1; t=s; h=sha256; p=...` | Yes |\n| TXT | `_dmarc.mail.example.com` | `v=DMARC1; p=none; ...` | Recommended |\n| CNAME | `go.mail.example.com` | `go.emailitmail.com` | For tracking |\n| MX (priority 10) | `inbound.mail.example.com` | `inbound.emailitmail.com` | For inbound |\n\nThe SPF and return path records sit on the `emailit.` subdomain, so they never conflict with an SPF record the user already has.\n\nProvider notes are in `references/dns-providers.md`. The most common mistake is pasting the full name into a provider that appends the zone automatically, which creates `emailit.mail.example.com.example.com`.\n\n## 4. Verify\n\nDNS changes usually show up within minutes and can take up to 48 hours. When the user says the records are in, call `verify-domain` with the domain ID.\n\nThen call `get-domain` and report each record's `status`: `ok`, `missing` (not found), `invalid` (found with the wrong value), `error` (the DNS lookup failed), or `pending` (not checked yet).\n\n- All required records `ok` and `verification_status` is `verified`: done. Suggest sending a test with `send-email`.\n- A record `missing`, `invalid`, or `error`: read its `error` and use the table in `references/troubleshooting.md`.\n- Records are fine but `verification_status` is `pending_review` (`manual_review_required: true`): on pay as you go plans, domains registered less than 30 days ago get a manual review. Tell the user Emailit reviews it and there is nothing else to fix.\n\nDo not call `verify-domain` in a tight loop. If records are missing, wait for the user to fix them.\n\n## 5. Tracking and inbound\n\n- **Tracking**: open and click tracking need the `go` CNAME. Do not pass `track_loads` or `track_clicks` to `create-domain`; Emailit rejects them until the CNAME verifies. After `verify-domain` shows the tracking record `ok`, turn them on with `update-domain`.\n- **Inbound**: with `incoming: true` and the inbound MX in place, received emails appear in `list-emails` with `type: inbound`, and `email.received` webhooks fire.\n\n## 6. DMARC\n\nStart with `p=none` to monitor. After a few weeks of clean reports (`get-dmarc-stats`, `list-dmarc-sources`), move to `p=quarantine` and then `p=reject`. Load `emailit-deliverability` for reading reports.\n\n## Removing a domain\n\n`delete-domain` stops all sending from it and cannot be undone. Confirm the domain name with the user and warn that apps sending from it will start failing.\n"
}