@vellumai/assistant 0.6.3 → 0.6.5

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

@@ -1,36 +0,0 @@
-import type {
-  ToolContext,
-  ToolExecutionResult,
-} from "../../../../tools/types.js";
-import * as calendar from "../calendar-client.js";
-import { getCalendarConnection, ok } from "./shared.js";
-
-export async function run(
-  input: Record<string, unknown>,
-  _context: ToolContext,
-): Promise<ToolExecutionResult> {
-  const account = input.account as string | undefined;
-  const eventId = input.event_id as string;
-  const response = input.response as "accepted" | "declined" | "tentative";
-
-  const connection = await getCalendarConnection(account);
-
-  // Fetch the event to get context for the response message
-  const event = await calendar.getEvent(connection, eventId);
-
-  // If the user is the organizer, no RSVP is needed
-  if (event.responseStatus?.response === "organizer") {
-    return ok("You are the organizer of this event. No RSVP needed.");
-  }
-
-  // Send RSVP via the dedicated Microsoft Graph endpoint, notifying the organizer
-  await calendar.rsvpEvent(connection, eventId, response, true);
-
-  const responseLabel =
-    response === "accepted"
-      ? "Accepted"
-      : response === "declined"
-        ? "Declined"
-        : "Tentatively accepted";
-  return ok(`${responseLabel} the event "${event.subject ?? eventId}".`);
-}

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

@@ -1,17 +0,0 @@
-import type { OAuthConnection } from "../../../../oauth/connection.js";
-import { resolveOAuthConnection } from "../../../../oauth/connection-resolver.js";
-import type { ToolExecutionResult } from "../../../../tools/types.js";
-
-export function ok(content: string): ToolExecutionResult {
-  return { content, isError: false };
-}
-
-export function err(message: string): ToolExecutionResult {
-  return { content: message, isError: true };
-}
-
-export async function getCalendarConnection(
-  account?: string,
-): Promise<OAuthConnection> {
-  return resolveOAuthConnection("outlook", { account });
-}

package/src/config/bundled-skills/outlook-calendar/types.ts

@@ -1,120 +0,0 @@
-/** Microsoft Graph date+time pair. timeZone may be omitted when dateTime carries an offset. */
-export interface OutlookDateTimeZone {
-  dateTime: string;
-  timeZone?: string;
-}
-
-/** Attendee on a calendar event. */
-export interface OutlookCalendarAttendee {
-  emailAddress: { address: string; name?: string };
-  type: "required" | "optional" | "resource";
-  status?: {
-    response:
-      | "none"
-      | "organizer"
-      | "tentativelyAccepted"
-      | "accepted"
-      | "declined"
-      | "notResponded";
-    time?: string;
-  };
-}
-
-/** Physical or virtual location for a calendar event. */
-export interface OutlookLocation {
-  displayName?: string;
-  locationType?: string;
-  address?: Record<string, unknown>;
-  coordinates?: Record<string, unknown>;
-}
-
-/** Rich-text body of a calendar item. */
-export interface OutlookItemBody {
-  contentType: "text" | "html";
-  content: string;
-}
-
-/** A single calendar event from Microsoft Graph. */
-export interface OutlookCalendarEvent {
-  id: string;
-  subject?: string;
-  bodyPreview?: string;
-  body?: OutlookItemBody;
-  start?: OutlookDateTimeZone;
-  end?: OutlookDateTimeZone;
-  location?: OutlookLocation;
-  locations?: OutlookLocation[];
-  attendees?: OutlookCalendarAttendee[];
-  organizer?: { emailAddress: { address: string; name?: string } };
-  isAllDay?: boolean;
-  isCancelled?: boolean;
-  showAs?:
-    | "free"
-    | "tentative"
-    | "busy"
-    | "oof"
-    | "workingElsewhere"
-    | "unknown";
-  importance?: "low" | "normal" | "high";
-  sensitivity?: "normal" | "personal" | "private" | "confidential";
-  webLink?: string;
-  onlineMeetingUrl?: string;
-  createdDateTime?: string;
-  lastModifiedDateTime?: string;
-  seriesMasterId?: string;
-  type?: "singleInstance" | "occurrence" | "exception" | "seriesMaster";
-  categories?: string[];
-  responseStatus?: { response: string; time?: string };
-}
-
-/** Paginated list of calendar events. */
-export interface OutlookCalendarEventListResponse {
-  value?: OutlookCalendarEvent[];
-  "@odata.nextLink"?: string;
-  "@odata.deltaLink"?: string;
-  "@odata.count"?: number;
-}
-
-/** A single schedule item (free/busy block). */
-export interface OutlookScheduleItem {
-  status:
-    | "free"
-    | "tentative"
-    | "busy"
-    | "oof"
-    | "workingElsewhere"
-    | "unknown";
-  start: OutlookDateTimeZone;
-  end: OutlookDateTimeZone;
-  subject?: string;
-  location?: string;
-}
-
-/** Schedule information for one user. */
-export interface OutlookScheduleInformation {
-  scheduleId: string;
-  availabilityView: string;
-  scheduleItems: OutlookScheduleItem[];
-  error?: Record<string, unknown>;
-}
-
-/** Response from the getSchedule endpoint. */
-export interface OutlookScheduleResponse {
-  value?: OutlookScheduleInformation[];
-}
-
-/** A calendar in the user's mailbox. */
-export interface OutlookCalendar {
-  id: string;
-  name?: string;
-  color?: string;
-  isDefaultCalendar?: boolean;
-  canEdit?: boolean;
-  owner?: { name: string; address: string };
-}
-
-/** Paginated list of calendars. */
-export interface OutlookCalendarListResponse {
-  value?: OutlookCalendar[];
-  "@odata.nextLink"?: string;
-}

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

