@vellumai/assistant 0.4.54 → 0.4.56

package/src/config/acp-schema.ts

@@ -0,0 +1,47 @@
+import { z } from "zod";
+
+export const AcpAgentConfigSchema = z
+  .object({
+    command: z.string().describe("Command to spawn the ACP agent process"),
+    args: z
+      .array(z.string())
+      .default([])
+      .describe("Arguments passed to the agent command"),
+    description: z
+      .string()
+      .optional()
+      .describe("Human-readable description of what this agent does"),
+    env: z
+      .record(z.string(), z.string())
+      .optional()
+      .describe("Environment variables set for the agent process"),
+  })
+  .describe("Configuration for an individual ACP agent");
+
+export const AcpConfigSchema = z
+  .object({
+    enabled: z
+      .boolean()
+      .default(false)
+      .describe(
+        "Whether the Agent Communication Protocol (ACP) system is enabled",
+      ),
+    maxConcurrentSessions: z
+      .number()
+      .int()
+      .positive()
+      .default(4)
+      .describe(
+        "Maximum number of ACP agent sessions that can run simultaneously",
+      ),
+    agents: z
+      .record(z.string(), AcpAgentConfigSchema)
+      .default({})
+      .describe("Map of agent names to their configurations"),
+  })
+  .describe(
+    "Agent Communication Protocol (ACP) — enables inter-agent communication and delegation",
+  );
+
+export type AcpConfig = z.infer<typeof AcpConfigSchema>;
+export type AcpAgentConfig = z.infer<typeof AcpAgentConfigSchema>;

package/src/config/bundled-skills/_shared/CLI_RETRIEVAL_PATTERN.md

@@ -5,23 +5,25 @@ When running the `assistant` CLI, run it using the `bash` (not `host_bash`) tool
 For account and auth workflows, prefer documented `assistant` CLI commands over
 any generic account registry:
 
-- `assistant credentials ...` for stored secrets and credential metadata
-- `assistant oauth connections token <provider-key>` for OAuth-backed integrations
+- `assistant credentials list` for discovering stored credential handles
+- `assistant oauth connections list` for discovering OAuth connection handles
+- `assistant credentials set ...` for storing new credentials
 - `assistant mcp auth <name>` when an MCP server needs browser login
 - `assistant platform status` for platform-linked deployment/auth context
 
 If a bundled skill documents a service-specific `assistant <service>` auth or
 session flow, follow that CLI exactly.
 
-# Outbound Network Requests
+# Authenticated Outbound Requests
 
-When a skill needs outbound API calls with a stored credential (outside of `assistant` CLI reads), use proxied `bash`:
+When a skill needs outbound API calls with a stored credential, use CES tools instead of
+extracting raw tokens into shell commands. CES injects credentials securely without exposing
+secrets to the assistant:
 
-```yaml
-bash:
-  network_mode: proxied
-  credential_ids:
-    - "<credential-id>"
-  command: |
-    curl -s https://api.example.com/resource
-```
+1. Discover the credential handle: `assistant credentials list --search <service>`
+2. Use the appropriate CES tool:
+   - `make_authenticated_request` for HTTP API calls (CES injects auth and returns the response)
+   - `run_authenticated_command` for CLI commands needing credential env vars (runs in CES sandbox)
+
+Note: `host_bash` is approval-gated and runs outside the CES secrecy boundary. Do not use
+`host_bash` to pass raw credentials to shell commands. Route authenticated work through CES tools.

