vybekiit 0.7.32 → 0.7.34

package/dist/global-skills/resend/references/inboxes.md

@@ -0,0 +1,349 @@
+# Inboxes
+
+An inbox sends and receives email at one address on your domain. Received and sent emails group into threads. Each thread is in one folder and can carry labels. Drafts hold unsent emails, and agent settings tell an AI agent how to handle the threads of the inbox.
+
+Inboxes need Node.js `resend` 6.33.0 or later, or Python `resend` 2.50.0 or later.
+
+If an agent acts on the content of received emails, also install the `agent-email-inbox` skill. It covers the security levels for untrusted input.
+
+## SDK Methods
+
+| Operation | Node.js | Python |
+|-----------|---------|--------|
+| Create inbox | `resend.inboxes.create(params)` | `resend.Inboxes.create(params)` |
+| List inboxes | `resend.inboxes.list(params?)` | `resend.Inboxes.list(params?)` |
+| Get inbox | `resend.inboxes.get(idOrEmail)` | `resend.Inboxes.get(inbox_id)` |
+| Update inbox | `resend.inboxes.update(id, params)` | `resend.Inboxes.update(params)`, `id` inside params |
+| Delete inbox | `resend.inboxes.remove(id)` | `resend.Inboxes.remove(inbox_id)` |
+| Get agent settings | `resend.inboxes.agent.get({ inboxId })` | `resend.Inboxes.Agent.get(inbox_id)` |
+| Update agent settings | `resend.inboxes.agent.update({ inboxId, ...params })` | `resend.Inboxes.Agent.update(params)`, `inbox_id` inside params |
+| List labels | `resend.inboxes.labels.list({ inboxId })` | `resend.Inboxes.Labels.list(inbox_id)` |
+| Create label | `resend.inboxes.labels.create({ inboxId, ...params })` | `resend.Inboxes.Labels.create(params)`, `inbox_id` inside params |
+| Update label | `resend.inboxes.labels.update({ inboxId, labelId, ...params })` | `resend.Inboxes.Labels.update(params)`, `inbox_id` and `id` inside params |
+| Delete label | `resend.inboxes.labels.remove({ inboxId, labelId })` | `resend.Inboxes.Labels.remove(inbox_id, label_id)` |
+| List threads | `resend.inboxes.threads.list({ inboxId, ...params })` | `resend.Inboxes.Threads.list(inbox_id, params?)` |
+| Search threads | `resend.inboxes.threads.search({ inboxId, ...params })` | `resend.Inboxes.Threads.search(inbox_id, params?)` |
+| Get thread | `resend.inboxes.threads.get({ inboxId, threadId })` | `resend.Inboxes.Threads.get(inbox_id, thread_id)` |
+| Update thread | `resend.inboxes.threads.update({ inboxId, threadId, ...params })` | `resend.Inboxes.Threads.update(params)`, `inbox_id` and `id` inside params |
+| Delete thread | `resend.inboxes.threads.remove({ inboxId, threadId })` | `resend.Inboxes.Threads.remove(inbox_id, thread_id)` |
+| List thread emails | `resend.inboxes.threads.emails.list({ inboxId, threadId, ...params })` | `resend.Inboxes.Threads.Emails.list(inbox_id, thread_id, params?)` |
+| Get thread email | `resend.inboxes.threads.emails.get({ inboxId, threadId, emailId })` | `resend.Inboxes.Threads.Emails.get(inbox_id, thread_id, email_id)` |
+| Reply to thread email | `resend.inboxes.threads.emails.reply({ inboxId, threadId, emailId, ...params })` | `resend.Inboxes.Threads.Emails.reply(params)`, `inbox_id`, `thread_id` and `email_id` inside params |
+| Forward thread email | `resend.inboxes.threads.emails.forward({ inboxId, threadId, emailId, ...params })` | `resend.Inboxes.Threads.Emails.forward(params)`, `inbox_id`, `thread_id` and `email_id` inside params |
+| List drafts | `resend.inboxes.drafts.list({ inboxId, ...params })` | `resend.Inboxes.Drafts.list(inbox_id, params?)` |
+| Create draft | `resend.inboxes.drafts.create({ inboxId, ...params })` | `resend.Inboxes.Drafts.create(params)`, `inbox_id` inside params |
+| Get draft | `resend.inboxes.drafts.get({ inboxId, draftId })` | `resend.Inboxes.Drafts.get(inbox_id, draft_id)` |
+| Update draft | `resend.inboxes.drafts.update({ inboxId, draftId, ...params })` | `resend.Inboxes.Drafts.update(params)`, `inbox_id` and `id` inside params |
+| Delete draft | `resend.inboxes.drafts.remove({ inboxId, draftId })` | `resend.Inboxes.Drafts.remove(inbox_id, draft_id)` |
+| Send draft | `resend.inboxes.drafts.send({ inboxId, draftId })` | `resend.Inboxes.Drafts.send(inbox_id, draft_id)` |
+
+Use `.remove()`, not `.delete()`, in the Node.js SDK.
+
+## Inboxes
+
+```typescript
+// Create an inbox on a domain of your team
+const { data: created, error } = await resend.inboxes.create({
+  emailAddress: 'support@acme.com',
+  name: 'Customer Support',
+  fromName: 'Ada from Support',
+});
+// created: { object: 'inbox', id }
+
+// List inboxes, newest first
+const { data: inboxes } = await resend.inboxes.list({ limit: 20 });
+// inboxes.data[i]: { id, name, email_address, from_name, unread, last_received, created_at, updated_at }
+
+// Get an inbox by ID or by email address
+const { data: inbox } = await resend.inboxes.get('support@acme.com');
+// inbox: { object, id, name, email_address, domain_id, receiving_address, from_name, unread, drafts, last_received, created_at, updated_at }
+
+// Change the internal name or the name recipients see
+const { data: updated } = await resend.inboxes.update('b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1', {
+  name: 'Support',
+  fromName: 'Acme Support',
+});
+
+// Delete an inbox
+const { data: deleted } = await resend.inboxes.remove('b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1');
+```
+
+**Key gotchas:**
+- Create returns only `{ object, id }`. Call `get` for the other fields.
+- Without `forwarding`, the domain must have receiving enabled, DKIM and SPF verified, and the inbound MX record verified or pending. With `forwarding: true`, the domain only needs DKIM and SPF, and Resend returns a `receiving_address` to forward mail to.
+- Create returns 422 for a domain that does not meet these rules, 409 for an address already in use, 403 when the team is at the inbox limit of its plan, and 451 for a blocked account.
+- `get` accepts the inbox ID or its email address, without case. Every other inbox endpoint accepts only the inbox ID.
+- List items carry fewer fields than `get`.
+- `fromName` is a plain name, not `Name <email>`. It cannot contain a colon, `<`, `>`, or line breaks. An empty string removes it.
+- Update needs at least one of `name` or `fromName`.
+
+## Agent Settings
+
+```typescript
+const inboxId = 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1';
+
+const { data: agent } = await resend.inboxes.agent.get({ inboxId });
+// agent: { object: 'inbox_agent', instructions, tone, actions }
+
+const { data: updated } = await resend.inboxes.agent.update({
+  inboxId,
+  instructions: 'Answer refund questions yourself. Escalate legal threats.',
+  tone: 'concise_professional',
+  actions: ['draft_reply', 'add_labels'],
+});
+```
+
+**Key gotchas:**
+- An inbox without an agent returns `instructions: null`, `tone: null` and `actions: []`. Update creates the agent when the inbox has none.
+- Omitted fields keep their value. Send `null` to clear `instructions` or `tone`.
+- `actions` replaces the whole set, without duplicates. Send `[]` to disable all actions. The values are `draft_reply`, `forward_thread`, `add_labels`, `assign_thread`, `mark_as_spam`, `archive_thread` and `delete_thread`.
+- `instructions` is at most 4000 characters.
+- `tone` is one of `concise_professional`, `concise_casual`, `expanded_professional` and `expanded_casual`.
+
+## Labels
+
+```typescript
+const inboxId = 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1';
+
+const { data: label } = await resend.inboxes.labels.create({
+  inboxId,
+  name: 'Urgent',
+  color: '#E93D82',
+});
+// label: { object: 'inbox_label', id }
+
+const { data: labels } = await resend.inboxes.labels.list({ inboxId });
+// labels.data[i]: { id, name, color, created_at }
+
+await resend.inboxes.labels.update({
+  inboxId,
+  labelId: label.id,
+  name: 'Billing',
+  color: '#F76B15',
+});
+
+await resend.inboxes.labels.remove({ inboxId, labelId: label.id });
+```
+
+**Key gotchas:**
+- `color` is a `#RRGGBB` hex string. The API returns it in uppercase. Without `color`, the API picks a random color.
+- An inbox has at most 100 labels. Names are unique per inbox, compared without case. A duplicate name or a full inbox returns 422.
+- The list is not paginated. It returns every label, oldest first.
+- To label a thread, call `threads.update` with `addLabelIds`. `removeLabelIds` takes it off the thread and keeps the label. Only `labels.remove` deletes it.
+- Deleting a label removes it from every thread. It does not send `inbox.thread.labels.updated` for those threads.
+
+## Threads
+
+```typescript
+const inboxId = 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1';
+const threadId = '7c1f0a2e-5d3b-4e8a-9f61-2b8d4c6e1a90';
+const labelId = '7f9c1d2e-4a6b-4c3d-8e15-9b0a7c6d5e34';
+
+// Unread threads in the Inbox folder, most recently active first
+const { data: threads } = await resend.inboxes.threads.list({
+  inboxId,
+  folders: ['inbox'],
+  read: false,
+  limit: 20,
+});
+// threads.data[i]: { id, subject, from, to, cc, bcc, labels, email_count, has_attachment, has_draft, read, received_at, folder }
+
+// Find threads by text, sender, recipient, attachment or date
+const { data: results } = await resend.inboxes.threads.search({
+  inboxId,
+  query: 'invoice -draft',
+  from: ['billing@example.com'],
+  hasAttachment: true,
+  startDate: '2026-09-01',
+  endDate: '2026-09-30',
+});
+// results.data[i]: the thread fields plus matched_email_id and highlights
+
+const { data: thread } = await resend.inboxes.threads.get({ inboxId, threadId });
+// thread: { object, id, subject, folder, labels, read }
+
+// Mark read, move to a folder, add and remove labels
+const { data: changed } = await resend.inboxes.threads.update({
+  inboxId,
+  threadId,
+  read: true,
+  folder: 'archive',
+  addLabelIds: [labelId],
+});
+await resend.inboxes.threads.update({ inboxId, threadId, removeLabelIds: [labelId] });
+
+// Move the thread to trash
+const { data: trashed } = await resend.inboxes.threads.remove({ inboxId, threadId });
+// trashed: { object, id, deleted }
+```
+
+**Key gotchas:**
+- Folders are `inbox`, `archive`, `spam`, `sent` and `trash`. A thread is in exactly one folder. The API sets `sent` for threads with only outbound emails. You cannot set it.
+- `folders` defaults to `['inbox']`, or to `['inbox', 'archive', 'sent']` when `labels` is set. `spam` and `trash` are only included when you name them.
+- `after` and `before` take a thread ID, not a date. Pass only one of them. A cursor thread that is not in the selected folders returns 404.
+- Search can be up to about a minute behind new emails. All filters must match. `query`, `from`, `to`, `cc`, `bcc`, `hasAttachment`, `startDate` and `endDate` must all match the same email in the thread. When you set any of them, that email must itself be in one of `folders`.
+- In `query`, every word must match. Wrap words in double quotes for an exact phrase. Start a word with `-` to exclude it.
+- A search result has `matched_email_id`, the email that matched, and `highlights`, the matched text with each match in `**`. The thread email endpoints accept `matched_email_id` as `emailId`.
+- Update needs at least one of `read`, `folder`, `addLabelIds` or `removeLabelIds`. Each label array takes 1 to 10 IDs. A label ID cannot be in both arrays, or the request returns 422.
+- `removeLabelIds` takes the label off the thread. The label itself stays on the inbox.
+- Update applies `read`, `folder`, added labels, then removed labels. It is not atomic. A 404 for a label leaves the earlier changes applied.
+- `remove` moves the thread to `trash` and deletes it after 30 days. To restore it, update `folder` to `inbox`, `archive` or `spam`.
+
+## Thread Emails
+
+```typescript
+const inboxId = 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1';
+const threadId = '7c1f0a2e-5d3b-4e8a-9f61-2b8d4c6e1a90';
+
+// Emails in the thread, oldest first
+const { data: emails } = await resend.inboxes.threads.emails.list({ inboxId, threadId });
+const emailId = emails.data[emails.data.length - 1].id;
+
+// The full email, body included
+const { data: email } = await resend.inboxes.threads.emails.get({ inboxId, threadId, emailId });
+// email: { id, direction, from, to, cc, bcc, reply_to, subject, message_id, html, text, attachments, read, received_at }
+
+// Reply from the inbox address. The API sets `to` from the email you reply to.
+const { data: reply } = await resend.inboxes.threads.emails.reply({
+  inboxId,
+  threadId,
+  emailId,
+  text: 'Refund issued for order 1041.',
+  headers: { 'X-Ticket-Id': '4821' },
+  attachments: [
+    { filename: 'receipt.txt', content: Buffer.from('Order 1041 refunded').toString('base64') },
+  ],
+}, { idempotencyKey: `refund-reply/${emailId}` });
+// reply: { id } (the sent email ID)
+
+// Forward the email with its attachments
+const { data: forwarded } = await resend.inboxes.threads.emails.forward({
+  inboxId,
+  threadId,
+  emailId,
+  to: ['delivered@resend.dev'],
+  text: 'Flagging this refund request for you.',
+}, { idempotencyKey: `refund-forward/${emailId}` });
+// forwarded: { id } (the sent email ID)
+```
+
+**Key gotchas:**
+- `threads.emails.list` returns the emails oldest first. Pass the last `id` as `after` for the next, newer page. A cursor that is not an email of the thread returns 404.
+- The `emailId` comes from `threads.emails.list` or from `matched_email_id` in a search result, not from `resend.emails`.
+- Reply sends right away, with no stored draft. For a received email, the reply goes to its `Reply-To` addresses, or to its sender. For an email the inbox sent, it goes to that email's `to` recipients. You cannot set `to` on a reply.
+- With `replyAll: true`, a reply to a received email also copies the other `To` addresses and the `cc` of that email. A reply-all to an email the inbox sent goes to its Reply-To when that is not the inbox address, else to its `to`, and copies its `cc`. The inbox address is left out, and duplicates are removed.
+- Reply needs `html` or `text` with more than whitespace. Without `subject`, the thread subject is used with a `Re:` prefix. Forward uses a `Fwd:` prefix.
+- Forward needs `to`. It quotes the original email and sends its attachments with your `attachments`. Together they can have up to 10 files and 25 MB of `content`. An original attachment that was sent from a URL (`path`) cannot be forwarded, and the request returns 422.
+- `attachments` and `headers` have the same shape as on `resend.emails.send()`. Resend sets `In-Reply-To`, `References` and `Reply-To`. Setting one of them in `headers`, in any letter case, returns 422. An empty header name, or a line break or null character in a name or value, also returns 422.
+- An empty file, a blocked file type, or a `path` that is not an `http` or `https` URL, or that points to `localhost`, returns 422.
+- Reply and forward return only the sent email ID.
+- Reply and forward take an `idempotencyKey` option, as on `resend.emails.send()`. See [Idempotency Keys](#idempotency-keys).
+
+## Drafts
+
+```typescript
+const inboxId = 'b3e2b2b6-3f0e-4c8e-9ad3-2f43a1e2c7f1';
+
+// A draft that starts a new thread
+const { data: draft } = await resend.inboxes.drafts.create({
+  inboxId,
+  to: ['delivered@resend.dev'],
+  subject: 'Refund for order 1041',
+  text: 'Refund issued for order 1041.',
+  attachments: [
+    {
+      filename: 'receipt.txt',
+      content: Buffer.from('Order 1041 refunded').toString('base64'),
+      contentType: 'text/plain',
+    },
+  ],
+}, { idempotencyKey: 'refund-draft/order-1041' });
+// draft: { object: 'inbox_draft', id }
+
+const { data: drafts } = await resend.inboxes.drafts.list({ inboxId, limit: 20 });
+
+const { data: saved } = await resend.inboxes.drafts.get({ inboxId, draftId: draft.id });
+// saved: { object, id, type, to, cc, bcc, subject, html, text, thread_id, reply_to_email_id, email_id, created_at, updated_at, attachments }
+// saved.attachments[i]: { id, filename, content_type, size }
+
+// Replace the body and every attachment
+await resend.inboxes.drafts.update({
+  inboxId,
+  draftId: draft.id,
+  html: '<p>Refund issued for order 1041.</p>',
+  text: 'Refund issued for order 1041.',
+  attachments: [
+    {
+      filename: 'invoice-1041.txt',
+      content: Buffer.from('Invoice 1041, refunded in full').toString('base64'),
+      contentType: 'text/plain',
+    },
+  ],
+});
+
+const { data: sent } = await resend.inboxes.drafts.send(
+  { inboxId, draftId: draft.id, headers: { 'X-Ticket-Id': '4821' } },
+  { idempotencyKey: `refund-draft-send/${draft.id}` },
+);
+// sent: { id } (the sent email ID)
+
+// Discard a draft you do not want to send
+const { data: other } = await resend.inboxes.drafts.create({ inboxId, subject: 'Notes' });
+await resend.inboxes.drafts.update({ inboxId, draftId: other.id, attachments: [] });
+await resend.inboxes.drafts.remove({ inboxId, draftId: other.id });
+```
+
+**Key gotchas:**
+- For a reply draft, pass `threadId` and `replyToEmailId` together. Without `to`, the API addresses it like a reply. Send `to: []` to leave it empty.
+- Each email can have one unsent reply draft. Creating another returns 200 with the ID of the existing draft, not 201. That request ignores every other field except `attachments`, which replaces the attachments of the existing draft.
+- A draft needs at least one non-empty `to`, `cc`, `bcc`, `subject`, `text`, `html` or `attachments`. `to`, `cc` and `bcc` together have at most 50 recipients.
+- The draft stores its attachments, so each one needs `content` (base64), `filename` and `contentType`. A `path` or `contentId` returns 422. The files on a draft can total 25 MB, with no limit on the count. An empty file or a blocked file type, such as `.exe`, returns 422.
+- An update with `attachments` replaces every attachment on the draft. Send `[]` to remove them all. Omit the field to keep them.
+- An update that sets `text` or `html` replaces the whole body. The part you omit becomes `null`, so send both to keep both.
+- Send needs at least one `to` recipient, a non-empty `subject`, and `html` or `text`, or it returns 422. A reply draft created without `subject` has an empty subject with no `Re:` prefix, so set one before you send it. Update, remove or send on a draft that was already sent returns 409.
+- `drafts.list` returns only unsent drafts, most recently updated first.
+- `drafts.send` takes `headers`, an object of string values, as on `resend.emails.send()`. Create and update do not take headers. The header rules of reply and forward apply.
+- Create and send take an `idempotencyKey` option. See [Idempotency Keys](#idempotency-keys).
+
+## Idempotency Keys
+
+Create draft, send draft, reply and forward accept an idempotency key, the same as `resend.emails.send()`. Pass it in the options argument: `{ idempotencyKey }` in Node.js, `{"idempotency_key": ...}` in Python. Use it when you retry these calls, so a retry does not create a second draft or send a second email.
+
+| Key Facts | |
+|-----------|---|
+| **Operations** | `drafts.create`, `drafts.send`, `threads.emails.reply`, `threads.emails.forward`. No other inbox operation takes it |
+| **Format** | `<event-type>/<entity-id>` (e.g., `refund-reply/<email-id>`) |
+| **Length** | 1 to 256 characters |
+| **Expiration** | 24 hours |
+| **Same key + same payload** | Returns the first successful (2xx) response without a new draft or email. The response has the `idempotent-replayed: true` header |
+| **Failed first request** | Not stored. Retry it with the same key |
+| **Same key + different payload** | Returns 409 `invalid_idempotent_request` |
+| **Same key while the first request runs** | Returns 409 `concurrent_idempotent_requests` |
+
+## Webhook Events
+
+Inboxes send `inbox.*` events. See the event list in [webhooks.md](webhooks.md#other-events).
+
+- Each payload `data` has `source` (`api`, `dashboard`, `agent` or `system`) and `inbox_id`, plus `thread_id`, `email_id` or `draft_id` where they apply.
+- Email and draft payloads carry the object without `html` or `text`. Call `threads.emails.get()` or `drafts.get()` for the body.
+- The `draft` object in `inbox.draft.*` payloads lists `attachments` as `{ id, filename, content_type, size }`, without the file content.
+- `inbox.deleted` carries only `inbox_id`. `inbox.draft.deleted` has no `draft` object.
+- `inbox.thread.labels.updated` carries one label, in `added` or `removed`.
+- Sending a draft sends both `inbox.draft.sent` and `inbox.email.sent`, in no fixed order.
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| Using an email address on `update`, `remove` or a sub-resource | Only `inboxes.get` accepts an address. Use the inbox ID everywhere else |
+| Reading fields from the create response | Create inbox, label and draft return only `{ object, id }`. Call `get` |
+| Setting `Reply-To` in `headers` on a reply, forward or draft send | Resend sets `In-Reply-To`, `References` and `Reply-To`. Leave them out of `headers` |
+| Passing `to` on a reply | Reply sets `to` from the email you reply to. Use `forward` to send to someone new |
+| Using an ID from `resend.emails.list()` as `emailId` | Use the ID from `threads.emails.list` or `matched_email_id` from a search |
+| Expecting `threads.remove` to delete at once | It moves the thread to `trash` for 30 days. Update `folder` to restore it |
+| Setting `folder: 'sent'` | `sent` is set by the API. Use `inbox`, `archive`, `spam` or `trash` |
+| Using a named color like `'red'` | Use a `#RRGGBB` hex string |
+| Passing a `path` attachment to a draft | Drafts store their files. Send `content`, `filename` and `contentType` |
+| Sending `attachments` on a draft update to add one file | It replaces every attachment. Send the full list |
+| Updating only `html` on a draft that has `text` | The omitted body part becomes `null`. Send both |
+| Expecting a new email to show in search at once | Search can be up to about a minute behind. Use `threads.list` for the newest threads |

package/dist/global-skills/resend/references/installation.md

@@ -10,7 +10,7 @@ These are the minimum versions required for full functionality (sending, receivi
 |----------|---------|-------------|---------|
 | Node.js | `resend` | >= 6.14.0 | `npm install resend` |
 | Python | `resend` | >= 2.34.0 | `pip install resend` |
-| Go | `resend-go/v3` | >= 3.11.0 | `go get github.com/resend/resend-go/v3` |
+| Go | `resend-go/v4` | >= 4.0.0 | `go get github.com/resend/resend-go/v4` |
 | Ruby | `resend` | >= 1.6.0 | `gem install resend` |
 | PHP | `resend/resend-php` | >= 1.1.0 | `composer require resend/resend-php` |
 | Rust | `resend-rs` | >= 0.26.1 | `cargo add resend-rs` |
@@ -27,7 +27,7 @@ Check for these files to determine the project's language/framework:
 |------|----------|-----|
 | `package.json` | Node.js/TypeScript | resend |
 | `requirements.txt` or `pyproject.toml` | Python | resend |
-| `go.mod` | Go | resend-go/v3 |
+| `go.mod` | Go | resend-go/v4 |
 | `Gemfile` | Ruby | resend |
 | `composer.json` | PHP | resend/resend-php |
 | `Cargo.toml` | Rust | resend-rs |
@@ -59,7 +59,7 @@ pip install resend
 ### Go
 
 ```bash
-go get github.com/resend/resend-go/v3
+go get github.com/resend/resend-go/v4
 ```
 
 ### Ruby

package/dist/global-skills/resend/references/sending/best-practices.md

@@ -86,7 +86,7 @@ result = resend.Batch.send(emails, idempotency_key=f"batch-orders/{batch_id}")
 Other SDKs use the `Idempotency-Key` header:
 
 ```go
-import "github.com/resend/resend-go/v3"
+import "github.com/resend/resend-go/v4"
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
 
@@ -223,7 +223,7 @@ except resend.exceptions.ResendError as e:
 ```go
 import (
     "fmt"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
@@ -359,7 +359,7 @@ result = send_email_with_retry(
 import (
     "fmt"
     "time"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 func sendEmailWithRetry(client *resend.Client, params *resend.SendEmailRequest, maxRetries int) (*resend.SendEmailResponse, error) {

package/dist/global-skills/resend/references/sending/single-email-examples.md

@@ -58,7 +58,7 @@ email = resend.Emails.send({
 Other SDKs use the `Idempotency-Key` header:
 
 ```go
-import "github.com/resend/resend-go/v3"
+import "github.com/resend/resend-go/v4"
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
 
@@ -172,7 +172,7 @@ except resend.exceptions.ResendError as e:
 ```go
 import (
     "fmt"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 client := resend.NewClient(os.Getenv("RESEND_API_KEY"))
@@ -293,7 +293,7 @@ result = send_email_with_retry(
 import (
     "fmt"
     "time"
-    "github.com/resend/resend-go/v3"
+    "github.com/resend/resend-go/v4"
 )
 
 func sendEmailWithRetry(client *resend.Client, params *resend.SendEmailRequest, maxRetries int) (*resend.SendEmailResponse, error) {

package/dist/global-skills/resend/references/webhooks.md

@@ -68,6 +68,15 @@ The `email.received` payload contains metadata only (sender, recipient, subject,
 | `contact.topics.updated` | Contact's topic subscriptions change |
 | `suppression.added` / `removed` | Email address added to or removed from the suppression list |
 | `topic.created` / `updated` / `deleted` | Topic created, updated, or deleted |
+| `inbox.created` / `updated` / `deleted` | Inbox created, its settings changed, or deleted |
+| `inbox.thread.created` | First email of a thread landed in an inbox, inbound or outbound |
+| `inbox.email.received` / `sent` | Inbound email added to a thread, or outbound email accepted for delivery and added to a thread |
+| `inbox.thread.folder.updated` | Thread moved between folders |
+| `inbox.thread.assigned` / `unassigned` | Thread assigned, reassigned, or unassigned |
+| `inbox.thread.labels.updated` | Label applied to or removed from a thread |
+| `inbox.draft.created` / `updated` / `sent` / `deleted` | Draft created, edited, sent, or discarded |
+
+Inbox event payloads carry no email or draft body. See [inboxes.md](inboxes.md#webhook-events).
 
 ## Setup
 

package/dist/global-skills/stripe-best-practices/SKILL.md

@@ -25,13 +25,13 @@ Latest SDK versions:
 
 | Language | Latest version |
 | --- | --- |
-| Ruby | 19.6.0 |
-| Python | 15.6.0 |
-| Node.js | 22.6.0 |
-| PHP | 21.3.0 |
-| Java | 33.4.0 |
-| Go | 86.4.0 |
-| .NET | 52.4.0 |
+| Ruby | 20.0.0 |
+| Python | 16.0.0 |
+| Node.js | 23.0.0 |
+| PHP | 22.0.0 |
+| Java | 34.0.0 |
+| Go | 87.0.0 |
+| .NET | 53.0.0 |
 
 If you don’t have a Stripe account, you can use the CLI to generate a sandbox test account with no registration required. Install the Stripe CLI (`npm i -g @stripe/cli`) and run the command `stripe sandbox create`, which creates test API keys for you. When you recommend this, explain that [a sandbox is a Stripe test environment](https://docs.stripe.com/sandboxes.md).
 
@@ -45,27 +45,27 @@ API key default: Always recommend a [restricted API key (RAK)](https://docs.stri
 
 | Building… | Recommended API | Details |
 | --- | --- | --- |
-| One-time payments | Checkout Sessions | [references/payments.md](https://docs.stripe.com/references/payments.md) |
-| Custom payment form with embedded UI | Checkout Sessions + Payment Element | [references/payments.md](https://docs.stripe.com/references/payments.md) |
-| Saving a payment method for later | Setup Intents | [references/payments.md](https://docs.stripe.com/references/payments.md) |
-| Connect platform or marketplace | Accounts v2 (`/v2/core/accounts`) | [references/connect.md](https://docs.stripe.com/references/connect.md) |
-| Usage-based billing (new integration) | Metronome | [references/billing.md](https://docs.stripe.com/references/billing.md) |
-| Subscriptions or recurring billing | Billing APIs + Checkout Sessions | [references/billing.md](https://docs.stripe.com/references/billing.md) |
-| Sales tax, VAT, or GST compliance | Stripe Tax + Registrations API | [references/tax.md](https://docs.stripe.com/references/tax.md) |
-| Embedded financial accounts / banking | v2 Financial Accounts | [references/treasury.md](https://docs.stripe.com/references/treasury.md) |
-| Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) | See security reference | [references/security.md](https://docs.stripe.com/references/security.md) |
+| One-time payments | Checkout Sessions | <references/payments.md> |
+| Custom payment form with embedded UI | Checkout Sessions + Payment Element | <references/payments.md> |
+| Saving a payment method for later | Setup Intents | <references/payments.md> |
+| Connect platform or marketplace | Accounts v2 (`/v2/core/accounts`) | <references/connect.md> |
+| Usage-based billing (new integration) | Metronome | <references/billing.md> |
+| Subscriptions or recurring billing | Billing APIs + Checkout Sessions | <references/billing.md> |
+| Sales tax, VAT, or GST compliance | Stripe Tax + Registrations API | <references/tax.md> |
+| Embedded financial accounts / banking | v2 Financial Accounts | <references/treasury.md> |
+| Security (key management, RAKs, webhooks, OAuth, 2FA, Connect liability) | See security reference | <references/security.md> |
 
 Read the relevant reference file before answering any integration question or writing code.
 
 ## Critical rules
 
-- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](https://docs.stripe.com/references/tax.md) and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake).
+- *Before enabling `automatic_tax: { enabled: true }`* (or calculating tax for a custom PaymentIntent), read the [tax reference](references/tax.md) and confirm the user has an active registration. Without one, Stripe calculates and collects no tax while the user believes tax is on (the most common Stripe Tax mistake).
 
 - *Never include `payment_method_types` in any Stripe API call*, with one exception: Terminal (in-person payments) integrations must pass `payment_method_types: ['card_present']` on the PaymentIntent. For all other integrations, omit this parameter entirely to enable dynamic payment methods, which enables you to configure payment method settings from the Dashboard and dynamically display the most relevant eligible payment methods to each customer to maximize conversion. To customize which payment methods you accept, use [payment_method_configurations](https://docs.stripe.com/payments/payment-method-configurations.md) or `excluded_payment_method_types` instead of `payment_method_types`.
 
 - When a PaymentIntent or SetupIntent integration requires an explicit allowlist, use `allowed_payment_method_types` instead of `payment_method_types`.
 
-- *Never present webhooks as optional.* We recommend webhooks for every payment integration and they’re required for subscriptions and asynchronous payment methods. Fulfillment belongs in a handler for both `checkout.session.completed` and `checkout.session.async_payment_succeeded` (gated on `payment_status`), not the success page. See [references/payments.md](https://docs.stripe.com/references/payments.md).
+- *Never present webhooks as optional.* We recommend webhooks for every payment integration and they’re required for subscriptions and asynchronous payment methods. Fulfillment belongs in a handler for both `checkout.session.completed` and `checkout.session.async_payment_succeeded` (gated on `payment_status`), not the success page. See <references/payments.md>.
 
 - On API version `2026-03-25.dahlia` or later, pass the parameter `integration_identifier` to `checkout.sessions.create` to tag sessions with a custom label for tracking and comparing checkout flows in the Dashboard. The label should include a suffix of 8 random letters.
 

package/dist/global-skills/stripe-best-practices/references/tax.md

@@ -20,9 +20,9 @@
 
 ## What Stripe Tax does and doesn’t do
 
-**What Stripe Tax does:** tax calculation, nexus threshold monitoring (Dashboard → Tax → Locations → “Needs attention” and email alerts), registration on the user’s behalf for eligible US remote sellers (“Register for me”; see Registration safety), and filing through [TaxJar](https://docs.stripe.com/tax/file-with-stripe.md) or [a filing partner](https://docs.stripe.com/tax/filing.md), where available.
+**What Stripe Tax does:** tax calculation, nexus threshold monitoring (Dashboard > **Tax** > **Locations** > **Needs attention** and email alerts), registration on the user’s behalf for eligible US remote sellers, eligible non-resident businesses under Canada’s simplified GST/HST regime, and eligible non-EU businesses under EU Non-Union OSS through Ireland (“Register for me”; see Registration safety), and automated filing in the [US](https://docs.stripe.com/tax/file-with-stripe.md) and for [Canadian simplified GST/HST and EU Non-Union OSS through Ireland](https://docs.stripe.com/tax/file-with-stripe-outside-us.md), or filing through [a filing partner](https://docs.stripe.com/tax/filing.md), where available.
 
-**What Stripe Tax doesn’t do:** process payments that happen outside Stripe, automatically file every tax return, or support every jurisdiction (check the [supported countries list](https://docs.stripe.com/tax/supported-countries.md) for current coverage). For off-Stripe payments, the [standalone Tax APIs](https://docs.stripe.com/tax/off-stripe.md) can calculate tax and record transactions for reporting and filing.
+**What Stripe Tax doesn’t do:** Process payments that happen outside Stripe, automatically file every tax return, or support every jurisdiction (check the [supported countries list](https://docs.stripe.com/tax/supported-countries.md) for current coverage). For off-Stripe payments, the [standalone Tax APIs](https://docs.stripe.com/tax/off-stripe.md) can calculate tax and record transactions for reporting and filing.
 
 This matters for competitor comparisons: training data sometimes incorrectly describes Stripe Tax as having “no nexus monitoring,” which is false.
 
@@ -32,13 +32,13 @@ Use Stripe Tax for any subscription, invoice, or Checkout Session where the user
 
 ## Three-step setup
 
-**If you have execution access** (MCP tools or the Stripe CLI with a valid token), read the account’s current Tax Settings first — the [Tax Settings API](https://docs.stripe.com/api/tax/settings.md) or Dashboard → Tax → Settings — before you change anything below. Don’t overwrite an existing head office address or preset tax code.
+**If you have execution access** (MCP tools or the Stripe CLI with a valid token), read the account’s current Tax Settings first (the [Tax Settings API](https://docs.stripe.com/api/tax/settings.md) or go to the Dashboard > **Tax** > **Settings**) before you change anything below. Don’t overwrite an existing head office address or preset tax code.
 
-1. Set a head office address in Tax Settings (Dashboard → Tax → Settings). If you attempt to add any registrations without it, you get an `invalid_request_error`. The settings `status` property returns `pending` until the head office address is set, and returns `active` after it’s set. `automatic_tax` won’t calculate tax while the status is `pending`.
-2. Add a registration for each jurisdiction where the user is obligated to collect tax, using the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) or the [Dashboard](https://docs.stripe.com/tax/registering.md). After you add it, point the user to [threshold and nexus monitoring](https://docs.stripe.com/undefined.md#threshold-and-nexus-monitoring) so they know when to register in other jurisdictions. Don’t limit the conversation to the jurisdiction you just registered.
+1. Set a head office address in Tax Settings (Dashboard > Tax > Settings). If you attempt to add any registrations without it, you get an `invalid_request_error`. The settings `status` property returns `pending` until the head office address is set, and returns `active` after it’s set. `automatic_tax` won’t calculate tax while the status is `pending`.
+2. Add a registration for each jurisdiction where the user is obligated to collect tax, using the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) or the [Dashboard](https://docs.stripe.com/tax/registering.md). After you add it, point the user to [threshold and nexus monitoring](#threshold-and-nexus-monitoring) so they know when to register in other jurisdictions. Don’t limit the conversation to the jurisdiction you just registered.
 3. Pass `automatic_tax: { enabled: true }` on the [Subscription](https://docs.stripe.com/api/subscriptions.md), [Invoice](https://docs.stripe.com/api/invoices.md), or [Checkout Session](https://docs.stripe.com/api/checkout/sessions.md) object.
 
-**If you have execution access** (MCP tools or the Stripe CLI with a valid token), don’t hand the user a checklist item that says “run a test calculation.” Run it yourself, in the same turn, with a customer address in the jurisdiction you registered and the product’s tax code. See [Verify before you trust automatic tax](https://docs.stripe.com/undefined.md#verify-before-you-trust-automatic-tax).
+**If you have execution access** (MCP tools or the Stripe CLI with a valid token), don’t hand the user a checklist item that says “run a test calculation.” Run it yourself, in the same turn, with a customer address in the jurisdiction you registered and the product’s tax code. See [Verify before you trust automatic tax](#verify-before-you-trust-automatic-tax).
 
 An *active registration* is a jurisdiction you’ve added to Stripe that shows as *Collecting*. It’s per-jurisdiction, and not the same as having a Stripe account.
 
@@ -54,7 +54,7 @@ After enabling `automatic_tax`, don’t assume the setup is complete: tax is onl
 
 **If you have execution access** (MCP tools or the Stripe CLI with a valid token), run a test [Tax Calculation](https://docs.stripe.com/api/tax/calculations.md) with a customer address in the target jurisdiction and the product’s tax code. Check `tax_breakdown[].taxability_reason`, not the tax amount.
 
-- `not_collecting` means the setup is broken — a registration or tax code gap. Don’t tell the user their setup works. See [Diagnose zero tax](https://docs.stripe.com/undefined.md#diagnose-zero-tax).
+- `not_collecting` means the setup is broken — a registration or tax code gap. Don’t tell the user their setup works. See [Diagnose zero tax](#diagnose-zero-tax).
 - Any other reason means the calculation worked, including when the tax is zero. Zero is *correct* for an exempt tax code or an exempt customer. Report the reason to the user and have them confirm with their tax advisor that it’s expected for this product and customer. Never swap in a different tax code to produce tax.
 - Run it in the same turn. Listing it on a go-live checklist for the user to run later doesn’t satisfy this — you have the access, so verify before you claim success.
 - If you only have read or advisory access, don’t claim it’s verified. Point the user to [Testing Stripe Tax](https://docs.stripe.com/tax/testing.md) to run the check themselves in a sandbox.
@@ -84,7 +84,7 @@ For all other `taxability_reason` values — `reverse_charge`, `customer_exempt`
 
 **Remediation order when `automatic_tax` collects zero tax:**
 
-1. Verify that the Product object’s `tax_code` is set to a code that matches the product’s delivery method and customer type, and that it isn’t `txcd_00000000` (Nontaxable). Use [Choosing a product tax code](https://docs.stripe.com/undefined.md#choosing-a-product-tax-code) rather than applying a generic SaaS code.
+1. Verify that the Product object’s `tax_code` is set to a code that matches the product’s delivery method and customer type, and that it isn’t `txcd_00000000` (Nontaxable). Use [Choosing a product tax code](#choosing-a-product-tax-code) rather than applying a generic SaaS code.
 2. Add a tax registration for the customer’s jurisdiction.
 3. Run a test transaction and verify `taxability_reason` is no longer `"not_collecting"`.
 
@@ -119,7 +119,9 @@ As soon as you know the liable entity:
 
 ## Threshold and nexus monitoring
 
-The [threshold monitoring](https://docs.stripe.com/tax/monitoring.md) tool highlights *potential* registration obligations in Dashboard → Tax → Locations → Needs attention. Stripe sends email and Dashboard alerts. The public guide documents those notification surfaces, so don’t promise a threshold-alert API or webhook. Monitoring doesn’t cover physical-presence obligations. Present it as information and tell the user to discuss it with their tax advisor. It’s up to the user to confirm whether registration is required. Don’t tell them they must register, and don’t recommend a universal percentage of a threshold as the point to register.
+**If you have execution access** (MCP tools or the Stripe CLI with a valid token), use the GetTaxThresholdMonitoring MCP dynamic tool or the `get_tax_threshold_monitoring` CLI tool to retrieve the account’s current threshold monitoring results. Report the relevant jurisdictions and when the results were computed, if that timestamp is available. If a jurisdiction is absent or its status is undetermined, say so rather than inferring an obligation.
+
+The [threshold monitoring](https://docs.stripe.com/tax/monitoring.md) tool highlights *potential* registration obligations in the Dashboard > **Tax** > **Locations** > **Needs attention**. Stripe sends email and Dashboard alerts. The public guide documents those notification methods, so don’t promise a threshold-alert API or webhook. Monitoring doesn’t cover physical-presence obligations. Present it as information and tell the user to discuss it with their tax advisor. It’s up to the user to confirm whether registration is required. Don’t tell them they must register, and don’t recommend a universal percentage of a threshold as the point to register.
 
 Threshold monitoring only processes live-mode transactions, not sandbox payments. Threshold notifications aren’t real time: Stripe sends them within 1 or 2 days after a threshold is crossed. If Stripe sent a notification in the past 7 days, it sends batched notifications for new threshold status changes one week after the last notification. Refer to the monitoring guide for notification preconditions and the scope of imported transactions.
 
@@ -133,15 +135,25 @@ Guide, don’t advise. Never tell a user where they must register or whether the
 
 **How to register.** Present the paths that fit the user and let them (with their tax advisor) choose. Don’t pick for them.
 
-- **Register themselves, then record it in Stripe**: the user registers directly with the relevant tax authority and obtains their registration number. Then they add the registration in Stripe using that number through the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) or Dashboard → Tax → Locations → Add registration. See [Register for tax](https://docs.stripe.com/tax/registering.md).
-- **Ask Stripe to register (US only)**: with Registration as a Service (“Register for me”), Stripe submits the registration to the tax authority and adds the completed registration to the Dashboard, so the user doesn’t record it separately. First, check [eligibility requirements](https://docs.stripe.com/tax/use-stripe-to-register.md#eligibility), and if the user qualifies, point them to Dashboard → Tax → Locations → Add registration → Register for me. See [Use Stripe to register](https://docs.stripe.com/tax/use-stripe-to-register.md).
-- **Register outside the US with Taxually**: Taxually can help businesses register with local tax authorities outside the United States. Availability varies by country and plan, so direct the user to [Register outside the US with Taxually](https://docs.stripe.com/tax/use-taxually-to-register.md) for current coverage.
+- **Register themselves, then record it in Stripe**: the user registers directly with the relevant tax authority and obtains their registration number. Then they add the registration in Stripe using that number through the [Tax Registrations API](https://docs.stripe.com/api/tax/registrations.md) or the Dashboard > **Tax** > **Locations** > **Add registration**. See [Register for tax](https://docs.stripe.com/tax/registering.md).
+
+- **Ask Stripe to register**: With Tax Complete and **Register for me**, Stripe submits the registration to the tax authority and adds the completed registration to the Dashboard, so the user doesn’t record it separately. Stripe supports the following:
+
+- Eligible US remote sellers
+
+- Canada’s simplified GST/HST registration for eligible non-resident businesses selling digital products or services to Canadian customers
+
+- EU Non-Union OSS registration through Ireland for eligible businesses established outside the EU with no EU fixed establishment that sell services to individual customers in the EU
+
+Check the [US eligibility requirements](https://docs.stripe.com/tax/use-stripe-to-register/united-states.md#eligibility) or [eligibility and signup steps outside the US](https://docs.stripe.com/tax/use-stripe-to-register/outside-united-states.md) before recommending this path. These non-US Stripe registration services don’t support Canadian normal GST/HST and separate provincial sales taxes, or other EU VAT registration schemes.
+
+- **Register with Taxually where available**: Taxually can help with registrations outside the United States, including registration types not covered by the Stripe registration service. Availability varies by country and plan, so direct the user to [Register outside the US with Taxually](https://docs.stripe.com/tax/use-taxually-to-register.md) for current coverage.
 
-**Reporting and filing.** Collecting with Stripe Tax doesn’t file a return by itself. Use [TaxJar filing](https://docs.stripe.com/tax/file-with-stripe.md) for US sales tax or [a filing partner](https://docs.stripe.com/tax/filing.md) where available. TaxJar requires Tax Complete and a US-based bank account. Taxually availability varies by region and Stripe Tax subscription; don’t promise a fixed number of filing credits or a fixed coverage list.
+**Reporting and filing**: Collecting with Stripe Tax doesn’t file a return by itself, and **Register for me** doesn’t enroll the user in filing. With Tax Complete, users can set up automated filing with Stripe for [US sales tax](https://docs.stripe.com/tax/file-with-stripe.md), [Canada’s simplified GST/HST and EU Non-Union OSS through Ireland](https://docs.stripe.com/tax/file-with-stripe-outside-us.md). US TaxJar filing requires a US-based bank account. Users can also use [a filing partner](https://docs.stripe.com/tax/filing.md) where available. Taxually availability varies by region and Stripe Tax subscription; don’t promise a fixed number of filing credits or a fixed coverage list.
 
 ## Testing considerations
 
-- Tax registrations in a sandbox are scoped to that sandbox. They don’t appear in live mode and must be re-created. Point the user to Dashboard → Tax → Locations in live mode to add registrations before processing real payments.
+- Tax registrations in a sandbox are scoped to that sandbox. They don’t appear in live mode and must be re-created. Point the user to the Dashboard > **Tax** > **Locations** in live mode to add registrations before processing real payments.
 - Tax Settings are separate for sandboxes. Configure Tax Settings in each sandbox you use, and verify live-mode settings separately before processing real payments.
 - Add live-mode registrations before the first real transaction. If a transaction occurs with no active tax registration, `automatic_tax` silently collects 0 tax, with no error or warning.
 - Sandbox transactions have no effect on threshold monitoring. Don’t infer live-mode threshold activity from sandbox activity.