@@ -1,107 +0,0 @@
----
-name: slack
-description: Read, send, and manage Slack messages via the Web API
-compatibility: "Designed for Vellum personal assistants"
-metadata:
-  emoji: "💬"
-  vellum:
-    display-name: "Slack"
----
-
-You help users interact with their Slack workspace. All Slack operations use the **Slack Web API** directly via the `bash` tool with credential proxy — there are no dedicated Slack tools.
-
-## Making Slack API Calls
-
-Use `bash` with these parameters:
-
-- **`network_mode`**: `"proxied"`
-- **`credential_ids`**: `["slack_channel/bot_token"]`
-
-The proxy intercepts requests to `slack.com` and injects the bot token as a `Bearer` header automatically. You never see or handle the token directly.
-
-Example — list channels:
-
-```
-bash {
-  command: "curl -s https://slack.com/api/conversations.list?types=public_channel,private_channel | jq ."
-  network_mode: "proxied"
-  credential_ids: ["slack_channel/bot_token"]
-  activity: "to list your Slack channels"
-}
-```
-
-Refer to https://api.slack.com/methods for available endpoints. The bot token scopes configured in the Slack app manifest determine what's accessible.
-
-## Common Operations
-
-### Reading messages
-
-- `conversations.list` — list channels
-- `conversations.history` — read recent messages in a channel
-- `conversations.replies` — read a full thread
-- `users.info` — resolve user IDs to display names
-
-### Sending messages
-
-- `chat.postMessage` — send a message to a channel or DM
-- `chat.update` — edit a message the bot previously sent
-- `chat.delete` — delete a message the bot previously sent
-
-### Reacting & managing
-
-- `reactions.add` — add an emoji reaction
-- `conversations.leave` — leave a channel
-- `search.messages` — search across the workspace
-
-### Channel scanning
-
-When the user asks to scan or catch up on Slack:
-
-1. Call `conversations.list` to get active channels, then `conversations.history` for each
-2. Present an overview first: channel names, message counts, top threads
-3. Offer to drill into specific threads with `conversations.replies`
-4. Summarize with attribution: who said what, decisions made, open questions
-
-## User Resolution
-
-When you need to send a DM or look up a Slack user by name, check contacts first to avoid redundant API calls:
-
-1. **Before calling `users.list`**: Use `contact_search` with `query: "<name>"` and `channel_type: "slack"`. If a matching contact has `externalUserId` (Slack user ID) and `externalChatId` (DM channel ID), skip the API lookups and use those IDs directly with `chat.postMessage`.
-
-   When `contact_search` returns notes for the recipient, use them to inform the message's tone, formality, and content. Contact notes capture relationship context and communication preferences that should shape how you write to this person.
-
-2. **After resolving via API**: When you had to call `users.list` or `conversations.open` to resolve a user, save the contact with `contact_upsert` so you can find them by name next time. External Slack IDs (user ID, DM channel ID) are cached automatically by the messaging layer and should not be passed through `contact_upsert`.
-
-## Privacy Rules
-
-**Channel privacy must be respected at all times:**
-
-- Check `is_private` on each channel before sharing content elsewhere
-- Private channel content must NEVER be shared to other channels, DMs, or external destinations
-- If the user asks to share private channel content, explain why you can't and offer alternatives (summarize the topic without quoting, ask the user to share manually)
-- Public channel content can be shared with attribution ("From #channel: ...")
-- Always confirm with the user before sending content to any destination
-
-## Delivery Notes
-
-- For rich content (digests, reports, formatted summaries): use the Slack API directly via `chat.postMessage` with blocks
-- For short alerts: `send_notification` is fine — it lets the notification router pick the best channel
-- For scheduled tasks: always include an explicit Slack API call to deliver results, otherwise output only lives in the conversation log
-
-## Threading
-
-When responding to messages from Slack channels, replies should be threaded. Pass `thread_ts` to `chat.postMessage` to reply in a thread rather than posting a new top-level message.
-
-## Connection
-
-Before making any Slack API calls, verify that Slack is connected. If not connected, load the **slack-app-setup** skill (`skill_load` with `skill: "slack-app-setup"`) and follow its guided flow. Do NOT improvise setup instructions — the `slack-app-setup` skill is the single source of truth. Slack uses Socket Mode and does not require redirect URLs or any OAuth flow.
-
-## Error Handling
-
-If a Slack API call fails due to missing or invalid credentials — for example, an error indicating that `slack_channel/bot_token` is not found, the credential is missing, or the token is invalid — do NOT attempt to fix the credentials manually. Instead, load the **slack-app-setup** skill (`skill_load` with `skill: "slack-app-setup"`) and follow its guided flow to set up or reconnect Slack. Tell the user something like "Slack needs to be reconnected" and start the setup skill.
-
-## Communication Style
-
-- **Be action-oriented.** When the user asks to check Slack, start scanning immediately.
-- **Keep it human.** Never mention OAuth, tokens, APIs, proxies, or credential IDs. If something isn't working, say "Slack needs to be reconnected."
-- **Show progress.** When scanning multiple channels, tell the user what you're doing.

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