package/src/config/bundled-skills/acp/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: acp
+description: Spawn external coding agents via the Agent Client Protocol (ACP)
+compatibility: "Designed for Vellum personal assistants"
+metadata:
+  emoji: "🔗"
+  vellum:
+    display-name: "ACP"
+---
+
+ACP agent orchestration — spawn external coding agents (Claude Code, Codex, Gemini CLI, etc.) to work on tasks via the Agent Client Protocol.
+
+## Usage
+
+Use `acp_spawn` to delegate a coding task to an external agent. The agent runs as a subprocess speaking the ACP protocol over stdio and streams results back.
+
+## First-time setup
+
+When the user first tries to use ACP and it's not configured, set it up automatically:
+
+1. **Check if `claude-agent-acp` is installed** by running `which claude-agent-acp`. If not found, install it:
+   ```bash
+   npm install -g @zed-industries/claude-agent-acp
+   ```
+
+2. **Enable ACP in the workspace config** by editing the config file to add the `acp` section. The correct config is:
+   ```json
+   {
+     "acp": {
+       "enabled": true,
+       "maxConcurrentSessions": 4,
+       "agents": {
+         "claude": {
+           "command": "claude-agent-acp",
+           "args": [],
+           "description": "Claude Code (via ACP adapter)"
+         }
+       }
+     }
+   }
+   ```
+
+3. **Wait a few seconds** for the config watcher to pick up the change (it hot-reloads automatically — no restart needed).
+
+4. Then retry the `acp_spawn` call. Do NOT run `vellum sleep && vellum wake` — that kills the conversation.
+
+## Critical: correct agent command
+
+- The command MUST be `claude-agent-acp` — this is the ACP adapter from `@zed-industries/claude-agent-acp`.
+- NEVER use `claude`, `claude -p`, `claude --acp`, or any other command. Only `claude-agent-acp` speaks the ACP JSON-RPC protocol.
+- NEVER change an existing ACP config to use a different command. If the config already has `claude-agent-acp`, leave it alone.
+
+## Tips
+
+- The spawned agent runs autonomously with its own tools, file editing, and terminal access.
+- Results are streamed back and injected into the conversation when the agent completes.
+- Use `acp_status` to check on running agents and `acp_abort` to stop them.
+- The `cwd` parameter controls where the agent works — set it to the project root the user wants the agent to operate in.

package/src/config/bundled-skills/acp/TOOLS.json

@@ -0,0 +1,79 @@
+{
+  "version": 1,
+  "tools": [
+    {
+      "name": "acp_spawn",
+      "description": "Spawn an external coding agent (e.g. Claude Code, Codex, Gemini CLI) via ACP to work on a task. The agent runs as a subprocess and streams results back. Use this when you want to delegate a coding task to an external agent that has its own tools, file editing, and terminal access. If ACP is not enabled, follow the setup instructions in SKILL.md to install claude-agent-acp and configure it. The command MUST be 'claude-agent-acp' — NEVER use 'claude', 'claude -p', or 'claude --acp'.",
+      "category": "orchestration",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "agent": {
+            "type": "string",
+            "description": "Which agent to spawn (e.g. 'claude', 'codex', 'gemini'). Defaults to 'claude'."
+          },
+          "task": {
+            "type": "string",
+            "description": "The task to give the agent — what it should accomplish"
+          },
+          "cwd": {
+            "type": "string",
+            "description": "Working directory for the agent. This determines where the agent runs and where its session is stored. Set this to the project/repo root the user wants the agent to work in. Defaults to current conversation's working directory."
+          },
+          "reason": {
+            "type": "string",
+            "description": "Brief explanation of why this tool is being called"
+          }
+        },
+        "required": ["task"]
+      },
+      "executor": "tools/acp-spawn.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "acp_status",
+      "description": "Get the status of a specific ACP session or list all ACP sessions. Only use this when the user explicitly asks about ACP session status — do NOT poll automatically, as you will be notified when sessions complete.",
+      "category": "orchestration",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "acp_session_id": {
+            "type": "string",
+            "description": "Optional ACP session ID to query. If omitted, returns all ACP sessions."
+          },
+          "reason": {
+            "type": "string",
+            "description": "Brief explanation of why this tool is being called"
+          }
+        },
+        "required": []
+      },
+      "executor": "tools/acp-status.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "acp_abort",
+      "description": "Abort a running ACP session by ID. This kills the agent process and removes the session.",
+      "category": "orchestration",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "acp_session_id": {
+            "type": "string",
+            "description": "The ID of the ACP session to abort."
+          },
+          "reason": {
+            "type": "string",
+            "description": "Brief explanation of why this tool is being called"
+          }
+        },
+        "required": ["acp_session_id"]
+      },
+      "executor": "tools/acp-abort.ts",
+      "execution_target": "host"
+    }
+  ]
+}

package/src/config/bundled-skills/{settings/tools/set-avatar.ts → acp/tools/acp-abort.ts}

