[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71FYHT916M59C2SCKWFZFY5":3,"skill-same:01M71FYHT916M59C2SCKWFZFY5":117},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":95,"commitSha":96,"skillDirectory":97,"forksCount":98,"repositoryHtmlUrl":99,"repositoryHomepageUrl":6,"ownerHtmlUrl":100,"ownerBlogUrl":101,"ownerDescription":102,"updatedAt":103,"install":104,"resources":116},"01M71FYHT916M59C2SCKWFZFY5","resend",null,"Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, automations, events, viewing API request logs, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like \"send an email with Resend\" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_resend_resend\u002Fskill.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[5,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50],"false","verification","contacts","batch","common","logs","api","tasks","when","critical","secret","domains","issues","up","send","api keys","get","webhook","fetch","2026-11-10 10:12:30",false,"---\nname: resend\ndescription: Use when working with the Resend email API — sending transactional emails (single or batch), receiving inbound emails via webhooks, managing email templates, tracking delivery events, managing domains, contacts, broadcasts, webhooks, API keys, automations, events, viewing API request logs, or setting up the Resend SDK. Always use this skill when the user mentions Resend, even for simple tasks like \"send an email with Resend\" — the skill contains critical gotchas (idempotency keys, webhook verification, template variable syntax) that prevent common production issues.\nlicense: MIT\nmetadata:\n    author: resend\n    version: \"3.3.3\"\n    homepage: https:\u002F\u002Fresend.com\u002Fagent-skills\n    source: https:\u002F\u002Fgithub.com\u002Fresend\u002Fresend-skills\n    openclaw:\n        primaryEnv: RESEND_API_KEY\n        requires:\n            env:\n                - RESEND_API_KEY\n        envVars:\n            - name: RESEND_API_KEY\n              required: true\n              description: Resend API key for sending and receiving emails\n            - name: RESEND_WEBHOOK_SECRET\n              required: false\n              description: Webhook signing secret for verifying event payloads\n        links:\n            repository: https:\u002F\u002Fgithub.com\u002Fresend\u002Fresend-skills\n            documentation: https:\u002F\u002Fresend.com\u002Fdocs\u002Fresend-skill\ninputs:\n    - name: RESEND_API_KEY\n      description: Resend API key for sending and receiving emails. Get yours at https:\u002F\u002Fresend.com\u002Fapi-keys\n      required: true\n    - name: RESEND_WEBHOOK_SECRET\n      description: Webhook signing secret for verifying event payloads. Found in the Resend dashboard under Webhooks after creating an endpoint.\n      required: false\nreferences:\n    - sending\n    - receiving.md\n    - templates.md\n    - webhooks.md\n    - domains.md\n    - contacts.md\n    - broadcasts.md\n    - api_keys.md\n    - logs.md\n    - contact_properties.md\n    - segments.md\n    - topics.md\n    - automations.md\n    - events.md\n    - installation.md\n    - fetch-all-templates.mjs\n---\n\n# Resend\n\n## Quick Send — Node.js\n\n```typescript\nimport { Resend } from 'resend';\n\nconst resend = new Resend(process.env.RESEND_API_KEY);\n\nconst { data, error } = await resend.emails.send(\n  {\n    from: 'Acme \u003Conboarding@resend.dev>',\n    to: ['delivered@resend.dev'],\n    subject: 'Hello World',\n    html: '\u003Cp>Email body here\u003C\u002Fp>',\n  },\n  { idempotencyKey: `welcome-email\u002F${userId}` }\n);\n\nif (error) {\n  console.error('Failed:', error.message);\n  return;\n}\nconsole.log('Sent:', data.id);\n```\n\n**Key gotcha:** The Resend Node.js SDK does NOT throw exceptions — it returns `{ data, error }`. Always check `error` explicitly instead of using try\u002Fcatch for API errors.\n\n## Quick Send — Python\n\n```python\nimport resend\nimport os\n\nresend.api_key = os.environ[\"RESEND_API_KEY\"]\n\nemail = resend.Emails.send({\n    \"from\": \"Acme \u003Conboarding@resend.dev>\",\n    \"to\": [\"delivered@resend.dev\"],\n    \"subject\": \"Hello World\",\n    \"html\": \"\u003Cp>Email body here\u003C\u002Fp>\",\n}, idempotency_key=f\"welcome-email\u002F{user_id}\")\n```\n\n### Single vs Batch Decision\n\n| Choose | When |\n|--------|------|\n| **Single** (`POST \u002Femails`) | 1 email, needs attachments, needs scheduling |\n| **Batch** (`POST \u002Femails\u002Fbatch`) | 2-100 distinct emails, no attachments, no scheduling |\n\nBatch is atomic — if one email fails validation, the entire batch fails. Always validate before sending. Batch does NOT support attachments or `scheduled_at`.\n\n### Idempotency Keys (Critical for Retries)\n\nPrevent duplicate emails when retrying failed requests:\n\n| Key Facts | |\n|-----------|---|\n| **Format (single)** | `\u003Cevent-type>\u002F\u003Centity-id>` (e.g., `welcome-email\u002Fuser-123`) |\n| **Format (batch)** | `batch-\u003Cevent-type>\u002F\u003Cbatch-id>` (e.g., `batch-orders\u002Fbatch-456`) |\n| **Expiration** | 24 hours |\n| **Max length** | 256 characters |\n| **Same key + same payload** | Returns original response without resending |\n| **Same key + different payload** | Returns 409 error |\n\n## Quick Receive (Node.js)\n\n```typescript\nimport { Resend } from 'resend';\n\nconst resend = new Resend(process.env.RESEND_API_KEY);\n\nexport async function POST(req: Request) {\n  const payload = await req.text(); \u002F\u002F Must use raw text, not req.json()\n\n  const event = resend.webhooks.verify({\n    payload,\n    headers: {\n      'svix-id': req.headers.get('svix-id'),\n      'svix-timestamp': req.headers.get('svix-timestamp'),\n      'svix-signature': req.headers.get('svix-signature'),\n    },\n    secret: process.env.RESEND_WEBHOOK_SECRET,\n  });\n\n  if (event.type === 'email.received') {\n    \u002F\u002F Webhook has metadata only — call API for body\n    const { data: email } = await resend.emails.receiving.get(\n      event.data.email_id\n    );\n    console.log(email.text);\n  }\n\n  return new Response('OK', { status: 200 });\n}\n```\n\n**Key gotcha:** Webhook payloads do NOT contain the email body. You must call `resend.emails.receiving.get()` separately.\n\n## What Do You Need?\n\n| Task | Reference |\n|------|-----------|\n| **Send a single email** | sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`) — parameters, deliverability, testing |\n| **Send batch emails** | sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`) → sending\u002Fbatch_email_examples.md (`references\u002Fsending\u002Fbatch_email_examples.md`) |\n| **Full SDK examples** (Node.js, Python, Go, cURL) | sending\u002Fsingle_email_examples.md (`references\u002Fsending\u002Fsingle_email_examples.md`) |\n| **Idempotency, retries, error handling** | sending\u002Fbest_practices.md (`references\u002Fsending\u002Fbest_practices.md`) |\n| **Get, list, reschedule, cancel emails** | sending\u002Femail_management.md (`references\u002Fsending\u002Femail_management.md`) |\n| **Receive inbound emails** | receiving.md (`references\u002Freceiving.md`) — domain setup, webhooks, attachments |\n| **Manage templates** (CRUD, variables) | templates.md (`references\u002Ftemplates.md`) — lifecycle, aliases, pagination |\n| **Set up webhooks** (events, verification) | webhooks.md (`references\u002Fwebhooks.md`) — verification, CRUD, retry schedule, IP allowlist |\n| **Manage domains** (create, verify, DNS) | domains.md (`references\u002Fdomains.md`) — regions, TLS, tracking, capabilities |\n| **Manage contacts** (CRUD, properties) | contacts.md (`references\u002Fcontacts.md`) — segments, topics, custom properties |\n| **Send broadcasts** (marketing campaigns) | broadcasts.md (`references\u002Fbroadcasts.md`) — lifecycle, scheduling, template variables |\n| **Manage API keys** | api_keys.md (`references\u002Fapi_keys.md`) — permission scoping, domain restrictions |\n| **View API request logs** | logs.md (`references\u002Flogs.md`) — list and retrieve API call history, debugging |\n| **Define contact properties** | contact_properties.md (`references\u002Fcontact_properties.md`) — custom fields for contacts |\n| **Manage segments** (contact groups) | segments.md (`references\u002Fsegments.md`) — broadcast targeting, contact grouping |\n| **Manage topics** (subscriptions) | topics.md (`references\u002Ftopics.md`) — opt-in\u002Fout preferences, broadcast filtering |\n| **Create automations** (event-driven workflows) | automations.md (`references\u002Fautomations.md`) — steps, connections, runs, conditions |\n| **Define and send events** (automation triggers) | events.md (`references\u002Fevents.md`) — schemas, payloads, contact association |\n| **Install SDK** (8+ languages) | installation.md (`references\u002Finstallation.md`) |\n| **Set up an AI agent inbox** | Install the `agent-email-inbox` skill — covers security levels for untrusted input |\n\n## SDK Version Requirements\n\nAlways install the latest SDK version. These are the minimum versions for full functionality (sending, receiving, webhook verification):\n\n| Language | Package | Min Version | Install |\n|----------|---------|-------------|---------|\n| Node.js | `resend` | >= 6.9.2 | `npm install resend` |\n| Python | `resend` | >= 2.21.0 | `pip install resend` |\n| Go | `resend-go\u002Fv3` | >= 3.1.0 | `go get github.com\u002Fresend\u002Fresend-go\u002Fv3` |\n| Ruby | `resend` | >= 1.0.0 | `gem install resend` |\n| PHP | `resend\u002Fresend-php` | >= 1.1.0 | `composer require resend\u002Fresend-php` |\n| Rust | `resend-rs` | >= 0.20.0 | `cargo add resend-rs` |\n| Java | `resend-java` | >= 4.11.0 | See installation.md (`references\u002Finstallation.md`) |\n| .NET | `Resend` | >= 0.2.1 | `dotnet add package Resend` |\n\n> **If the project already has a Resend SDK installed**, check the version and upgrade if it's below the minimum. Older SDKs may be missing `webhooks.verify()` or `emails.receiving.get()`.\n\nSee installation.md (`references\u002Finstallation.md`) for full installation commands, language detection, and cURL fallback.\n\n## Common Setup\n\n### API Key\n\nStore in environment variable — never hardcode:\n```bash\nexport RESEND_API_KEY=re_xxxxxxxxx\n```\n\nGet your key at [resend.com\u002Fapi-keys](https:\u002F\u002Fresend.com\u002Fapi-keys).\n\n### Detect Project Language\n\nCheck for these files: `package.json` (Node.js), `requirements.txt`\u002F`pyproject.toml` (Python), `go.mod` (Go), `Gemfile` (Ruby), `composer.json` (PHP), `Cargo.toml` (Rust), `pom.xml`\u002F`build.gradle` (Java), `*.csproj` (.NET).\n\n## Common Mistakes\n\n| # | Mistake | Fix |\n|---|---------|-----|\n| 1 | **Retrying without idempotency key** | Always include idempotency key — prevents duplicate sends on retry. Format: `\u003Cevent-type>\u002F\u003Centity-id>` |\n| 2 | **Not verifying webhook signatures** | Always verify with `resend.webhooks.verify()` — unverified events can't be trusted |\n| 3 | **Template variable name mismatch** | Variable names are case-sensitive — must match the template definition exactly. Use triple mustache `{{{VAR}}}` syntax |\n| 4 | **Expecting email body in webhook payload** | Webhooks contain metadata only — call `resend.emails.receiving.get()` for body content |\n| 5 | **Using try\u002Fcatch for Node.js SDK errors** | SDK returns `{ data, error }` — check `error` explicitly, don't wrap in try\u002Fcatch |\n| 6 | **Using batch for emails with attachments** | Batch doesn't support attachments — use single sends instead |\n| 7 | **Testing with fake emails (test@gmail.com)** | Use `delivered@resend.dev` — fake addresses bounce and hurt reputation |\n| 8 | **Sending with draft template** | Templates must be published before sending — call `.publish()` first |\n| 9 | **`html` + `template` in same send call** | Mutually exclusive — remove `html`\u002F`text`\u002F`react` when using template |\n| 10 | **MX record not lowest priority for inbound** | Ensure Resend's MX has the lowest number (highest priority) or emails won't route |\n| 11 | **403 when sending from `resend.dev`** | The default `onboarding@resend.dev` is a sandbox — it can only deliver to your Resend account email. Verify your own domain first |\n| 12 | **403 domain mismatch** | The `from` address domain must exactly match a verified domain. Verified `send.acme.com` but sending from `user@acme.com` will fail |\n| 13 | **Calling Resend API from the browser (CORS)** | The API does not support CORS — this is intentional to protect your API key. Always call from server-side (API routes, serverless functions) |\n| 14 | **401 `restricted_api_key`** | A sending-only API key was used on a non-sending endpoint (domains, contacts, etc.). Create a full-access key instead |\n\n## Cross-Cutting Concerns\n\n### Send + Receive Together\n\nAuto-replies, email forwarding, or any receive-then-send workflow requires both capabilities:\n1. Set up inbound domain first (see receiving.md (`references\u002Freceiving.md`))\n2. Set up sending (see sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`))\n3. Note: batch sending does NOT support attachments or scheduling — use single sends when forwarding with attachments\n\n### AI Agent Inbox\n\nIf your system processes untrusted email content and takes actions (refunds, database changes, forwarding), install the `agent-email-inbox` skill. This applies whether or not AI is involved — any system interpreting freeform email content from external senders needs security measures.\n\n### Marketing Emails\n\nThe sending capabilities in this skill are for **transactional email** (receipts, confirmations, notifications). For marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking, use Resend Broadcasts — see broadcasts.md (`references\u002Fbroadcasts.md`) for the API.\n\n### Domain Warm-up\n\nNew domains must gradually increase sending volume. Day 1 limit: ~150 emails (new domain) or ~1,000 (existing domain). See the warm-up schedule in sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`).\n\n### Testing\n\n**Never test with fake addresses at real email providers** (test@gmail.com, fake@outlook.com) — they bounce and destroy sender reputation.\n\n| Address | Result |\n|---------|--------|\n| `delivered@resend.dev` | Simulates successful delivery |\n| `bounced@resend.dev` | Simulates hard bounce |\n| `complained@resend.dev` | Simulates spam complaint |\n\n### Suppression List\n\nResend automatically suppresses hard-bounced and spam-complained addresses. Sending to suppressed addresses fires the `email.suppressed` webhook event instead of attempting delivery. Manage in Dashboard → Suppressions.\n\n### Webhook Event Types\n\n| Event | Trigger |\n|-------|---------|\n| `email.sent` | API request successful |\n| `email.delivered` | Reached recipient's mail server |\n| `email.bounced` | Permanently rejected (hard bounce) |\n| `email.complained` | Recipient marked as spam |\n| `email.opened` \u002F `email.clicked` | Recipient engagement |\n| `email.delivery_delayed` | Soft bounce, Resend retries |\n| `email.received` | Inbound email arrived |\n| `domain.*` \u002F `contact.*` | Domain\u002Fcontact changes |\n\nSee webhooks.md (`references\u002Fwebhooks.md`) for full details, signature verification, and retry schedule.\n\n## Error Handling Quick Reference\n\n| Code | Action |\n|------|--------|\n| 400, 422 | Fix request parameters, don't retry |\n| 401 | Check API key — `restricted_api_key` means sending-only key used on non-sending endpoint |\n| 403 | Verify domain ownership — common causes: `resend.dev` sandbox, `from` domain mismatch, unverified domain |\n| 409 | Idempotency conflict — use new key or fix payload |\n| 429 | Rate limited — retry with exponential backoff (default rate limit: 2 req\u002Fs) |\n| 500 | Server error — retry with exponential backoff |\n\n## Resources\n\n- [Resend Documentation](https:\u002F\u002Fresend.com\u002Fdocs)\n- [API Reference](https:\u002F\u002Fresend.com\u002Fdocs\u002Fapi-reference)\n- [Dashboard](https:\u002F\u002Fresend.com\u002Femails)\n","# Resend\n\n## Quick Send — Node.js\n\n```typescript\nimport { Resend } from 'resend';\n\nconst resend = new Resend(process.env.RESEND_API_KEY);\n\nconst { data, error } = await resend.emails.send(\n  {\n    from: 'Acme \u003Conboarding@resend.dev>',\n    to: ['delivered@resend.dev'],\n    subject: 'Hello World',\n    html: '\u003Cp>Email body here\u003C\u002Fp>',\n  },\n  { idempotencyKey: `welcome-email\u002F${userId}` }\n);\n\nif (error) {\n  console.error('Failed:', error.message);\n  return;\n}\nconsole.log('Sent:', data.id);\n```\n\n**Key gotcha:** The Resend Node.js SDK does NOT throw exceptions — it returns `{ data, error }`. Always check `error` explicitly instead of using try\u002Fcatch for API errors.\n\n## Quick Send — Python\n\n```python\nimport resend\nimport os\n\nresend.api_key = os.environ[\"RESEND_API_KEY\"]\n\nemail = resend.Emails.send({\n    \"from\": \"Acme \u003Conboarding@resend.dev>\",\n    \"to\": [\"delivered@resend.dev\"],\n    \"subject\": \"Hello World\",\n    \"html\": \"\u003Cp>Email body here\u003C\u002Fp>\",\n}, idempotency_key=f\"welcome-email\u002F{user_id}\")\n```\n\n### Single vs Batch Decision\n\n| Choose | When |\n|--------|------|\n| **Single** (`POST \u002Femails`) | 1 email, needs attachments, needs scheduling |\n| **Batch** (`POST \u002Femails\u002Fbatch`) | 2-100 distinct emails, no attachments, no scheduling |\n\nBatch is atomic — if one email fails validation, the entire batch fails. Always validate before sending. Batch does NOT support attachments or `scheduled_at`.\n\n### Idempotency Keys (Critical for Retries)\n\nPrevent duplicate emails when retrying failed requests:\n\n| Key Facts | |\n|-----------|---|\n| **Format (single)** | `\u003Cevent-type>\u002F\u003Centity-id>` (e.g., `welcome-email\u002Fuser-123`) |\n| **Format (batch)** | `batch-\u003Cevent-type>\u002F\u003Cbatch-id>` (e.g., `batch-orders\u002Fbatch-456`) |\n| **Expiration** | 24 hours |\n| **Max length** | 256 characters |\n| **Same key + same payload** | Returns original response without resending |\n| **Same key + different payload** | Returns 409 error |\n\n## Quick Receive (Node.js)\n\n```typescript\nimport { Resend } from 'resend';\n\nconst resend = new Resend(process.env.RESEND_API_KEY);\n\nexport async function POST(req: Request) {\n  const payload = await req.text(); \u002F\u002F Must use raw text, not req.json()\n\n  const event = resend.webhooks.verify({\n    payload,\n    headers: {\n      'svix-id': req.headers.get('svix-id'),\n      'svix-timestamp': req.headers.get('svix-timestamp'),\n      'svix-signature': req.headers.get('svix-signature'),\n    },\n    secret: process.env.RESEND_WEBHOOK_SECRET,\n  });\n\n  if (event.type === 'email.received') {\n    \u002F\u002F Webhook has metadata only — call API for body\n    const { data: email } = await resend.emails.receiving.get(\n      event.data.email_id\n    );\n    console.log(email.text);\n  }\n\n  return new Response('OK', { status: 200 });\n}\n```\n\n**Key gotcha:** Webhook payloads do NOT contain the email body. You must call `resend.emails.receiving.get()` separately.\n\n## What Do You Need?\n\n| Task | Reference |\n|------|-----------|\n| **Send a single email** | sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`) — parameters, deliverability, testing |\n| **Send batch emails** | sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`) → sending\u002Fbatch_email_examples.md (`references\u002Fsending\u002Fbatch_email_examples.md`) |\n| **Full SDK examples** (Node.js, Python, Go, cURL) | sending\u002Fsingle_email_examples.md (`references\u002Fsending\u002Fsingle_email_examples.md`) |\n| **Idempotency, retries, error handling** | sending\u002Fbest_practices.md (`references\u002Fsending\u002Fbest_practices.md`) |\n| **Get, list, reschedule, cancel emails** | sending\u002Femail_management.md (`references\u002Fsending\u002Femail_management.md`) |\n| **Receive inbound emails** | receiving.md (`references\u002Freceiving.md`) — domain setup, webhooks, attachments |\n| **Manage templates** (CRUD, variables) | templates.md (`references\u002Ftemplates.md`) — lifecycle, aliases, pagination |\n| **Set up webhooks** (events, verification) | webhooks.md (`references\u002Fwebhooks.md`) — verification, CRUD, retry schedule, IP allowlist |\n| **Manage domains** (create, verify, DNS) | domains.md (`references\u002Fdomains.md`) — regions, TLS, tracking, capabilities |\n| **Manage contacts** (CRUD, properties) | contacts.md (`references\u002Fcontacts.md`) — segments, topics, custom properties |\n| **Send broadcasts** (marketing campaigns) | broadcasts.md (`references\u002Fbroadcasts.md`) — lifecycle, scheduling, template variables |\n| **Manage API keys** | api_keys.md (`references\u002Fapi_keys.md`) — permission scoping, domain restrictions |\n| **View API request logs** | logs.md (`references\u002Flogs.md`) — list and retrieve API call history, debugging |\n| **Define contact properties** | contact_properties.md (`references\u002Fcontact_properties.md`) — custom fields for contacts |\n| **Manage segments** (contact groups) | segments.md (`references\u002Fsegments.md`) — broadcast targeting, contact grouping |\n| **Manage topics** (subscriptions) | topics.md (`references\u002Ftopics.md`) — opt-in\u002Fout preferences, broadcast filtering |\n| **Create automations** (event-driven workflows) | automations.md (`references\u002Fautomations.md`) — steps, connections, runs, conditions |\n| **Define and send events** (automation triggers) | events.md (`references\u002Fevents.md`) — schemas, payloads, contact association |\n| **Install SDK** (8+ languages) | installation.md (`references\u002Finstallation.md`) |\n| **Set up an AI agent inbox** | Install the `agent-email-inbox` skill — covers security levels for untrusted input |\n\n## SDK Version Requirements\n\nAlways install the latest SDK version. These are the minimum versions for full functionality (sending, receiving, webhook verification):\n\n| Language | Package | Min Version | Install |\n|----------|---------|-------------|---------|\n| Node.js | `resend` | >= 6.9.2 | `npm install resend` |\n| Python | `resend` | >= 2.21.0 | `pip install resend` |\n| Go | `resend-go\u002Fv3` | >= 3.1.0 | `go get github.com\u002Fresend\u002Fresend-go\u002Fv3` |\n| Ruby | `resend` | >= 1.0.0 | `gem install resend` |\n| PHP | `resend\u002Fresend-php` | >= 1.1.0 | `composer require resend\u002Fresend-php` |\n| Rust | `resend-rs` | >= 0.20.0 | `cargo add resend-rs` |\n| Java | `resend-java` | >= 4.11.0 | See installation.md (`references\u002Finstallation.md`) |\n| .NET | `Resend` | >= 0.2.1 | `dotnet add package Resend` |\n\n> **If the project already has a Resend SDK installed**, check the version and upgrade if it's below the minimum. Older SDKs may be missing `webhooks.verify()` or `emails.receiving.get()`.\n\nSee installation.md (`references\u002Finstallation.md`) for full installation commands, language detection, and cURL fallback.\n\n## Common Setup\n\n### API Key\n\nStore in environment variable — never hardcode:\n```bash\nexport RESEND_API_KEY=re_xxxxxxxxx\n```\n\nGet your key at [resend.com\u002Fapi-keys](https:\u002F\u002Fresend.com\u002Fapi-keys).\n\n### Detect Project Language\n\nCheck for these files: `package.json` (Node.js), `requirements.txt`\u002F`pyproject.toml` (Python), `go.mod` (Go), `Gemfile` (Ruby), `composer.json` (PHP), `Cargo.toml` (Rust), `pom.xml`\u002F`build.gradle` (Java), `*.csproj` (.NET).\n\n## Common Mistakes\n\n| # | Mistake | Fix |\n|---|---------|-----|\n| 1 | **Retrying without idempotency key** | Always include idempotency key — prevents duplicate sends on retry. Format: `\u003Cevent-type>\u002F\u003Centity-id>` |\n| 2 | **Not verifying webhook signatures** | Always verify with `resend.webhooks.verify()` — unverified events can't be trusted |\n| 3 | **Template variable name mismatch** | Variable names are case-sensitive — must match the template definition exactly. Use triple mustache `{{{VAR}}}` syntax |\n| 4 | **Expecting email body in webhook payload** | Webhooks contain metadata only — call `resend.emails.receiving.get()` for body content |\n| 5 | **Using try\u002Fcatch for Node.js SDK errors** | SDK returns `{ data, error }` — check `error` explicitly, don't wrap in try\u002Fcatch |\n| 6 | **Using batch for emails with attachments** | Batch doesn't support attachments — use single sends instead |\n| 7 | **Testing with fake emails (test@gmail.com)** | Use `delivered@resend.dev` — fake addresses bounce and hurt reputation |\n| 8 | **Sending with draft template** | Templates must be published before sending — call `.publish()` first |\n| 9 | **`html` + `template` in same send call** | Mutually exclusive — remove `html`\u002F`text`\u002F`react` when using template |\n| 10 | **MX record not lowest priority for inbound** | Ensure Resend's MX has the lowest number (highest priority) or emails won't route |\n| 11 | **403 when sending from `resend.dev`** | The default `onboarding@resend.dev` is a sandbox — it can only deliver to your Resend account email. Verify your own domain first |\n| 12 | **403 domain mismatch** | The `from` address domain must exactly match a verified domain. Verified `send.acme.com` but sending from `user@acme.com` will fail |\n| 13 | **Calling Resend API from the browser (CORS)** | The API does not support CORS — this is intentional to protect your API key. Always call from server-side (API routes, serverless functions) |\n| 14 | **401 `restricted_api_key`** | A sending-only API key was used on a non-sending endpoint (domains, contacts, etc.). Create a full-access key instead |\n\n## Cross-Cutting Concerns\n\n### Send + Receive Together\n\nAuto-replies, email forwarding, or any receive-then-send workflow requires both capabilities:\n1. Set up inbound domain first (see receiving.md (`references\u002Freceiving.md`))\n2. Set up sending (see sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`))\n3. Note: batch sending does NOT support attachments or scheduling — use single sends when forwarding with attachments\n\n### AI Agent Inbox\n\nIf your system processes untrusted email content and takes actions (refunds, database changes, forwarding), install the `agent-email-inbox` skill. This applies whether or not AI is involved — any system interpreting freeform email content from external senders needs security measures.\n\n### Marketing Emails\n\nThe sending capabilities in this skill are for **transactional email** (receipts, confirmations, notifications). For marketing campaigns to large subscriber lists with unsubscribe links and engagement tracking, use Resend Broadcasts — see broadcasts.md (`references\u002Fbroadcasts.md`) for the API.\n\n### Domain Warm-up\n\nNew domains must gradually increase sending volume. Day 1 limit: ~150 emails (new domain) or ~1,000 (existing domain). See the warm-up schedule in sending\u002Foverview.md (`references\u002Fsending\u002Foverview.md`).\n\n### Testing\n\n**Never test with fake addresses at real email providers** (test@gmail.com, fake@outlook.com) — they bounce and destroy sender reputation.\n\n| Address | Result |\n|---------|--------|\n| `delivered@resend.dev` | Simulates successful delivery |\n| `bounced@resend.dev` | Simulates hard bounce |\n| `complained@resend.dev` | Simulates spam complaint |\n\n### Suppression List\n\nResend automatically suppresses hard-bounced and spam-complained addresses. Sending to suppressed addresses fires the `email.suppressed` webhook event instead of attempting delivery. Manage in Dashboard → Suppressions.\n\n### Webhook Event Types\n\n| Event | Trigger |\n|-------|---------|\n| `email.sent` | API request successful |\n| `email.delivered` | Reached recipient's mail server |\n| `email.bounced` | Permanently rejected (hard bounce) |\n| `email.complained` | Recipient marked as spam |\n| `email.opened` \u002F `email.clicked` | Recipient engagement |\n| `email.delivery_delayed` | Soft bounce, Resend retries |\n| `email.received` | Inbound email arrived |\n| `domain.*` \u002F `contact.*` | Domain\u002Fcontact changes |\n\nSee webhooks.md (`references\u002Fwebhooks.md`) for full details, signature verification, and retry schedule.\n\n## Error Handling Quick Reference\n\n| Code | Action |\n|------|--------|\n| 400, 422 | Fix request parameters, don't retry |\n| 401 | Check API key — `restricted_api_key` means sending-only key used on non-sending endpoint |\n| 403 | Verify domain ownership — common causes: `resend.dev` sandbox, `from` domain mismatch, unverified domain |\n| 409 | Idempotency conflict — use new key or fix payload |\n| 429 | Rate limited — retry with exponential backoff (default rate limit: 2 req\u002Fs) |\n| 500 | Server error — retry with exponential backoff |\n\n## Resources\n\n- [Resend Documentation](https:\u002F\u002Fresend.com\u002Fdocs)\n- [API Reference](https:\u002F\u002Fresend.com\u002Fdocs\u002Fapi-reference)\n- [Dashboard](https:\u002F\u002Fresend.com\u002Femails)\n",{"name":5,"inputs":56,"license":15,"metadata":64,"references":78,"description":7},[57,61],{"name":58,"required":59,"description":60},"RESEND_API_KEY",true,"Resend API key for sending and receiving emails. Get yours at https:\u002F\u002Fresend.com\u002Fapi-keys",{"name":62,"required":52,"description":63},"RESEND_WEBHOOK_SECRET","Webhook signing secret for verifying event payloads. Found in the Resend dashboard under Webhooks after creating an endpoint.",{"author":5,"source":65,"version":66,"homepage":67,"openclaw":68},"https:\u002F\u002Fgithub.com\u002Fresend\u002Fresend-skills","3.3.3","https:\u002F\u002Fresend.com\u002Fagent-skills",{"links":69,"envVars":71,"requires":76,"primaryEnv":58},{"repository":65,"documentation":70},"https:\u002F\u002Fresend.com\u002Fdocs\u002Fresend-skill",[72,74],{"name":58,"required":59,"description":73},"Resend API key for sending and receiving emails",{"name":62,"required":52,"description":75},"Webhook signing secret for verifying event payloads",{"env":77},[58],[79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94],"sending","receiving.md","templates.md","webhooks.md","domains.md","contacts.md","broadcasts.md","api_keys.md","logs.md","contact_properties.md","segments.md","topics.md","automations.md","events.md","installation.md","fetch-all-templates.mjs","master","c2e410e11df4d80d885e0ecf0583ef3c926df736",".ai\u002Fskills\u002Fofficial_resend_resend",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":105,"prompt":115,"zipAvailable":59},[106,109,112],{"tool":107,"command":108},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill resend",{"tool":110,"command":111},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill resend",{"tool":113,"command":114},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill resend","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002F.ai\u002Fskills\u002Fofficial_resend_resend\u002Fskill.md",[],[118,147,169,191,211,231],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":127,"publishedAt":146},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[124],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[128,129,130,131,132,133,134,135,136,137,138,139,140,141,40,142,38,143,144,145],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","route","create","libraries","2026-11-10 13:02:02",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":146},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[153],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[128,155,156,132,157,158,159,160,141,161,40,39,142,162,163,164,165,166,167,168],"react native","native","vercel react native skills","react native skills","modules","performance","apps","mobile","expo","list","mobile performance","platform","animations","for",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":176,"publishedAt":146},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[175],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[128,177,178,132,179,160,180,40,181,39,142,182,183,184,185,186,187,188,189,190],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":198,"publishedAt":146},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[197],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[199,132,200,187,201,202,203,204,190,205,206,207,40,208,39,142,209,210,38,128],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","architecture","react composition",{"skillNo":212,"name":213,"nameZh":6,"description":214,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":215,"categories":216,"keywords":218,"publishedAt":146},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[217],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[219,220,221,222,179,223,224,225,168,188,160,226,227,180,228,207,229,41,230,40],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","database",{"skillNo":232,"name":233,"nameZh":6,"description":234,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":235,"categories":236,"keywords":238,"publishedAt":253},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[237],{"categoryNo":125,"categoryName":126,"taxonomyType":21,"taxonomyTypeDesc":22},[239,240,241,242,243,138,244,204,44,141,245,246,40,128,247,248,249,250,251,252],"text","portable text serialization","portable","serialization","extracting","strings","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]