vybekiit 0.7.26 → 0.7.28

package/dist/global-skills/neon-postgres/references/vector-search.md

@@ -0,0 +1,137 @@
+# Semantic Vector Search
+
+Use `lakebase_vector` for approximate nearest-neighbor retrieval over embeddings. It retains pgvector's vector types, distance operators, and query syntax; the index access method is `lakebase_ann`.
+
+## Contents
+
+- [Create the extension](#create-the-extension) — enable `lakebase_vector` and its `pgvector` dependency
+- [Prepare embeddings](#prepare-embeddings) — define the vector column and keep embedding dimensions consistent
+- [Build the index](#build-the-index) — match the distance metric, operator class, and query operator
+- [Tune the index](#tune-the-index) — configure index-build options and concurrent index management
+- [Query](#query) — rank by vector distance or filter by a similarity radius
+- [Tune search](#tune-search) — inspect the index and tune recall against latency
+  - [Use prefilter selectively](#use-prefilter-selectively) — apply selective filters before ANN scoring
+
+## Create the Extension
+
+Lakebase Search requires Postgres 16 or later. Enable the extension before creating vector columns or indexes:
+
+```sql
+CREATE EXTENSION IF NOT EXISTS lakebase_vector CASCADE;
+```
+
+`lakebase_vector` installs `pgvector` through `CASCADE`. It relies on a preloaded library that Neon enables by default; if the project customized its preloaded-library list, confirm the library remains enabled.
+
+## Prepare Embeddings
+
+Use any embedding provider whose vector dimensions and distance metric match the schema and index:
+
+```sql
+CREATE TABLE documents (
+  id bigint GENERATED BY DEFAULT AS IDENTITY PRIMARY KEY,
+  title text NOT NULL,
+  body text NOT NULL,
+  embedding vector(1536)
+);
+```
+
+Replace `1536` with the embedding model's dimension. Generate stored-document and query embeddings with the same model and preprocessing. Keep embedding generation outside SQL unless the architecture already provides an in-database embedding function.
+
+## Build the Index
+
+Choose the operator class and query operator as a matched pair:
+
+| Metric | Common use | Operator class | Distance operator |
+| --- | --- | --- | --- |
+| Cosine | Most text embeddings | `vector_cosine_ops` | `<=>` |
+| L2 / Euclidean | Absolute distance matters; vectors do not need normalization | `vector_l2_ops` | `<->` |
+| Inner product | Unit-normalized vectors; matches cosine for unit vectors | `vector_ip_ops` | `<#>` |
+
+```sql
+CREATE INDEX documents_embedding_ann ON documents
+  USING lakebase_ann (embedding vector_cosine_ops);
+```
+
+## Tune the Index
+
+The default index options suit most workloads:
+
+- `build_mode = 'standard'` balances recall and index build time. Use `quality` for better recall when a longer build is acceptable.
+- `lists = 'auto'` chooses the IVF partition layout from the number of indexed vectors. Choose between `auto` and a manual value case by case: test both on the target dataset and use the value that better meets recall and performance targets.
+
+To prioritize recall over index build time:
+
+```sql
+CREATE INDEX documents_embedding_ann_quality ON documents
+  USING lakebase_ann (embedding vector_cosine_ops)
+  WITH (build_mode = 'quality');
+```
+
+To override the automatic partition layout instead:
+
+```sql
+CREATE INDEX documents_embedding_ann_lists ON documents
+  USING lakebase_ann (embedding vector_cosine_ops)
+  WITH (lists = '1024');
+```
+
+For a large table, use `CREATE INDEX CONCURRENTLY` to avoid locking out writes while creating the index. For a frequently changing table, periodically use `REINDEX INDEX CONCURRENTLY` to rebuild the index with minimal write locking.
+
+## Query
+
+Generate the query embedding with the same model and preprocessing used for stored documents, then bind it as a parameter:
+
+```sql
+SELECT id, title, embedding <=> $1::vector AS distance
+FROM documents
+ORDER BY distance
+LIMIT $2;
+```
+
+Distance sorts ascending: a smaller value is a closer match. Keep the query operator consistent with the index operator class.
+
+To filter by a similarity radius, use the matching boolean range operator in `WHERE` and the distance operator in `ORDER BY`:
+
+```sql
+SELECT id, title
+FROM documents
+WHERE embedding <<=>> sphere($1::vector, 0.5)
+ORDER BY embedding <=> $1::vector
+LIMIT $2;
+```
+
+The cosine range operator `<<=>>` returns a boolean; do not use it as the ranking expression.
+
+## Tune Search
+
+Inspect the index before overriding defaults:
+
+```sql
+SELECT lakebase_ann_index_info('documents_embedding_ann');
+```
+
+This reports `lists`, `default_probes`, and `default_epsilon`. Small datasets use exact flat search before IVF lists are built. In that state, `lists` and `default_probes` are empty. Leave `lakebase_ann.probes` set to its default of `'auto'`; `lakebase_ann.epsilon` still controls full-precision reranking during flat search.
+
+For an IVF index, `lakebase_ann.probes` controls how many partitions are searched at each level. Higher values generally improve recall at the cost of speed. Its default is `'auto'`. When `lists` is not empty, the shape of `probes` must match the shape of `lists`: use one value for a one-level index or two comma-separated values for a two-level index. At each level, the `probes` value must be no larger than the corresponding `lists` value. A mismatched or out-of-range value causes an error.
+
+`lakebase_ann.epsilon` controls how many candidates are reranked using full-precision distances. Higher values rerank more candidates and take longer. Its default is `'auto'`, which works well for most workloads.
+
+### Use Prefilter Selectively
+
+By default, PostgreSQL applies non-vector filters after the ANN index returns candidate rows. Enable prefilter when a filter is cheap to evaluate and removes most rows. Leave it off for loose or expensive filters.
+
+```sql
+BEGIN;
+SET LOCAL lakebase_ann.prefilter = on;
+
+SELECT id, title
+FROM documents
+WHERE id % 100 = 0
+ORDER BY embedding <=> $1::vector
+LIMIT $2;
+COMMIT;
+```
+
+Start with `probes` and `epsilon` set to `'auto'`. Benchmark manual probe values against representative query embeddings and choose the smallest values that satisfy recall and tail-latency targets. Keep session settings and the query in the same transaction when using a connection pool or stateless driver.
+
+Source: [`lakebase_vector` documentation](https://neon.com/docs/extensions/lakebase-vector).

package/dist/global-skills/neon-postgres-branches/SKILL.md

@@ -19,7 +19,7 @@ metadata:
 If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with:
 
 ```bash
-npx skills add neondatabase/agent-skills --skill neon
+neon skills -s neon -y
 ```
 
 # Lakebase Postgres Branching
@@ -127,7 +127,7 @@ Schema-only branching is in Beta. If users report unexpected behavior, errors, o
 1. Ask them to share feedback in the Neon Console:
    - https://console.neon.tech/app/projects?modal=feedback
 2. Recommend opening a support conversation in the Neon Discord:
-   - https://discord.gg/92vNTzKDGp
+   - https://neon.com/discord
 
 ## Reset from Parent
 
@@ -282,7 +282,7 @@ Common CI/CD use cases for Neon branches:
    - `neon branches create --name compliance-dev --parent main --schema-only --project-id <your-project-id> --expires-at 2026-12-15T18:02:16Z`
 5. Mention Beta support path:
    - https://console.neon.tech/app/projects?modal=feedback
-   - https://discord.gg/92vNTzKDGp
+   - https://neon.com/discord
 
 ## Further Reading
 

package/dist/global-skills/neon-postgres-egress-optimizer/SKILL.md

@@ -19,7 +19,7 @@ metadata:
 If the `neon` skill is not installed, fetch it from https://neon.com/docs/ai/skills/neon/SKILL.md or install it with:
 
 ```bash
-npx skills add neondatabase/agent-skills --skill neon
+neon skills -s neon -y
 ```
 
 # Postgres Egress Optimizer

package/dist/global-skills/onboarding/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: onboarding
-description: "take the builder from \"I just bought this\" to **their app running and visible in front of. Use when the builder says something like: set up my app; let's start; get me going; just bought."
+description: "take the vibe coder from \"I just bought this\" to **their app running and visible in front of. Use when the vibe coder says something like: set up my app; let's start; get me going; just bought."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---
@@ -9,7 +9,7 @@ metadata:
 
 # Skill: onboarding
 
-**Goal:** take the builder from "I just bought this" to **their app running and visible in front of
+**Goal:** take the vibe coder from "I just bought this" to **their app running and visible in front of
 them** in this one session. This is the keystone — the moment that proves the purchase was worth it.
 
 **Contract:** one action at a time · verify-before-advance · plain language (`language.md`) ·
@@ -18,17 +18,18 @@ translate every error · celebrate. Decide all technical choices yourself.
 ## Steps
 
 <!-- vybekiit:page-recipe-install -->
-0. **Install the end-user onboarding recipe when the builder wants a first-run wizard (catalog SSOT — Option C).**
+0. **Install the end-user onboarding recipe when the vibe coder wants a first-run wizard (catalog SSOT — Option C).**
    Copy `apps/componentLibrary/src/pageRecipes/OnboardingPage.tsx` export `OnboardingPage` into the buyer app at route `/onboarding`.
    Recipe id: `onboarding`. Presets: none.
    Keep every `TODO:` in the recipe and wire each one after the route renders.
-   Skip this step if the builder only needs *their* kit setup (steps 1–5 below) and not a product wizard for their users.
+   Skip this step if the vibe coder only needs *their* kit setup (steps 1–5 below) and not a product wizard for their users.
    Also reference `packages/agentKit` `getPageRecipeInstall('onboarding')` / page-recipe-manifest.json.
    **Verify:** if installed, `/onboarding` builds with practice UI.
 
 1. **Welcome + ask the one thing that matters.**
-   Greet warmly. Ask: *"In one sentence, what do you want to build?"* Use their answer to tailor the
-   starter page later — don't turn it into a technical interview.
+   Greet warmly. If the vibe coder already described their app, use that description. Otherwise ask:
+   *"In one sentence, what do you want to build?"* Use their answer to tailor the starter page later.
+   Keep the conversation about their idea.
 
 1b. **One-time planning offer** (skip if `.vybekiit/state/planning-intro-seen` exists).
    Ask: *"Before we start building — want to **think it through together** first? I'll ask one question
@@ -40,17 +41,18 @@ translate every error · celebrate. Decide all technical choices yourself.
 
 2. **Set up the tools, then get the preview running.**
    First run `vybekiit doctor` — it installs the tools the app will need (for the database and for
-   putting the app online) so the builder never configures anything. It may say a tool "isn't signed
+   putting the app online) so the vibe coder never configures anything. It may say a tool "isn't signed
    in yet" — that's fine for now; sign-in happens later, only when a step needs it (one browser click
-   each). Then install the project's building blocks. Before starting the app, check whether
-   `http://localhost:3000` already responds and reuse that running preview when it does. Otherwise,
-   start exactly one preview with the agent's background-task support and keep its task handle.
+   each). Then install the project's building blocks. Check the URL printed by setup and the
+   project's running processes. Reuse a preview only after confirming it serves this app.
+   If none is running, choose an available port, start exactly one preview with the agent's
+   background-task support, and keep its task handle and URL.
    If a running preview is unhealthy, inspect and restart that same process instead of starting a
    second copy. Do this yourself, in plain words.
    After dependencies install, run **quality smoke** yourself: `pnpm verify` (format, lint, typecheck,
    tests). Confirm `.cursorignore` hides `.env` (doctor checks this). Optionally install UI walkthrough
    browsers: `pnpm exec playwright install chromium` (agent-only — see `playwright-vybekiit.md`).
-   Fix anything red before showing the preview. The builder hears: *"Everything checks out."*
+   Fix anything red before showing the preview. The vibe coder hears: *"Everything checks out."*
    **Verify:** the dev server is up with no errors. If it fails → run `doctor`.
 
    > (Agent-only) **Database MCP tier:** Supabase, Neon, and Firebase use login-once MCP configs
@@ -61,7 +63,7 @@ translate every error · celebrate. Decide all technical choices yourself.
    > `setup-payments` runs — same merge guide.
 
 3. **Show them their app.**
-   Give them the one link to open (`http://localhost:3000`) and tell them what they'll see.
+   Give them the verified preview link from this run and tell them what they'll see.
    **Verify:** ask them to confirm they can see the page. Don't continue until they say yes.
    🎉 *Celebrate* — their app is alive.
    Mention Report mode once: *"If something looks wrong, press Option+Shift+R (Alt+Shift+R on
@@ -85,7 +87,7 @@ Stop the steps and run `doctor`. Never show a raw error — say what happened an
 
 ## Definition of done
 
-The builder has seen their own app running and personalized, and knows the next thing they can ask
+The vibe coder has seen their own app running and personalized, and knows the next thing they can ask
 for. Save progress for them (don't make them think about it).
 
 ## After completing this skill
@@ -102,4 +104,4 @@ Update checklist.md Progress (mark done, note next). If checklist.md doesn't exi
 
 Append one entry to `checklist.md` Decision log using `formatChecklistEntry({ from, to, because })`.
 
-If MCP or first debug fails once, run `vybekiit doc-fallback <tech-id>` and tell the builder only: *"I'm double-checking the official setup guide for this — hang tight, I'll have the next step in a moment."*
+If MCP or first debug fails once, run `vybekiit doc-fallback <tech-id>` and tell the vibe coder only: *"I'm double-checking the official setup guide for this — hang tight, I'll have the next step in a moment."*

package/dist/global-skills/plan-my-idea/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: plan-my-idea
-description: "help the builder figure out exactly what they want **before** you build — so the first. Use when the builder says something like: help me plan; figure out my idea; think it through; marketplace; like airbnb."
+description: "help the builder figure out exactly what they want **before** you build — so the first. Use when the vibe coder says something like: help me plan; figure out my idea; think it through; marketplace; like airbnb."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

package/dist/global-skills/publish-app/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: publish-app
-description: "the builder's app is **in the App Store and Google Play** for anyone to download. This is. Use when the builder says something like: put it online; publish; make it live; ship it; deploy; publish app."
+description: "the builder's app is **in the App Store and Google Play** for anyone to download. This is. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; publish app."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

package/dist/global-skills/publish-extension/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: publish-extension
-description: "the builder's extension is **listed in the Chrome Web Store** for anyone to install. Use when the builder says something like: put it online; publish; make it live; ship it; deploy; chrome store."
+description: "the builder's extension is **listed in the Chrome Web Store** for anyone to install. Use when the vibe coder says something like: put it online; publish; make it live; ship it; deploy; chrome store."
 metadata:
   vybekiit-generated: buyer-skill-stub
 ---

package/dist/global-skills/resend/SKILL.md

@@ -1,10 +1,10 @@
 ---
 name: resend
-description: 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.
+description: 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, checking account usage and quotas, 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.
 license: MIT
 metadata:
     author: resend
-    version: "3.6.0"
+    version: "3.12.0"
     homepage: https://resend.com/agent-skills
     source: https://github.com/resend/resend-skills
     openclaw:
@@ -44,6 +44,7 @@ references:
     - topics.md
     - automations.md
     - events.md
+    - usage.md
     - installation.md
     - fetch-all-templates.mjs
 ---
@@ -170,6 +171,7 @@ export async function POST(req: Request) {
 | **Manage topics** (subscriptions) | [topics.md](references/topics.md) — opt-in/out preferences, broadcast filtering |
 | **Create automations** (event-driven workflows) | [automations.md](references/automations.md) — steps, connections, runs, conditions |
 | **Define and send events** (automation triggers) | [events.md](references/events.md) — schemas, payloads, contact association |
+| **Check account usage and quotas** | [usage.md](references/usage.md) — emails, contacts, segments, broadcasts, AI credits, automation runs, domains, rate limit |
 | **Install SDK** (8+ languages) | [installation.md](references/installation.md) |
 | **Set up an AI agent inbox** | Install the `agent-email-inbox` skill — covers security levels for untrusted input |
 

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

@@ -11,6 +11,7 @@ Send emails to audience segments. Broadcasts follow a two-step lifecycle: **crea
 | List | `resend.broadcasts.list(params)` | `resend.Broadcasts.list(params)` |
 | Send | `resend.broadcasts.send(id, params?)` | `resend.Broadcasts.send(params)` |
 | Cancel | `resend.broadcasts.cancel(id)` | `resend.Broadcasts.cancel(id)` |
+| Duplicate | `resend.broadcasts.duplicate(id)` | `resend.Broadcasts.duplicate(id)` |
 | Update | `resend.broadcasts.update(id, params)` | `resend.Broadcasts.update(params)` |
 | Delete | `resend.broadcasts.remove(id)` | `resend.Broadcasts.remove(id)` |
 | Clicked Links | `resend.broadcasts.clickedLinks(id, params?)` | `resend.Broadcasts.clicked_links(id, params?)` |
@@ -69,7 +70,7 @@ const { data, error } = await resend.broadcasts.create({
 });
 ```
 
-## Get, List, Update, Cancel, Delete
+## Get, List, Update, Cancel, Duplicate, Delete
 
 ```typescript
 // Get
@@ -87,6 +88,10 @@ const { data, error } = await resend.broadcasts.update('bc_abc123', {
 // reverts a scheduled one to draft. Does not remove the broadcast.
 const { data, error } = await resend.broadcasts.cancel('bc_abc123');
 
+// Duplicate — creates a new draft named "<name> (copy)" with the same content.
+// Works on any broadcast, including sent ones. Returns the new broadcast's id.
+const { data, error } = await resend.broadcasts.duplicate('bc_abc123');
+
 // Delete — draft or scheduled only (deleting a scheduled broadcast also
 // cancels its delivery). Sent broadcasts cannot be deleted.
 const { data, error } = await resend.broadcasts.remove('bc_abc123');

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

@@ -167,7 +167,7 @@ const { data: attachments } = await resend.emails.receiving.attachments.list({
   emailId: event.data.email_id,
 });
 
-for (const attachment of attachments) {
+for (const attachment of attachments.data) {
   console.log(attachment.filename);
   console.log(attachment.download_url);  // signed URL, see expires_at
   console.log(attachment.expires_at);
@@ -179,7 +179,7 @@ for (const attachment of attachments) {
 ```typescript
 const { data: attachment } = await resend.emails.receiving.attachments.get({
   emailId: event.data.email_id,
-  attachmentId: 'att_abc123',
+  id: 'att_abc123',
 });
 
 console.log(attachment.download_url); // signed URL
@@ -213,19 +213,33 @@ export async function POST(req: Request) {
 
   if (event.type === 'email.received') {
     // 1. Get email content
-    const { data: email } = await resend.emails.receiving.get(
+    const { data: email, error: emailError } = await resend.emails.receiving.get(
       event.data.email_id
     );
 
+    if (emailError) {
+      console.error(emailError);
+      return new Response('Failed to fetch email', { status: 500 });
+    }
+
     // 2. Get attachments (if any)
-    const { data: attachmentList } = await resend.emails.receiving.attachments.list({
-      emailId: event.data.email_id,
-    });
+    const { data: attachmentList, error: attachmentsError } =
+      await resend.emails.receiving.attachments.list({
+        emailId: event.data.email_id,
+      });
+
+    if (attachmentsError) {
+      console.error(attachmentsError);
+      return new Response('Failed to list attachments', { status: 500 });
+    }
 
     // 3. Download and encode attachments
     const attachments = await Promise.all(
-      attachmentList.map(async (att) => {
+      attachmentList.data.map(async (att) => {
         const res = await fetch(att.download_url);
+        if (!res.ok) {
+          throw new Error(`Failed to download ${att.filename}`);
+        }
         const buffer = Buffer.from(await res.arrayBuffer());
         return {
           filename: att.filename,
@@ -235,14 +249,19 @@ export async function POST(req: Request) {
     );
 
     // 4. Forward the email (single send — batch doesn't support attachments)
-    await resend.emails.send({
+    const { error: sendError } = await resend.emails.send({
       from: 'Support System <system@acme.com>',
       to: ['team@acme.com'],
       subject: `Fwd: ${email.subject}`,
-      html: email.html,
-      text: email.text,
+      html: email.html ?? undefined,
+      text: email.text ?? '',
       attachments,
     });
+
+    if (sendError) {
+      console.error(sendError);
+      return new Response('Failed to forward email', { status: 500 });
+    }
   }
 
   return new Response('OK', { status: 200 });

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

@@ -103,16 +103,21 @@ List and download attachments for sent emails. Returns metadata and a signed dow
 | Operation | Node.js | Python |
 |-----------|---------|--------|
 | List | `resend.emails.attachments.list({ emailId })` | `resend.Emails.Attachments.list(email_id)` |
-| Get | `resend.emails.attachments.get({ emailId, attachmentId })` | `resend.Emails.Attachments.get(email_id, attachment_id)` |
+| Get | `resend.emails.attachments.get({ emailId, id })` | `resend.Emails.Attachments.get(email_id, attachment_id)` |
 
 ### Examples
 
 ```typescript
 // List all attachments for a sent email
-const { data: attachments } = await resend.emails.attachments.list({
+const { data: attachments, error } = await resend.emails.attachments.list({
   emailId: 'email_abc123',
 });
 
+if (error) {
+  console.error(error);
+  return;
+}
+
 for (const att of attachments.data) {
   console.log(att.filename);      // 'invoice.pdf'
   console.log(att.content_type);   // 'application/pdf'
@@ -121,11 +126,16 @@ for (const att of attachments.data) {
 }
 
 // Get a single attachment
-const { data: attachment } = await resend.emails.attachments.get({
+const { data: attachment, error: getError } = await resend.emails.attachments.get({
   emailId: 'email_abc123',
-  attachmentId: 'att_def456',
+  id: 'att_def456',
 });
 
+if (getError) {
+  console.error(getError);
+  return;
+}
+
 // Download the content
 const response = await fetch(attachment.download_url);
 const buffer = await response.arrayBuffer();

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

@@ -20,8 +20,8 @@ Fine-grained subscription preferences — contacts opt in or out per topic. Topi
 |-----------|--------|
 | Create | `resend.Topics.create(params)` |
 | Get | `resend.Topics.get(id)` |
-| List | `resend.Topics.list()` |
-| Update | `resend.Topics.update(params)` |
+| List | `resend.Topics.list(params?)` — `limit`, `after`, `before` |
+| Update | `resend.Topics.update(id, params)` |
 | Delete | `resend.Topics.remove(id)` |
 
 ## Create Topic
@@ -31,7 +31,6 @@ const { data, error } = await resend.topics.create({
   name: 'Product Updates',
   defaultSubscription: 'opt_in',  // REQUIRED: "opt_in" or "opt_out"
   description: 'New features and releases',
-  visibility: 'public',  // "public" or "private" (default: "private")
 });
 
 if (error) {
@@ -50,8 +49,13 @@ console.log(data.id); // topic_xxxxxxxx
 const { data, error } = await resend.topics.update({
   id: 'topic_xxx',
   name: 'Product News',
-  visibility: 'public',
+  description: 'News about our products',
 });
+
+if (error) {
+  console.error(error);
+  return;
+}
 ```
 
 ## Managing Contact Subscriptions
@@ -90,7 +94,7 @@ await resend.broadcasts.create({
 | Name max length | 50 characters |
 | Description max length | 200 characters |
 | `defaultSubscription` | `"opt_in"` or `"opt_out"` — immutable after create |
-| `visibility` | `"public"` (shown on preference page) or `"private"` (default) |
+| `visibility` | `"public"` (shown on the unsubscribe page) or `"private"` (default) |
 
 ## Common Mistakes
 
@@ -100,5 +104,4 @@ await resend.broadcasts.create({
 | Trying to change `defaultSubscription` | Immutable after creation — delete and recreate with new value |
 | Calling `.delete()` | SDK method is `.remove()` |
 | `visibility: "hidden"` | Not a valid value — use `"private"` |
-| Expecting `list()` to accept pagination | `topics.list()` takes no params — returns all topics |
 | Broadcast without `topicId` | Goes to all contacts in segment regardless of topic preferences |

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

@@ -0,0 +1,117 @@
+# Usage
+
+Account-level usage and quotas. A single snapshot endpoint — no ID, no pagination, no filters. Use it to check how close an account is to its plan limits for emails, contacts, segments, broadcasts, AI credits, automation runs, and domains, plus the account's API rate limit.
+
+## SDK Methods
+
+| Operation | Node.js | Python |
+|-----------|---------|--------|
+| Get | `resend.usage.get()` | `resend.Usage.get()` |
+
+Method naming per SDK: Ruby `Resend::Usage.get`, Go `client.Usage.Get()`, PHP `$resend->usage->get()`, Java `resend.usage().get()`, .NET `resend.UsageAsync()`, Rust `resend.usage.get().await`.
+
+## Get Usage
+
+`GET /usage`
+
+Takes no parameters.
+
+### Node.js
+
+```typescript
+import { Resend } from 'resend';
+const resend = new Resend(process.env.RESEND_API_KEY);
+
+const { data, error } = await resend.usage.get();
+
+if (error) {
+  console.error(error);
+  return;
+}
+
+console.log(`${data.emails.daily.used} emails today`);
+console.log(`${data.contacts.used} / ${data.contacts.limit} contacts`);
+```
+
+### Python
+
+```python
+import resend
+import os
+
+resend.api_key = os.environ["RESEND_API_KEY"]
+
+usage = resend.Usage.get()
+
+print(f'{usage["emails"]["daily"]["used"]} emails today')
+print(f'{usage["contacts"]["used"]} / {usage["contacts"]["limit"]} contacts')
+```
+
+### cURL
+
+```bash
+curl -s "https://api.resend.com/usage" \
+  -H "Authorization: Bearer $RESEND_API_KEY" \
+  -H "User-Agent: curl"
+```
+
+### Response
+
+```json
+{
+  "object": "usage",
+  "emails": {
+    "daily": { "used": 258, "limit": null, "sent": 57, "received": 201, "resets_at": "2026-07-17T00:00:00.000Z" },
+    "monthly": { "used": 5442, "limit": 10000, "sent": 1000, "received": 4442, "resets_at": "2026-08-01T00:00:00.000Z" }
+  },
+  "contacts": { "used": 85000, "limit": 150000 },
+  "segments": { "used": 2, "limit": 3 },
+  "broadcasts": { "used": 100, "limit": null },
+  "ai_credits": { "used": 0, "limit": 500, "next_increase_at": "2026-07-18T09:00:00.000Z" },
+  "automation_runs": { "used": 0, "limit": 1000, "resets_at": "2026-08-01T00:00:00.000Z" },
+  "domains": { "used": 1, "limit": 1000 },
+  "rate_limit": { "limit": 10, "duration": "1000ms" }
+}
+```
+
+## Response Fields
+
+| Field | Type | Nullable | Description |
+|-------|------|----------|--------------|
+| `object` | string | No | Always `"usage"` |
+| `emails.daily.used` | number | No | Emails sent + received in the current day (`sent` + `received`) |
+| `emails.daily.limit` | number \| null | Yes | Plan's daily email cap. `null` when the plan has no daily cap (only a monthly one) |
+| `emails.daily.sent` | number | No | Emails sent today |
+| `emails.daily.received` | number | No | Emails received (inbound) today |
+| `emails.daily.resets_at` | timestamp | No | When the daily counters next reset |
+| `emails.monthly.used` | number | No | Emails sent + received in the current billing month |
+| `emails.monthly.limit` | number | No | Plan's monthly email cap — always a number |
+| `emails.monthly.sent` | number | No | Emails sent this month |
+| `emails.monthly.received` | number | No | Emails received (inbound) this month |
+| `emails.monthly.resets_at` | timestamp | No | When the monthly counters next reset |
+| `contacts.used` | number | No | Total contacts on the account |
+| `contacts.limit` | number | No | Plan's contact cap — always a number |
+| `segments.used` | number | No | Segments created |
+| `segments.limit` | number \| null | Yes | Plan's segment cap. `null` when the plan doesn't cap segments |
+| `broadcasts.used` | number | No | Broadcasts sent |
+| `broadcasts.limit` | null | Always null | Broadcasts have no plan cap — this field is always `null` |
+| `ai_credits.used` | number | No | AI credits consumed in the current period |
+| `ai_credits.limit` | number \| null | Yes | Plan's AI credit cap. `null` when the plan grants unlimited AI credits |
+| `ai_credits.next_increase_at` | timestamp \| null | Yes | When credits are next scheduled to increase. `null` if no increase is scheduled |
+| `automation_runs.used` | number | No | Automation runs in the current period |
+| `automation_runs.limit` | number | No | Plan's automation run cap — always a number |
+| `automation_runs.resets_at` | timestamp | No | When the automation run counter next resets |
+| `domains.used` | number | No | Domains added to the account |
+| `domains.limit` | number \| null | Yes | Plan's domain cap. `null` when the plan doesn't cap domains |
+| `rate_limit.limit` | number | No | Max API requests allowed per `duration` window |
+| `rate_limit.duration` | string | No | Length of the rate-limit window, e.g. `"1000ms"` |
+
+## Common Mistakes
+
+| Mistake | Fix |
+|---------|-----|
+| Assuming every `limit` field can be `null` | Only `emails.daily.limit`, `segments.limit`, `ai_credits.limit`, and `domains.limit` can be `null`. `emails.monthly.limit`, `contacts.limit`, and `automation_runs.limit` are always numbers, and `broadcasts.limit` is always `null` |
+| Reading `emails.daily.used` as "sent only" | `used` is `sent` + `received` combined — check `sent`/`received` separately for a breakdown |
+| Expecting `ai_credits.next_increase_at` to always be set | It's `null` when no future increase is scheduled |
+| Calling `.list()` or passing an ID | Usage is a single account-level snapshot — no list, get-by-id, create, update, or delete operations |
+| Treating `rate_limit` as per-endpoint | It reflects the account's default API rate limit, not a per-endpoint override |