@@ -1,4 +1,4 @@
-import { setAvatarTool } from "../../../../tools/system/avatar-generator.js";
+import { executeAcpAbort } from "../../../../tools/acp/abort.js";
 import type {
   ToolContext,
   ToolExecutionResult,
@@ -8,5 +8,5 @@ export async function run(
   input: Record<string, unknown>,
   context: ToolContext,
 ): Promise<ToolExecutionResult> {
-  return setAvatarTool.execute(input, context);
+  return executeAcpAbort(input, context);
 }

package/src/config/bundled-skills/acp/tools/acp-spawn.ts

@@ -0,0 +1,12 @@
+import { executeAcpSpawn } from "../../../../tools/acp/spawn.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeAcpSpawn(input, context);
+}

package/src/config/bundled-skills/acp/tools/acp-status.ts

@@ -0,0 +1,12 @@
+import { executeAcpStatus } from "../../../../tools/acp/status.js";
+import type {
+  ToolContext,
+  ToolExecutionResult,
+} from "../../../../tools/types.js";
+
+export async function run(
+  input: Record<string, unknown>,
+  context: ToolContext,
+): Promise<ToolExecutionResult> {
+  return executeAcpStatus(input, context);
+}

package/src/config/bundled-skills/app-builder/SKILL.md

@@ -10,7 +10,7 @@ metadata:
       - "frontend-design"
 ---
 
-You are an expert app builder and visual designer. When the user asks you to create an app, tool, or utility, you immediately design a data schema, choose a stunning visual direction, build a self-contained HTML/CSS/JS interface, and open it — all in one step. You don't discuss or ask for permission to be creative. You ARE the designer: you pick the colors, the layout, the atmosphere, the micro-interactions. Your apps should make users stop and say "whoa" — they should feel designed, not generated.
+You are an expert app builder and visual designer. When the user asks you to create an app, tool, or utility, you immediately design a data schema, choose a stunning visual direction, build the interface, and open it — all in one step. You don't discuss or ask for permission to be creative. You ARE the designer: you pick the colors, the layout, the atmosphere, the micro-interactions. Your apps should make users stop and say "whoa" — they should feel designed, not generated.
 
 **Every app gets its own visual identity.** A plant tracker should feel earthy and green. A finance dashboard should feel precise and navy. A fitness app should feel energetic and purple. Apps should look like they were designed by a boutique studio for that specific domain — not like generic branded tools. Think standalone premium product, not template.
 
@@ -88,11 +88,9 @@ Apps are rendered inside a sandboxed WebView on macOS.
 
 <!-- feature:app-builder-multifile:start -->
 
-You can build them in two formats: **multi-file TSX** (preferred) or **single-file HTML** (legacy).
+#### Multi-file TSX projects
 
-#### Multi-file TSX projects (preferred)
-
-Use this format for any non-trivial app. You get component reuse, TypeScript type-checking, and clean file organization. The build system uses esbuild to bundle everything automatically.
+Build apps as multi-file TSX projects. You get component reuse, TypeScript type-checking, and clean file organization. The build system uses esbuild to bundle everything automatically.
 
 **Project structure:**
 
@@ -151,7 +149,7 @@ useEffect(() => {
 }, []);
 ```
 
-**File workflow:** Use `app_file_write` for each source file. The build happens automatically when you call `app_open`.
+**File workflow:** Use `app_file_write` for each source file. Each write automatically triggers a recompile of the project.
 
 **Allowed third-party packages:** `date-fns`, `chart.js`, `lodash-es`, `zod`, `clsx`, `lucide`. Import them directly — esbuild resolves them at build time. No CDN imports. Note: `lucide` is the vanilla JS icon library (not `lucide-react`). Use its `createElement` or `createIcons` API, or manually inline SVG — do not import JSX icon components.
 
@@ -219,6 +217,8 @@ app_file_write(app_id, "src/styles.css", `.app { padding: var(--v-spacing-lg); }
 - The WebView blocks all navigation — links and form `action` attributes won't work
 <!-- feature:app-builder-multifile:end -->
 
+<!-- feature:app-builder-multifile:alt -->
+
 #### Single HTML file
 
 Write a complete, self-contained HTML document.
@@ -231,6 +231,8 @@ Write a complete, self-contained HTML document.
 - Design for 400-600px width with graceful resizing
 - The WebView blocks all navigation — links and form `action` attributes won't work
 
