vellum 0.2.13 → 0.3.2

package/src/config/bundled-skills/public-ingress/SKILL.md

@@ -1,183 +0,0 @@
----
-name: "Public Ingress"
-description: "Set up and manage ngrok-based public ingress for webhooks and OAuth callbacks via ingress.publicBaseUrl"
-user-invocable: true
-metadata: {"vellum": {"emoji": "🌍"}}
----
-
-You are setting up and managing a public ingress tunnel so that external services (Telegram webhooks, OAuth callbacks, etc.) can reach the local Vellum gateway. This skill uses ngrok to create a secure tunnel and persists the public URL as `ingress.publicBaseUrl`.
-
-## Overview
-
-The Vellum gateway listens locally and needs a publicly reachable URL for:
-- Telegram webhook delivery
-- Google/Slack OAuth redirect callbacks
-- Any other inbound webhook traffic
-
-This skill installs ngrok, configures authentication, starts a tunnel, discovers the public URL, and saves it to the assistant's ingress config.
-
-## Step 1: Check Current Ingress Status
-
-First, check whether ingress is already configured:
-
-```bash
-vellum config get ingress.publicBaseUrl
-```
-
-Also determine the local gateway target. The gateway listens on `http://127.0.0.1:${GATEWAY_PORT:-7830}` by default.
-
-If `ingress.publicBaseUrl` is already set and the tunnel is running (check via `curl -s http://127.0.0.1:4040/api/tunnels`), tell the user the current status and ask if they want to reconfigure or if this is sufficient.
-
-## Step 2: Install ngrok
-
-Check if ngrok is installed:
-
-```bash
-ngrok version
-```
-
-If not installed, install it:
-
-**macOS (Homebrew):**
-```bash
-brew install ngrok/ngrok/ngrok
-```
-
-**Linux (snap):**
-```bash
-sudo snap install ngrok
-```
-
-**Linux (apt — alternative):**
-```bash
-curl -sSL https://ngrok-agent.s3.amazonaws.com/ngrok.asc | sudo tee /etc/apt/trusted.gpg.d/ngrok.asc >/dev/null
-echo "deb https://ngrok-agent.s3.amazonaws.com buster main" | sudo tee /etc/apt/sources.list.d/ngrok.list
-sudo apt update && sudo apt install ngrok
-```
-
-After installation, verify with `ngrok version`.
-
-## Step 3: Authenticate ngrok
-
-Check if ngrok already has an auth token configured:
-
-```bash
-ngrok config check
-```
-
-If not authenticated:
-
-1. Tell the user: "You need an ngrok account to create tunnels. If you don't have one, sign up at https://dashboard.ngrok.com/signup — it's free."
-2. Once they have an account, ask them to paste their auth token directly in chat. They can find it at https://dashboard.ngrok.com/get-started/your-authtoken.
-
-3. Once the user provides the token, configure ngrok with it immediately:
-```bash
-ngrok config add-authtoken <token>
-```
-
-Verify authentication succeeded by checking `ngrok config check` again.
-
-## Step 4: Start the Tunnel
-
-Before starting, check for an existing ngrok process to avoid duplicates:
-
-```bash
-curl -s http://127.0.0.1:4040/api/tunnels 2>/dev/null
-```
-
-If a tunnel is already running, check whether it points to the correct local target. If so, skip to Step 5. If it points elsewhere, stop it first:
-
-```bash
-pkill -f ngrok || true
-sleep 1
-```
-
-Start ngrok in the background, tunneling to the local gateway:
-
-```bash
-nohup ngrok http http://127.0.0.1:${GATEWAY_PORT:-7830} --log=stdout > /tmp/ngrok.log 2>&1 &
-echo $! > /tmp/ngrok.pid
-```
-
-Wait a few seconds for the tunnel to establish:
-
-```bash
-sleep 3
-```
-
-## Step 5: Discover the Public URL
-
-Query the ngrok local API for the tunnel's public URL:
-
-```bash
-curl -s http://127.0.0.1:4040/api/tunnels | python3 -c "
-import sys, json
-data = json.load(sys.stdin)
-tunnels = data.get('tunnels', [])
-for t in tunnels:
-    url = t.get('public_url', '')
-    if url.startswith('https://'):
-        print(url)
-        sys.exit(0)
-for t in tunnels:
-    url = t.get('public_url', '')
-    if url:
-        print(url)
-        sys.exit(0)
-print('ERROR: no tunnel found')
-sys.exit(1)
-"
-```
-
-If no tunnel is found, check `/tmp/ngrok.log` for errors and report them to the user.
-
-## Step 6: Persist the Ingress Setting
-
-Save the discovered public URL and enable ingress:
-
-```bash
-vellum config set ingress.publicBaseUrl "<public-url>"
-vellum config set ingress.enabled true
-```
-
-Verify it was saved:
-
-```bash
-vellum config get ingress.publicBaseUrl
-vellum config get ingress.enabled
-```
-
-## Step 7: Report Completion
-
-Summarize the setup:
-
-- **Public URL:** `<the-url>` (this is your `ingress.publicBaseUrl`)
-- **Local gateway:** `http://127.0.0.1:${GATEWAY_PORT:-7830}`
-- **ngrok dashboard:** http://127.0.0.1:4040
-
-Provide useful follow-up commands:
-
-- **Check tunnel status:** `curl -s http://127.0.0.1:4040/api/tunnels | python3 -c "import sys,json; [print(t['public_url']) for t in json.load(sys.stdin)['tunnels']]"`
-- **View ngrok logs:** `cat /tmp/ngrok.log`
-- **Restart tunnel:** `pkill -f ngrok; sleep 1; nohup ngrok http http://127.0.0.1:${GATEWAY_PORT:-7830} --log=stdout > /tmp/ngrok.log 2>&1 &`
-- **Stop tunnel:** `pkill -f ngrok`
-- **Rotate URL:** Stop and restart ngrok (free tier assigns a new URL each time; update `ingress.publicBaseUrl` afterward)
-
-**Important:** On ngrok's free tier, the public URL changes every time the tunnel restarts. After restarting, re-run this skill or manually update `ingress.publicBaseUrl` and any registered webhooks (e.g., Telegram).
-
-## Troubleshooting
-
-### ngrok not installed
-Run the install commands in Step 2. On macOS, make sure Homebrew is installed first (`brew --version`).
-
-### Auth token invalid or expired
-Sign in to https://dashboard.ngrok.com, copy a fresh token from the "Your Authtoken" page, and re-run Step 3.
-
-### ngrok API (port 4040) not responding
-The ngrok process may not be running. Check with `ps aux | grep ngrok`. If not running, start it per Step 4. If running but 4040 is unresponsive, check `/tmp/ngrok.log` for errors.
-
-### Gateway not reachable on local target
-Ensure the Vellum gateway is running on `http://127.0.0.1:${GATEWAY_PORT:-7830}`. Check with `curl -s http://127.0.0.1:${GATEWAY_PORT:-7830}/health`. If not running, start the assistant daemon first.
-
-### "Too many connections" or tunnel limit errors
-ngrok's free tier allows one tunnel at a time. Stop any other ngrok tunnels before starting a new one.

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

