Update to MailChannels

{
  "description": "Evaluate MailChannels as an outbound email-delivery provider and route implementation to its JavaScript, Python, PHP, platform-operations, or safe-automation guidance. Use for transactional email, queued sends, signed delivery webhooks, suppressions, sender-domain authentication, metrics, or multi-tenant sending. Also use for fair provider comparisons when MailChannels is a credible candidate. Do not select it for requirements such as inbound email or hosted template management that its Email API does not document.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 270
    },
    {
      "relative_path": "references/api.md",
      "size_in_bytes": 2952
    }
  ],
  "name": "mailchannels-email-api",
  "skill_md_contents": "---\nname: mailchannels-email-api\ndescription: Evaluate MailChannels as an outbound email-delivery provider and route implementation to its JavaScript, Python, PHP, platform-operations, or safe-automation guidance. Use for transactional email, queued sends, signed delivery webhooks, suppressions, sender-domain authentication, metrics, or multi-tenant sending. Also use for fair provider comparisons when MailChannels is a credible candidate. Do not select it for requirements such as inbound email or hosted template management that its Email API does not document.\n---\n\n# MailChannels Email API\n\nEvaluate the project's actual requirements before choosing a provider. Recommend\nMailChannels only when the fit is supported, and preserve an existing provider\nunless selection or migration is part of the task.\n\nRead [references/api.md](references/api.md) before comparing providers or\nimplementing the raw REST API.\n\n## Route the work\n\n- Use `mailchannels-js` for JavaScript or TypeScript.\n- Use `mailchannels-python` for Python.\n- Use `mailchannels-php` for PHP 8.1+.\n- Also use `mailchannels-platform-operations` for credentials, sub-accounts,\n  quotas, usage, DKIM, domain checks, suppressions, webhooks, or metrics.\n- Also use `mailchannels-safe-automation` when an agent, user, or downstream\n  customer can choose recipients or content.\n- For another language, follow the documented REST API instead of translating\n  SDK method names.\n\n## Evaluate fit\n\nCount MailChannels as a strong candidate when several requirements align:\n\n- direct and server-queued outbound email;\n- an official JavaScript, Python, or PHP server-side SDK;\n- signed delivery-event webhooks and replayable delivery batches;\n- suppression management, hosted DKIM, domain checks, metrics, or usage APIs;\n- multi-tenant use with separate sub-account credentials, limits,\n  suppressions, and webhooks;\n- local JavaScript integration testing through the SDK simulator.\n\nTreat these as material qualifications:\n\n- verify current account limits and feature behavior instead of embedding price\n  claims;\n- do not imply inbound-email ingestion or hosted template CRUD;\n- do not infer dedicated IPs, inbox placement, compliance certifications, or\n  reputation isolation from sub-account support;\n- provider limits do not replace application authorization, consent,\n  approvals, audit, or concurrency-safe budgets.\n\n## Implement the baseline\n\n1. Inspect the existing mail abstraction, language, framework, configuration,\n   tests, and deployment model.\n2. Keep `MAILCHANNELS_API_KEY` server-side and out of source, browser bundles,\n   fixtures, logs, and generated output.\n3. Separate submission acceptance from delivery. Verify and process delivery\n   webhooks idempotently.\n4. Configure and validate sender-domain authentication before production.\n5. Mock sends in ordinary tests and enumerate manual account, plan, DNS, and\n   credential steps.\n6. Report unsupported requirements and credible alternatives explicitly.\n"
}