+<!-- feature:app-builder-multifile:alt:end -->
+
 #### Injected design system
 
 A design system CSS is auto-injected inside a `@layer`, so your styles always take priority. It provides element defaults and automatic light/dark mode switching via `prefers-color-scheme`.
@@ -420,6 +422,8 @@ Important:
 
 `localStorage` and `sessionStorage` are available for ephemeral UI state (filters, view modes, collapsed state, preferences, form drafts). Use `window.vellum.data` for persistent app records, `localStorage` for UI preferences.
 
+<!-- feature:app-builder-multifile:alt -->
+
 #### JavaScript patterns
 
 Initialize apps with clean state management:
@@ -472,7 +476,14 @@ function showView(name) {
 }
 ```
 
+<!-- feature:app-builder-multifile:alt:end -->
+
+<!-- feature:app-builder-multifile:start -->
+### 4. Create and Open the App
+<!-- feature:app-builder-multifile:end -->
+<!-- feature:app-builder-multifile:alt -->
 ### 5. Create and Open the App
+<!-- feature:app-builder-multifile:alt:end -->
 
 Call `app_create` with:
 
@@ -485,7 +496,12 @@ Call `app_create` with:
 
 The app is NOT opened in a workspace panel automatically — users open it via the 'Open App' button on the inline card.
 
+<!-- feature:app-builder-multifile:start -->
+### 5. Handle Iteration
+<!-- feature:app-builder-multifile:end -->
+<!-- feature:app-builder-multifile:alt -->
 ### 6. Handle Iteration
+<!-- feature:app-builder-multifile:alt:end -->
 
 When the user requests changes, prefer **`app_file_edit`** over rewriting the entire file.
 

package/src/config/bundled-skills/browser/SKILL.md

@@ -6,8 +6,9 @@ metadata:
   emoji: "🌐"
   vellum:
     display-name: "Browser"
-    user-invocable: true
     feature-flag: "browser"
+    activation-hints:
+      - "Load first if you need browser_* tools (navigating, clicking, extracting web content)"
 ---
 
 Use this skill to browse the web. After loading this skill, the following browser tools become available:

package/src/config/bundled-skills/browser/TOOLS.json

@@ -67,7 +67,7 @@
     },
     {
       "name": "browser_close",
-      "description": "Close the browser page for the current session, or all pages if close_all_pages is true.",
+      "description": "Close the browser page for the current conversation, or all pages if close_all_pages is true.",
       "category": "browser",
       "risk": "low",
       "input_schema": {
@@ -75,7 +75,7 @@
         "properties": {
           "close_all_pages": {
             "type": "boolean",
-            "description": "If true, close all browser pages and the browser context. Default: false (close only the current session page)."
+            "description": "If true, close all browser pages and the browser context. Default: false (close only the current conversation page)."
           },
           "reason": {
             "type": "string",

package/src/config/bundled-skills/browser/tools/browser-wait-for-download.ts

@@ -15,7 +15,7 @@ export async function run(
 
   try {
     const download = await browserManager.waitForDownload(
-      context.sessionId,
+      context.conversationId,
       timeout,
     );
     return {

package/src/config/bundled-skills/chatgpt-import/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "📥"
   vellum:
     display-name: "ChatGPT Import"
-    user-invocable: true
 ---
 
 Import ChatGPT conversation history into Vellum so users can keep their conversation context and memory when switching from ChatGPT.

package/src/config/bundled-skills/claude-code/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "💻"
   vellum:
     display-name: "Claude Code"
-    user-invocable: true
 ---
 
 You are delegating a coding task to Claude Code, an autonomous AI coding agent. Use this skill when the user needs hands-on software engineering work done.
@@ -40,7 +39,7 @@ Do NOT delegate when:
 - Claude Code runs in a sandboxed environment with approval flows for destructive actions
 - File writes, edits, and shell commands that modify state require user confirmation (unless auto-approved by trust rules)
 - Read-only operations (file reads, searches, web fetches) are auto-approved
-- The working directory defaults to the current session's working directory but can be overridden
+- The working directory defaults to the current conversation's working directory but can be overridden
 
 ## Worker Profiles
 

package/src/config/bundled-skills/claude-code/TOOLS.json

@@ -23,7 +23,7 @@
           },
           "working_dir": {
             "type": "string",
-            "description": "Working directory for Claude Code (defaults to session working directory)"
+            "description": "Working directory for Claude Code (defaults to conversation working directory)"
           },
           "resume": {
             "type": "string",

package/src/config/bundled-skills/computer-use/SKILL.md

@@ -6,14 +6,12 @@ metadata:
   emoji: "🖥️"
   vellum:
     display-name: "Computer Use"
-    user-invocable: false
-    disable-model-invocation: true
 ---
 
 This skill provides the computer_use_* action tools for controlling
 the macOS desktop. CU tools run through the main agent loop via HostCuProxy.
 
-The skill is internally preactivated for sessions with a connected desktop client.
+The skill is internally preactivated for conversations with a connected desktop client.
 
 Tools in this skill are proxy tools — execution is forwarded to the connected
 macOS client, never handled locally by the assistant.

package/src/config/bundled-skills/contacts/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "👥"
   vellum:
     display-name: "Contacts"
-    user-invocable: true
     feature-flag: "contacts"
 ---
 

package/src/config/bundled-skills/contacts/TOOLS.json

@@ -150,6 +150,10 @@
           "reason": {
             "type": "string",
             "description": "Brief non-technical explanation of why this tool is being called"
+          },
+          "account": {
+            "type": "string",
+            "description": "Email address of the Gmail account to use. Required when multiple Gmail accounts are connected. If omitted, uses the most recently connected account."
           }
         },
         "required": ["action"]

package/src/config/bundled-skills/contacts/tools/google-contacts.ts

@@ -36,6 +36,7 @@ export async function run(
   input: Record<string, unknown>,
   _context: ToolContext,
 ): Promise<ToolExecutionResult> {
+  const account = input.account as string | undefined;
   const action = input.action as string;
 
   if (!action) {
@@ -43,7 +44,10 @@ export async function run(
   }
 
   try {
-    const connection = await resolveOAuthConnection("integration:google");
+    const connection = await resolveOAuthConnection(
+      "integration:google",
+      account,
+    );
     switch (action) {
       case "list": {
         const pageSize = (input.page_size as number) ?? 50;

package/src/config/bundled-skills/followups/SKILL.md

@@ -27,7 +27,7 @@ When `expected_response_hours` is set, the follow-up automatically becomes overd
 
 Follow-ups can be resolved in two ways:
 1. **By ID** -- resolve a specific follow-up directly
-2. **By thread** -- provide channel + thread_id to auto-resolve all matching pending follow-ups (useful when a response arrives on a thread)
+2. **By conversation** -- provide channel + conversation_id to auto-resolve all matching pending follow-ups (useful when a response arrives on a conversation)
 
 ## Tips
 

package/src/config/bundled-skills/followups/TOOLS.json

@@ -13,9 +13,9 @@
             "type": "string",
             "description": "Communication channel (e.g. email, slack, whatsapp)"
           },
-          "thread_id": {
+          "conversation_id": {
             "type": "string",
-            "description": "External thread or conversation identifier on that channel"
+            "description": "External conversation identifier on that channel"
           },
           "contact_id": {
             "type": "string",
@@ -34,7 +34,7 @@
             "description": "Brief non-technical explanation of why this tool is being called"
           }
         },
-        "required": ["channel", "thread_id"]
+        "required": ["channel", "conversation_id"]
       },
       "executor": "tools/followup-create.ts",
       "execution_target": "host"
@@ -76,7 +76,7 @@
     },
     {
       "name": "followup_resolve",
-      "description": "Manually resolve a follow-up by ID, or auto-resolve by channel + thread ID when a response is received.",
+      "description": "Manually resolve a follow-up by ID, or auto-resolve by channel + conversation ID when a response is received.",
       "category": "followups",
       "risk": "low",
       "input_schema": {
@@ -88,11 +88,11 @@
           },
           "channel": {
             "type": "string",
-            "description": "Channel to match (used with thread_id for auto-resolution)"
+            "description": "Channel to match (used with conversation_id for auto-resolution)"
           },
-          "thread_id": {
+          "conversation_id": {
             "type": "string",
-            "description": "Thread ID to match (used with channel for auto-resolution)"
+            "description": "Conversation ID to match (used with channel for auto-resolution)"
           },
           "reason": {
             "type": "string",

package/src/config/bundled-skills/gmail/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "📨"
   vellum:
     display-name: "Gmail"
-    user-invocable: true
 ---
 
 This skill provides Gmail-specific tools. For cross-platform messaging (send, read, search, reply), use the **messaging** skill. Gmail tools depend on the messaging skill's provider infrastructure — load messaging first if Gmail is not yet connected.

package/src/config/bundled-skills/google-calendar/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "📅"
   vellum:
     display-name: "Google Calendar"
-    user-invocable: true
 ---
 
 You are a Google Calendar assistant with full access to the user's calendar. Use the Calendar tools to help them view, create, and manage events.

package/src/config/bundled-skills/google-calendar/tools/calendar-check-availability.ts

@@ -15,7 +15,7 @@ export async function run(
   const calendarIds = (input.calendar_ids as string[]) ?? ["primary"];
   const timezone = input.timezone as string | undefined;
 
-  const connection = await getCalendarConnection(account, calendarIds[0]);
+  const connection = await getCalendarConnection(account);
   const result = await calendar.freeBusy(connection, {
     timeMin,
     timeMax,

package/src/config/bundled-skills/google-calendar/tools/calendar-create-event.ts

@@ -41,7 +41,7 @@ export async function run(
     eventBody.attendees = attendees.map((email) => ({ email }));
   }
 
-  const connection = await getCalendarConnection(account, calendarId);
+  const connection = await getCalendarConnection(account);
   const event = await calendar.createEvent(connection, eventBody, calendarId);
   const link = event.htmlLink ? ` View it here: ${event.htmlLink}` : "";
   return ok(`Event created (ID: ${event.id}).${link}`);

package/src/config/bundled-skills/google-calendar/tools/calendar-get-event.ts

@@ -13,7 +13,7 @@ export async function run(
   const eventId = input.event_id as string;
   const calendarId = (input.calendar_id as string) ?? "primary";
 
-  const connection = await getCalendarConnection(account, calendarId);
+  const connection = await getCalendarConnection(account);
   const event = await calendar.getEvent(connection, eventId, calendarId);
   return ok(JSON.stringify(event, null, 2));
 }

package/src/config/bundled-skills/google-calendar/tools/calendar-list-events.ts

@@ -18,7 +18,7 @@ export async function run(
   const singleEvents = (input.single_events as boolean) ?? true;
   const orderBy = input.order_by as "startTime" | "updated" | undefined;
 
-  const connection = await getCalendarConnection(account, calendarId);
+  const connection = await getCalendarConnection(account);
   const result = await calendar.listEvents(connection, calendarId, {
     timeMin,
     timeMax,

package/src/config/bundled-skills/google-calendar/tools/calendar-rsvp.ts

@@ -14,7 +14,7 @@ export async function run(
   const response = input.response as "accepted" | "declined" | "tentative";
   const calendarId = (input.calendar_id as string) ?? "primary";
 
-  const connection = await getCalendarConnection(account, calendarId);
+  const connection = await getCalendarConnection(account);
 
   // First get the event to find the user's attendee entry
   const event = await calendar.getEvent(connection, eventId, calendarId);

package/src/config/bundled-skills/google-calendar/tools/shared.ts

@@ -12,10 +12,6 @@ export function ok(content: string): ToolExecutionResult {
  */
 export async function getCalendarConnection(
   account?: string,
-  calendarId?: string,
 ): Promise<OAuthConnection> {
-  // If no explicit account but calendar_id looks like an email, use it as the account hint
-  const resolved =
-    account ?? (calendarId?.includes("@") ? calendarId : undefined);
-  return resolveOAuthConnection("integration:google", resolved);
+  return resolveOAuthConnection("integration:google", account);
 }

package/src/config/bundled-skills/image-studio/SKILL.md

@@ -6,7 +6,6 @@ metadata:
   emoji: "🎨"
   vellum:
     display-name: "Image Studio"
-    user-invocable: true
 ---
 
 You are an image generation assistant. When the user asks you to create or edit images, use the `media_generate_image` tool.