@@ -1,20 +0,0 @@
----
-name: "Reminder"
-description: "One-time time-based reminders that fire at a specific future time"
-metadata: {"vellum": {"emoji": "🔔"}}
----
-
-Create, list, and cancel one-time reminders. Reminders fire at a specific future time and either notify the user or execute a message through the assistant.
-
-## Modes
-
-- **notify** (default) — shows a notification to the user when the reminder fires
-- **execute** — sends the reminder message to a background assistant conversation for autonomous handling
-
-## Usage Notes
-
-- Use reminders ONLY for time-triggered notifications (e.g. "remind me at 3pm", "remind me in 2 hours").
-- For recurring automation, use schedules instead.
-- For task tracking ("add to my tasks", "add to my queue"), use task_list_add instead.
-- `fire_at` must be a strict ISO 8601 timestamp with timezone offset or Z (e.g. `2025-03-15T09:00:00-05:00` or `2025-03-15T09:00:00Z`). Ambiguous timestamps without timezone info will be rejected.
-- `label` is a short human-readable summary shown in the notification.

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

@@ -1,67 +0,0 @@
-{
-  "version": 1,
-  "tools": [
-    {
-      "name": "reminder_create",
-      "description": "Create a one-time time-based reminder. Reminders fire at a specific future time and either notify the user or execute a message through the assistant. Use this ONLY when the user wants a time-triggered notification (e.g. \"remind me at 3pm\", \"remind me in 2 hours\"). Do NOT use this for \"add to my tasks\" or \"add to my queue\" — use task_list_add for those requests.",
-      "category": "reminder",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "fire_at": {
-            "type": "string",
-            "description": "ISO 8601 timestamp for when the reminder should fire"
-          },
-          "label": {
-            "type": "string",
-            "description": "Human-readable label"
-          },
-          "message": {
-            "type": "string",
-            "description": "Content shown in notification (notify) or sent to agent (execute)"
-          },
-          "mode": {
-            "type": "string",
-            "enum": ["notify", "execute"],
-            "description": "How the reminder fires. Defaults to notify."
-          }
-        },
-        "required": ["fire_at", "label", "message"]
-      },
-      "executor": "tools/reminder-create.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "reminder_list",
-      "description": "List all reminders and their current status.",
-      "category": "reminder",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {},
-        "required": []
-      },
-      "executor": "tools/reminder-list.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "reminder_cancel",
-      "description": "Cancel a pending reminder by ID.",
-      "category": "reminder",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "reminder_id": {
-            "type": "string",
-            "description": "Reminder ID to cancel"
-          }
-        },
-        "required": ["reminder_id"]
-      },
-      "executor": "tools/reminder-cancel.ts",
-      "execution_target": "host"
-    }
-  ]
-}