@@ -1,37 +0,0 @@
----
-name: tasks
-description: Two-layer task system with reusable templates and a prioritized work queue
-compatibility: "Designed for Vellum personal assistants"
-metadata:
-  emoji: "✅"
-  vellum:
-    display-name: "Tasks"
-    activation-hints:
-      - "User wants to add, check, or manage items on their to-do list or task queue"
-      - "For one-off action items, not recurring automations (use schedule for those)"
-    avoid-when:
-      - "User wants recurring/scheduled automation — use the schedule skill instead"
----
-
-Two-layer task system: **task templates** (reusable definitions with input placeholders) and **work items** (instances in the Task Queue with priority tiers and status tracking).
-
-## Task Templates
-
-Templates are reusable definitions saved from conversations via `task_save`. They capture the conversation pattern with placeholders that can be run later with different inputs via `task_run`. List templates with `task_list`, delete with `task_delete`.
-
-## Work Items (Task Queue)
-
-Work items are the user-facing "Tasks" managed through conversation. They track status and priority:
-
-- **Priority tiers**: 0 = high, 1 = medium (default), 2 = low
-- **Status flow**: queued -> running -> awaiting_review -> done
-- **Resolution precedence**: work_item_id > task_id > task_name > title
-
-Use `task_list_add` to enqueue items (ad-hoc or from a template), `task_list_show` to view the queue, `task_list_update` to modify, and `task_list_remove` to remove.
-
-## Tips
-
-- When the user says "add to my tasks" or "add to my queue", use `task_list_add` (NOT schedule_create).
-- Use `task_save` only when the user wants to capture a conversation pattern as a reusable template.
-- `task_list` shows saved templates; `task_list_show` shows the active work queue.
-- **Always specify `required_tools`** when calling `task_list_add`. Think about what tools the task will need at execution time and list them explicitly (e.g. `["host_bash"]` for shell commands, `["host_file_read", "host_file_write"]` for file operations, `["web_search", "web_fetch"]` for web lookups). The user must approve these tools before the task can run - omitting them forces a fallback to all tools, which is noisy and may miss non-standard tools the task actually needs.

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

