vybekiit 0.7.16 → 0.7.18

package/dist/global-skills/neon-ai-gateway/SKILL.md

@@ -4,7 +4,7 @@ description: >-
   One API and one credential for frontier and open-source LLMs, built into your
   Neon branch and powered by Databricks. Use when a user wants to call an LLM,
   add AI/chat/an agent to their app, route between model providers (OpenAI,
-  Anthropic, Google/Gemini, Meta, Alibaba, DeepSeek), or avoid juggling
+  Anthropic, Google/Gemini, Meta, Alibaba, and more), or avoid juggling
   separate provider API keys and accounts — especially when they already use
   Neon and want AI requests to branch with their project. Works with the OpenAI
   SDK, Anthropic SDK, google-genai, the Vercel AI SDK, and Mastra by changing
@@ -29,7 +29,7 @@ npx skills add neondatabase/agent-skills --skill neon
 
 This is a public beta feature and only available in `us-east-2`.
 
-The Neon AI Gateway is the LLM inference layer built into your Neon branch: one API and one Neon credential give you access to frontier and open-source models from Anthropic, OpenAI, Google, Meta, Alibaba, DeepSeek, and Databricks — powered by Databricks. Your existing OpenAI/Anthropic/Gemini SDK works by changing only the base URL.
+The Neon AI Gateway is the LLM inference layer built into your Neon branch: one API and one Neon credential give you access to frontier and open-source models from many providers (Anthropic, OpenAI, Google, Meta, and more), all hosted and powered by Databricks. The catalog shifts over time, so treat `/v1/models` and the [models.dev Neon page](https://models.dev/providers/neon) as the source of truth rather than a fixed provider list. Your existing OpenAI/Anthropic/Gemini SDK works by changing only the base URL.
 
 Use this skill to help the user send model calls through the gateway, wire it into the AI SDK or Mastra, and switch providers without rewiring code. Deliver a working inference request, a configured agent, or a precise answer from the official Neon docs.
 
@@ -37,7 +37,7 @@ Use this skill to help the user send model calls through the gateway, wire it in
 
 Reach for the AI Gateway whenever an app or agent needs to call an LLM and the user would rather not manage model providers themselves:
 
-- **One credential instead of many provider accounts.** A single Neon credential reaches the entire model catalog across seven providers. No separate OpenAI / Anthropic / Google billing, keys, or signups to provision and rotate.
+- **One credential instead of many provider accounts.** A single Neon credential reaches the entire model catalog across every provider Databricks hosts. No separate OpenAI / Anthropic / Google billing, keys, or signups to provision and rotate.
 - **Switch models without rewiring.** The unified endpoint is OpenAI-compatible and works with every model in the catalog — change one `model` field to move between Claude, GPT, and Gemini. Standard SDKs (OpenAI, Anthropic, google-genai) work with just a base-URL change.
 - **AI follows your branches.** Each branch has its own gateway endpoint, scoped with the same lineage as your database. AI requests from a preview/feature branch are isolated to that branch — the same isolation your data already gets — which makes preview, CI, and agent environments self-contained.
 - **No extra infrastructure, and it's already next to your data.** The gateway lives inside your Neon project (and is injected into Neon Functions automatically), runs on the same Databricks infrastructure that serves trillions of tokens a month, and supports streaming (SSE) out of the box.
@@ -46,7 +46,7 @@ If the user already has a deep, single-provider integration and no interest in N
 
 ## What It Does
 
-- **One API for all models** — Frontier and open-source models behind a single endpoint, addressed by their catalog ID (e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-2-5-flash`).
+- **One API for all models** — Frontier and open-source models behind a single endpoint, addressed by their catalog ID (e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-3-flash`).
 - **Standard SDKs, one URL change** — OpenAI SDK and AI SDK (OpenAI-compatible MLflow/Responses routes), Anthropic SDK (native Messages), google-genai (native Gemini).
 - **Branch-scoped** — Each branch gets its own gateway host; the Neon credential authorizes requests for that branch and its descendants.
 - **Streaming** — Server-sent events work on all endpoints with no extra configuration.
@@ -55,7 +55,7 @@ If the user already has a deep, single-provider integration and no interest in N
 
 Check these preconditions before setting anything up:
 
-The AI Gateway is a public beta feature available only on new projects in the `us-east-2` region; it can't be enabled on existing projects. Foundation model access requires a paid Neon plan. Confirm the user's project is a new project in `us-east-2`.
+The AI Gateway is a public beta feature available in the `us-east-2` region. Foundation model access requires a paid Neon plan. Confirm the user's project is in `us-east-2`.
 
 ### Enabling the gateway: plan and model-catalog gating
 
@@ -112,10 +112,10 @@ When `preview.aiGateway` is enabled, Neon injects the gateway credentials as **N
 
 - `/v1` — unified, OpenAI **Chat Completions**-compatible; recommended default, works with every provider (`/v1/chat/completions`).
 - `/openai/v1` — OpenAI **Responses** API (required for `gpt-5-…-codex` variants and `gpt-5-5-pro`); the `@ai-sdk/openai` provider uses the Responses API by default (`/openai/v1/responses`).
-- `/anthropic/v1` — native Anthropic Messages (extended thinking, prompt caching); mirrors the real Anthropic API path (`/anthropic/v1/messages`).
-- `/gemini/v1beta/...` — native Gemini `generateContent` (`/gemini/v1beta/models/<model>:generateContent`).
+- `/anthropic` — native Anthropic Messages (extended thinking, prompt caching). Give the Anthropic SDK this as its base URL and it appends `/v1/messages` itself, so the full request path is `/anthropic/v1/messages`.
+- `/gemini` — native Gemini `generateContent`. Give google-genai this as its base URL and it appends `/v1beta/models/<model>:generateContent` itself, so the full request path is `/gemini/v1beta/models/<model>:generateContent`.
 
-So `${NEON_AI_GATEWAY_BASE_URL}/v1` is the chat-completions endpoint, `${NEON_AI_GATEWAY_BASE_URL}/openai/v1` the OpenAI Responses endpoint, and so on.
+So `${NEON_AI_GATEWAY_BASE_URL}/v1` is the chat-completions endpoint and `${NEON_AI_GATEWAY_BASE_URL}/openai/v1` the OpenAI Responses endpoint (both appended by you); for the native Anthropic and Gemini dialects you hand the SDK the shorter `/anthropic` or `/gemini` base and it appends the rest. See [Use with Plain SDKs](#use-with-plain-sdks-lower-level) below.
 
 For typed, validated access to the injected credentials, pass the same `neon.ts` config object to `parseEnv` from `@neon/env` — it returns an `env.aiGateway` namespace (`apiKey`, `baseUrl`) derived from your config.
 
@@ -130,7 +130,7 @@ import { neon } from "@neon/ai-sdk-provider";
 import { streamText } from "ai";
 
 const result = streamText({
-  model: neon("gpt-5-mini"), // or claude-sonnet-4-6, gemini-2-5-flash, ...
+  model: neon("gpt-5-mini"), // or claude-sonnet-4-6, gemini-3-flash, ...
   messages,
   tools: {
     image_generation: neon.tools.imageGeneration({
@@ -149,7 +149,7 @@ import { neon } from "@neon/ai-sdk-provider";
 import { generateText } from "ai";
 
 const { text } = await generateText({
-  model: neon("claude-haiku-4-5"), // or gpt-5-3-codex, gemini-2-5-flash, ...
+  model: neon("claude-haiku-4-5"), // or gpt-5-3-codex, gemini-3-flash, ...
   prompt: "Summarize Postgres for me.",
 });
 ```
@@ -213,7 +213,7 @@ const client = new OpenAI({
 });
 
 const res = await client.responses.create({
-  model: "gpt-5-mini", // swap to claude-sonnet-4-6, gemini-2-5-flash, ...
+  model: "gpt-5-mini", // swap to claude-sonnet-4-6, gemini-3-flash, ...
   input: "What is Neon?",
 });
 ```
@@ -236,7 +236,7 @@ The Anthropic SDK and google-genai work the same way for native provider feature
 
 ## Model Identifiers
 
-Use a model's catalog ID directly in the `model` field — e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-2-5-flash`. No provider prefix is needed. To look up the exact identifiers the gateway serves, which underlying model each maps to, and their context windows, pricing, and capabilities, use any of:
+Use a model's catalog ID directly in the `model` field — e.g. `claude-sonnet-4-6`, `gpt-5-mini`, `gemini-3-flash`. No provider prefix is needed. To look up the exact identifiers the gateway serves, which underlying model each maps to, and their context windows, pricing, and capabilities, use any of:
 
 - **models.dev Neon provider page: https://models.dev/providers/neon** — the canonical, always-current list of the Neon provider's model IDs and their underlying models. The machine-readable catalog is at https://models.dev/api.json (the `neon` key).
 - **Models doc:** see Further Reading.
@@ -272,7 +272,7 @@ Any Neon credential (`nt_live_...`) valid for the branch works as the bearer tok
       "canonical_slug": "claude-sonnet-4-6",
       "name": "Claude Sonnet 4.6",            // human-readable display name
       "object": "model",
-      "owned_by": "anthropic",                // anthropic | openai | google | meta | alibaba | databricks
+      "owned_by": "anthropic",                // provider slug, e.g. anthropic | openai | google | meta | alibaba | databricks | ... (non-exhaustive; read live)
       "created": 0,
       "enabled": true,
       "context_length": null,

package/dist/global-skills/neon-functions/SKILL.md

@@ -55,7 +55,7 @@ If the workload is a pure static site, a cron/background job that needs its own
 
 ## Availability
 
-Check this precondition before setting anything up: Neon Functions is a public beta feature available only on new projects in the `us-east-2` region. Confirm the user's Neon project is a new project in `us-east-2`; it can't be enabled on existing projects. Functions usage isn't billed during the public beta.
+Check this precondition before setting anything up: Neon Functions is a public beta feature available in the `us-east-2` region. Confirm the user's Neon project is in `us-east-2`. Functions usage isn't billed during the public beta.
 
 ## Architecture: Where Functions Fit
 
@@ -135,7 +135,7 @@ neon dev      # serves every function in neon.ts with hot reload; injects DATABA
 neon deploy   # bundles with esbuild, uploads, and applies neon.ts to the linked branch
 ```
 
-To deploy a single function without `neon.ts`: `neon functions deploy <slug> --src src/index.ts` (`--src` takes either the entry file or a directory containing `index.ts`, `index.mjs`, or `index.js`). Retrieve the public URL with `neon functions get <slug>` (the `invocation_url` field, of the form `https://<branch_id>-<slug>.compute.c-1.us-east-2.aws.neon.tech`). Manage with `neon functions list|get|delete`.
+To deploy a single function without `neon.ts`: `neon functions deploy <slug> --src src/index.ts` (`--src` takes either the entry file or a directory containing `index.ts`, `index.mjs`, or `index.js`). Retrieve the public URL with `neon functions get <slug>` (the `invocation_url` field, of the form `https://<branch_id>-<slug>.compute.<cell>.us-east-2.aws.neon.tech`). Manage with `neon functions list|get|delete`.
 
 When `neon checkout` _creates_ a new branch and a `neon.ts` is present, it applies the policy automatically — deploying the function to the fresh branch. Checking out an existing branch does not re-deploy; run `neon deploy` explicitly.
 
@@ -229,7 +229,7 @@ Functions are long-running but **still serverless** — they are a request/respo
 
 - **Time to first byte: 15 minutes.** Your handler must _begin_ returning a response within 15 minutes of receiving a request. Most handlers finish in seconds; the 15-minute ceiling exists so agent workloads like image/video generation have room.
 - **Heartbeat: 15 minutes.** Open WebSocket/SSE connections stay alive as long as data flows. The timeout only fires when a connection goes silent — send at least one byte every 15 minutes to keep a quiet stream alive.
-- **`waitUntil`: 15 minutes.** Work registered with `waitUntil` keeps the invocation alive after the response is sent, up to 15 minutes — for cleanup like analytics writes and audit logs, **not** a background job runner. (`waitUntil` from `@neon/functions` is currently a stub during the preview.)
+- **`waitUntil`: 15 minutes.** Work registered with `waitUntil` (from `@neon/functions`) keeps the invocation alive after the response is sent, up to 15 minutes — for cleanup like analytics writes and audit logs, **not** a background job runner. Off the Neon runtime (local `neon dev`, tests) it's a no-op: the promise still runs but isn't tracked.
 - **Idle eviction.** With no active connections Neon shuts the function down; it may also evict/restart for operational reasons — e.g. maintenance, or moving the function to a different compute node (active functions can run for hours first). Treat eviction like a process restart — WebSocket/SSE clients must reconnect. Neon sends `SIGINT` before evicting, so a `process.on("SIGINT", ...)` handler lets you detect that the function is about to be evicted and run any last-minute cleanup. You don't need one just to close Postgres connections — Neon's pooler reclaims those on its own.
 - **Runtime:** Node.js 24, memory fixed at 2048 MiB during the preview. Slugs must match `^[a-z0-9]{1,20}$`. **An isolate is reused across many requests** — multiple requests can be in flight on the same isolate at once (interleaved on Node's single-threaded event loop), and under load the runtime runs several isolates in parallel, each with its own copy of module state. State held in module scope is therefore per-isolate (shared by every request that isolate handles) and in-memory only — persist anything that must survive eviction in Postgres. This reuse is exactly why you create a connection pool once at module scope rather than per request (see [Connecting to Postgres](#connecting-to-postgres)).
 

package/dist/global-skills/neon-functions/references/ai-sdk.md

@@ -51,7 +51,7 @@ export default {
     const { messages } = (await request.json()) as { messages: ModelMessage[] };
 
     const result = streamText({
-      model: neon("claude-sonnet-4-6"), // swap to gpt-5-mini, gemini-2-5-flash, …
+      model: neon("claude-sonnet-4-6"), // swap to gpt-5-mini, gemini-3-flash, …
       system: "You are a concise assistant with access to the user's todos.",
       messages,
       tools: {

package/dist/global-skills/neon-object-storage/SKILL.md

@@ -53,7 +53,7 @@ If the user has no Neon project, isn't on Postgres, and just needs a standalone
 
 ## Availability
 
-Check this precondition before setting anything up: Neon Object Storage is a public beta feature available only on new projects in the `us-east-2` region. Confirm the user's Neon project is a new project in `us-east-2` before proceeding; it can't be enabled on existing projects.
+Check this precondition before setting anything up: Neon Object Storage is a public beta feature available in the `us-east-2` region. Confirm the user's Neon project is in `us-east-2` before proceeding.
 
 ## Setup
 

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

@@ -4,7 +4,7 @@ description: Use when working with the Resend email API — sending transactiona
 license: MIT
 metadata:
     author: resend
-    version: "3.5.2"
+    version: "3.6.0"
     homepage: https://resend.com/agent-skills
     source: https://github.com/resend/resend-skills
     openclaw:

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

@@ -16,6 +16,7 @@ Automations are created in a `disabled` state by default. Set `status: "enabled"
 | Get | `resend.automations.get(id)` | Returns full automation with steps and connections |
 | List | `resend.automations.list(params?)` | Filter by `status`, cursor-paginated |
 | Update | `resend.automations.update(params)` | Partial update — name, status, or steps+connections |
+| Duplicate | `resend.automations.duplicate(id)` | Copies steps and connections, returns the new automation ID |
 | Delete | `resend.automations.remove(id)` | Permanent |
 | Stop | `resend.automations.stop(id)` | Sets status to `disabled` |
 | List Runs | `resend.automations.runs.list({ automationId, status? })` | Filter by run status |
@@ -23,7 +24,7 @@ Automations are created in a `disabled` state by default. Set `status: "enabled"
 
 ### Python
 
-`resend.Automations.create/get/list/update/remove/stop` — same operations with snake_case params.
+`resend.Automations.create/get/list/update/remove/duplicate/stop` — same operations with snake_case params.
 
 ## Graph Model
 
@@ -207,6 +208,14 @@ const { data, error } = await resend.automations.stop('aut_abc123');
 // data.status === 'disabled'
 ```
 
+### Duplicate an Automation
+
+```typescript
+const { data, error } = await resend.automations.duplicate('aut_abc123');
+// data.id is the new automation's ID
+// The copy starts disabled, named "<original name> (Copy)"
+```
+
 ## Constraints
 
 - Max **150 steps** per automation

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vybekiit",
-  "version": "0.7.16",
+  "version": "0.7.18",
   "description": "Choose your services, sign in, create a VybeKiit app, and open its verified local welcome page.",
   "license": "MIT",
   "publishConfig": {
@@ -32,13 +32,13 @@
     "tsup": "8.5.1",
     "typescript": "5.7.2",
     "vitest": "3.2.6",
-    "@vybekiit/db": "0.7.16",
-    "@vybekiit/core": "0.7.16",
-    "@vybekiit/agent-mcp": "0.7.16",
-    "@vybekiit/payments": "0.7.16",
-    "@vybekiit/agent-kit": "0.7.16",
-    "@vybekiit/report-mode": "0.7.16",
-    "@vybekiit/deploy": "0.7.16"
+    "@vybekiit/db": "0.7.18",
+    "@vybekiit/agent-kit": "0.7.18",
+    "@vybekiit/deploy": "0.7.18",
+    "@vybekiit/core": "0.7.18",
+    "@vybekiit/agent-mcp": "0.7.18",
+    "@vybekiit/payments": "0.7.18",
+    "@vybekiit/report-mode": "0.7.18"
   },
   "scripts": {
     "build": "tsup && node scripts/bundleGlobalSkills.mjs",