package/src/config/bundled-skills/reminder/tools/reminder-cancel.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeReminderCancel } from '../../../../tools/reminder/reminder.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  _context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeReminderCancel(input);
-}

package/src/config/bundled-skills/reminder/tools/reminder-create.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeReminderCreate } from '../../../../tools/reminder/reminder.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  _context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeReminderCreate(input);
-}

package/src/config/bundled-skills/reminder/tools/reminder-list.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeReminderList } from '../../../../tools/reminder/reminder.js';
-
-export async function run(
-  _input: Record<string, unknown>,
-  _context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeReminderList();
-}

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

@@ -1,74 +0,0 @@
----
-name: "Schedule"
-description: "Recurring automation that dispatches messages on a cron or RRULE schedule"
-metadata: {"vellum": {"emoji": "\ud83d\udcc5"}}
----
-
-Manage recurring scheduled automations. Each schedule has an expression (cron or RRULE) that defines when it fires, and a message that gets dispatched to the assistant at trigger time.
-
-## Schedule Syntax
-
-### Cron
-
-Standard 5-field cron syntax: `minute hour day-of-month month day-of-week`
-
-| Field         | Values        | Special characters |
-|---------------|---------------|--------------------|
-| Minute        | 0-59          | , - * /            |
-| Hour          | 0-23          | , - * /            |
-| Day of month  | 1-31          | , - * /            |
-| Month         | 1-12          | , - * /            |
-| Day of week   | 0-7 (0,7=Sun) | , - * /            |
-
-Examples:
-- `0 9 * * 1-5` — weekdays at 9:00 AM
-- `30 8 * * *` — every day at 8:30 AM
-- `0 */2 * * *` — every 2 hours
-- `0 9 1 * *` — first of every month at 9:00 AM
-
-### RRULE (RFC 5545)
-
-iCalendar recurrence rules for complex patterns. Must include a DTSTART line.
-
-Supported lines (all expressions must include DTSTART + at least one RRULE or RDATE):
-
-| Line | Purpose |
-|------|---------|
-| `DTSTART` | Start date/time anchor (required) |
-| `RRULE:` | Recurrence rule (multiple lines = union of occurrences) |
-| `RDATE` | Add one-off dates not covered by the pattern |
-| `EXDATE` | Exclude specific dates from the set |
-| `EXRULE` | Exclude an entire recurring series |
-
-Exclusions (EXDATE, EXRULE) always take precedence over inclusions (RRULE, RDATE).
-
-#### Basic examples
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=DAILY` — every day at 9:00 AM UTC
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR` — Mon/Wed/Fri at 9:00 AM UTC
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=MONTHLY;BYMONTHDAY=1,15` — 1st and 15th of each month
-
-#### Bounded recurrence
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=DAILY;COUNT=30` — daily for 30 occurrences then stop
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=WEEKLY;BYDAY=MO;UNTIL=20250331T235959Z` — every Monday until end of March
-
-#### Set construct examples
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=WEEKLY;BYDAY=MO,WE,FR\nEXDATE:20250120T090000Z` — Mon/Wed/Fri except Jan 20
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=DAILY\nEXRULE:FREQ=WEEKLY;BYDAY=SA,SU` — every weekday (daily minus weekends)
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=MONTHLY;BYMONTHDAY=1\nRDATE:20250704T090000Z` — 1st of each month plus July 4th
-- `DTSTART:20250101T090000Z\nRRULE:FREQ=WEEKLY;BYDAY=TU\nRRULE:FREQ=WEEKLY;BYDAY=TH` — union of Tuesdays and Thursdays
-
-## Tool Input
-
-Use `syntax` + `expression` to specify the schedule type explicitly, or just `expression` to auto-detect. The legacy `cron_expression` field is still accepted as a cron alias.
-
-## Lifecycle
-
-1. Create a schedule with a name, expression, and message.
-2. At each trigger time, the message is dispatched to the assistant as if the user sent it.
-3. Schedules can be enabled/disabled, updated, or deleted.
-
-## Tips
-
-- Only use `schedule_create` when the user explicitly wants recurring automation (e.g. "every day at 9am", "weekly on Mondays"). For one-time tasks, use the task list instead.
-- Timezones default to the system timezone if omitted. Use IANA timezone identifiers (e.g. "America/Los_Angeles").
-- Prefer RRULE for complex patterns that cron cannot express (e.g. "every other Tuesday", "last weekday of the month").

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