@@ -1,353 +0,0 @@
-{
-  "version": 1,
-  "tools": [
-    {
-      "name": "task_save",
-      "description": "Save the current conversation as a reusable task template (definition). This is NOT for adding items to the user's task queue \u2014 use task_list_add for that. task_save extracts the conversation pattern into a reusable definition with placeholders that can be run later with different inputs.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "conversation_id": {
-            "type": "string",
-            "description": "The conversation to capture as a task template. If omitted, uses the current conversation."
-          },
-          "title": {
-            "type": "string",
-            "description": "Optional override for the auto-generated task title"
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        },
-        "required": []
-      },
-      "executor": "tools/task-save.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_run",
-      "description": "Run a task template. Resolves the template by name (fuzzy match) or ID, renders it with the provided inputs, and returns the rendered prompt for execution as a Task (work item).",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "task_name": {
-            "type": "string",
-            "description": "Fuzzy match a task template by name (case-insensitive substring match)"
-          },
-          "task_id": {
-            "type": "string",
-            "description": "Exact match a task template by ID"
-          },
-          "inputs": {
-            "type": "object",
-            "description": "Values for template placeholders (e.g. {\"file_path\": \"/tmp/foo.txt\", \"url\": \"https://example.com\"})",
-            "additionalProperties": {
-              "type": "string"
-            }
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-run.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_list",
-      "description": "List saved task templates (reusable definitions). To see your active Tasks (work items), use task_list_show instead.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-list.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_delete",
-      "description": "Delete one or more task templates by ID. Also removes associated task runs and work items (Tasks).",
-      "category": "tasks",
-      "risk": "medium",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "task_ids": {
-            "type": "array",
-            "items": {
-              "type": "string"
-            },
-            "description": "One or more task IDs to delete."
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        },
-        "required": ["task_ids"]
-      },
-      "executor": "tools/task-delete.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_list_show",
-      "description": "List the user's Task Queue (work items) with their status, priority, and last run info. Use this when the user says \"show my tasks\", \"what's in my queue\", \"what's on my task list\", or similar. Present the results as a summary in the conversation.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "status": {
-            "oneOf": [
-              {
-                "type": "string"
-              },
-              {
-                "type": "array",
-                "items": {
-                  "type": "string"
-                }
-              }
-            ],
-            "description": "Optional status filter. A single status string (e.g. \"queued\") or an array of statuses to include."
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-list-show.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_list_add",
-      "description": "Add a task to the user's Task Queue. Use this when the user says \"add to my tasks\", \"add to my queue\", \"put this on my task list\", \"track this task\", or any variation of adding a one-off item they want to remember or work on. You can provide just a title for ad-hoc items, or reference an existing task definition by name or ID. Do NOT use schedule_create or reminder for simple \"add to tasks\" requests \u2014 those are for timed/recurring automation only.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "task_id": {
-            "type": "string",
-            "description": "ID of an existing task definition to enqueue. Provide this, task_name, or just title."
-          },
-          "task_name": {
-            "type": "string",
-            "description": "Title/name of an existing task definition to search for (case-insensitive substring match). Provide this, task_id, or just title."
-          },
-          "title": {
-            "type": "string",
-            "description": "Title for the work item. When provided WITHOUT task_id or task_name, creates an ad-hoc work item directly (a lightweight task template is auto-created behind the scenes). When provided WITH task_id or task_name, overrides the task definition title."
-          },
-          "execution_prompt": {
-            "type": "string",
-            "description": "The full instruction to execute when this task runs. If omitted, the title is used as the execution prompt. Use this to preserve detailed instructions (e.g. full file paths, specific parameters) that would be lost in a short display title."
-          },
-          "notes": {
-            "type": "string",
-            "description": "Notes to attach to the work item."
-          },
-          "priority_tier": {
-            "type": "number",
-            "description": "0 = high, 1 = medium (default), 2 = low."
-          },
-          "sort_index": {
-            "type": "number",
-            "description": "Manual sort order within the priority tier."
-          },
-          "if_exists": {
-            "type": "string",
-            "enum": ["create_duplicate", "reuse_existing", "update_existing"],
-            "description": "What to do if an active work item with the same title already exists. Defaults to \"reuse_existing\"."
-          },
-          "required_tools": {
-            "type": "array",
-            "items": {
-              "type": "string"
-            },
-            "description": "Tools the task will need at execution time. Always specify this \u2014 think about what tools are needed to accomplish the task (e.g. [\"host_bash\"] for shell commands, [\"host_file_read\", \"host_file_write\"] for file operations, [\"web_search\"] for web lookups). The user must approve these before the task runs. Pass [] if no tools are needed."
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-list-add.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_list_update",
-      "description": "Update an existing task in the Task Queue. Can change priority, notes, status (including marking as done), or sort order. Identifies the task by work item ID, task ID, task name, or title.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "work_item_id": {
-            "type": "string",
-            "description": "Direct work item ID (most precise selector)"
-          },
-          "task_id": {
-            "type": "string",
-            "description": "Task definition ID to find the work item for"
-          },
-          "task_name": {
-            "type": "string",
-            "description": "Task name/title to search for (case-insensitive exact match)"
-          },
-          "title": {
-            "type": "string",
-            "description": "Work item title to search for (case-insensitive exact match)"
-          },
-          "priority_tier": {
-            "type": "number",
-            "description": "0 = high, 1 = medium, 2 = low"
-          },
-          "notes": {
-            "type": "string",
-            "description": "Updated notes for the work item"
-          },
-          "status": {
-            "type": "string",
-            "enum": [
-              "queued",
-              "running",
-              "awaiting_review",
-              "done",
-              "failed",
-              "cancelled",
-              "archived"
-            ],
-            "description": "New status for the work item. To mark a task as done, it must currently be in 'awaiting_review' status."
-          },
-          "sort_index": {
-            "type": "number",
-            "description": "Manual sort order within the same priority tier"
-          },
-          "filter_priority_tier": {
-            "type": "number",
-            "description": "Disambiguation filter: narrow by current priority tier (0=high, 1=medium, 2=low) when multiple items share the same title/task_id. This identifies WHICH item to update \u2014 it is NOT the new priority value."
-          },
-          "filter_status": {
-            "type": "string",
-            "enum": [
-              "queued",
-              "running",
-              "awaiting_review",
-              "failed",
-              "cancelled",
-              "done",
-              "archived"
-            ],
-            "description": "Disambiguation filter: narrow by current status when multiple items share the same title/task_id."
-          },
-          "created_order": {
-            "type": "number",
-            "description": "Disambiguation filter: pick the Nth oldest match (1 = oldest, 2 = second oldest, etc.) when multiple items share the same title/task_id."
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-list-update.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_list_remove",
-      "description": "Remove a task from the Task Queue. Identifies the task by work item ID, task ID, task name, or title. When multiple items match, use the disambiguation fields (priority_tier, status, created_order) to narrow down.",
-      "category": "tasks",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "work_item_id": {
-            "type": "string",
-            "description": "Direct work item ID (most precise selector)"
-          },
-          "task_id": {
-            "type": "string",
-            "description": "Task definition ID to find the work item for"
-          },
-          "task_name": {
-            "type": "string",
-            "description": "Task name/title to search for (case-insensitive exact match)"
-          },
-          "title": {
-            "type": "string",
-            "description": "Work item title to search for (case-insensitive exact match)"
-          },
-          "priority_tier": {
-            "type": "number",
-            "description": "Disambiguator: filter by priority tier (0 = high, 1 = medium, 2 = low)"
-          },
-          "status": {
-            "type": "string",
-            "enum": [
-              "queued",
-              "running",
-              "awaiting_review",
-              "failed",
-              "cancelled"
-            ],
-            "description": "Disambiguator: filter by work item status"
-          },
-          "created_order": {
-            "type": "number",
-            "description": "Disambiguator: 1-indexed creation order among matches (1 = oldest, 2 = second oldest, etc.)"
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-list-remove.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "task_queue_run",
-      "description": "Run a task from the Task Queue in the background. Use this when the user says \"run this task\", \"execute this task\", \"start this task\", or wants to kick off a queued work item. The task runs asynchronously \u2014 the user can continue chatting while it executes. Required tool permissions are auto-approved since the user is explicitly requesting execution.",
-      "category": "tasks",
-      "risk": "medium",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "work_item_id": {
-            "type": "string",
-            "description": "Direct work item ID (most precise selector)"
-          },
-          "task_name": {
-            "type": "string",
-            "description": "Task name/title to search for (case-insensitive substring match)"
-          },
-          "title": {
-            "type": "string",
-            "description": "Work item title to search for (case-insensitive substring match)"
-          },
-          "activity": {
-            "type": "string",
-            "description": "Brief non-technical explanation of why this tool is being called"
-          }
-        }
-      },
-      "executor": "tools/task-queue-run.ts",
-      "execution_target": "host"
-    }
-  ]
-}