@@ -1,135 +0,0 @@
-{
-  "version": 1,
-  "tools": [
-    {
-      "name": "schedule_create",
-      "description": "Create a recurring scheduled automation that sends a message at a cron or RRULE interval. ONLY use this when the user explicitly wants something to run on a schedule (e.g. \"every day at 9am\", \"weekly on Mondays\", \"every hour\"). Do NOT use this for \"add to my tasks\" or \"add to my queue\" — use task_list_add for those requests instead.",
-      "category": "schedule",
-      "risk": "medium",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "name": {
-            "type": "string",
-            "description": "A human-readable name for the scheduled task"
-          },
-          "syntax": {
-            "type": "string",
-            "enum": ["cron", "rrule"],
-            "description": "Schedule syntax type. Auto-detected if omitted."
-          },
-          "expression": {
-            "type": "string",
-            "description": "Canonical schedule expression (cron or RRULE). Preferred over cron_expression."
-          },
-          "cron_expression": {
-            "type": "string",
-            "description": "Deprecated alias for expression with cron syntax. Use expression + syntax instead."
-          },
-          "timezone": {
-            "type": "string",
-            "description": "IANA timezone (e.g. \"America/Los_Angeles\"). Defaults to system timezone if omitted."
-          },
-          "message": {
-            "type": "string",
-            "description": "The message to send to the assistant when the schedule triggers"
-          },
-          "enabled": {
-            "type": "boolean",
-            "description": "Whether the job is enabled immediately. Defaults to true."
-          }
-        },
-        "required": ["name", "message"]
-      },
-      "executor": "tools/schedule-create.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "schedule_list",
-      "description": "List recurring scheduled automations (cron jobs or RRULE schedules), or show details and recent runs for a specific one. For the user's task queue, use task_list_show instead.",
-      "category": "schedule",
-      "risk": "low",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "enabled_only": {
-            "type": "boolean",
-            "description": "When true, only show enabled jobs. Defaults to false."
-          },
-          "job_id": {
-            "type": "string",
-            "description": "If provided, show detailed info and recent runs for this specific job."
-          }
-        },
-        "required": []
-      },
-      "executor": "tools/schedule-list.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "schedule_update",
-      "description": "Update an existing recurring scheduled automation (expression, syntax, message, name, or enabled state)",
-      "category": "schedule",
-      "risk": "medium",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "job_id": {
-            "type": "string",
-            "description": "The ID of the schedule to update"
-          },
-          "name": {
-            "type": "string",
-            "description": "New name for the job"
-          },
-          "syntax": {
-            "type": "string",
-            "enum": ["cron", "rrule"],
-            "description": "Schedule syntax type. Auto-detected if omitted."
-          },
-          "expression": {
-            "type": "string",
-            "description": "New schedule expression (cron or RRULE). Preferred over cron_expression."
-          },
-          "cron_expression": {
-            "type": "string",
-            "description": "Deprecated alias for expression with cron syntax. Use expression + syntax instead."
-          },
-          "timezone": {
-            "type": "string",
-            "description": "New IANA timezone"
-          },
-          "message": {
-            "type": "string",
-            "description": "New message to send when triggered"
-          },
-          "enabled": {
-            "type": "boolean",
-            "description": "Enable or disable the job"
-          }
-        },
-        "required": ["job_id"]
-      },
-      "executor": "tools/schedule-update.ts",
-      "execution_target": "host"
-    },
-    {
-      "name": "schedule_delete",
-      "description": "Delete a recurring scheduled automation and all its run history",
-      "category": "schedule",
-      "risk": "high",
-      "input_schema": {
-        "type": "object",
-        "properties": {
-          "job_id": {
-            "type": "string",
-            "description": "The ID of the schedule to delete"
-          }
-        },
-        "required": ["job_id"]
-      },
-      "executor": "tools/schedule-delete.ts",
-      "execution_target": "host"
-    }
-  ]
-}

package/src/config/bundled-skills/schedule/tools/schedule-create.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeScheduleCreate } from '../../../../tools/schedule/create.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeScheduleCreate(input, context);
-}

package/src/config/bundled-skills/schedule/tools/schedule-delete.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeScheduleDelete } from '../../../../tools/schedule/delete.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeScheduleDelete(input, context);
-}

package/src/config/bundled-skills/schedule/tools/schedule-list.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeScheduleList } from '../../../../tools/schedule/list.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeScheduleList(input, context);
-}

package/src/config/bundled-skills/schedule/tools/schedule-update.ts

@@ -1,9 +0,0 @@
-import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
-import { executeScheduleUpdate } from '../../../../tools/schedule/update.js';
-
-export async function run(
-  input: Record<string, unknown>,
-  context: ToolContext,
-): Promise<ToolExecutionResult> {
-  return executeScheduleUpdate(input, context);
-}

package/src/config/bundled-skills/self-upgrade/SKILL.md

@@ -1,68 +0,0 @@
----
-name: "Self Upgrade"
-description: "Upgrade vellum to the latest version, restart the daemon, and restart the gateway"
-user-invocable: true
-metadata: {"vellum": {"emoji": "⬆️"}}
----
-
-You are performing a self-upgrade of the Vellum assistant. Follow these steps **in order**. Use the `bash` tool to run each command. Confirm each step succeeds before moving to the next.
-
-## Step 1: Record the current version
-
-```bash
-vellum --version
-```
-
-Save this value to report later.
-
-## Step 2: Install the latest vellum
-
-```bash
-bun install -g vellum@latest
-```
-
-After updating, verify the new version:
-
-```bash
-vellum --version
-```
-
-## Step 3: Restart the gateway
-
-If a gateway process is running, restart it so it picks up any protocol or dependency changes from the new version:
-
-```bash
-pgrep -f 'vellum-gateway|gateway/src/index.ts' || echo "No gateway process found"
-```
-
-If a gateway PID is found, send it SIGTERM so it drains gracefully:
-
-```bash
-pkill -TERM -f 'vellum-gateway|gateway/src/index.ts'
-```
-
-Then start the gateway again using whatever method the user's deployment uses (e.g. `bun run gateway/src/index.ts`, a systemd service, or a container orchestrator). If you are unsure how the gateway is deployed, ask the user.
-
-## Step 4: Restart the daemon
-
-Use `vellum daemon restart` which stops the old daemon and starts a new one from the updated binary in a single command:
-
-```bash
-vellum daemon restart
-```
-
-Verify it is running:
-
-```bash
-vellum daemon status
-```
-
-**Important:** This is the last step because the current daemon process is the one executing this conversation. After the restart, the new daemon takes over and this session ends gracefully.
-
-## After Upgrade
-
-Report back to the user with:
-- The previous and new vellum version
-- Daemon status (running, PID)
-- Gateway status (restarted or not found)
-- Any errors encountered during the process