vellum 0.2.1 → 0.2.2

package/src/config/bundled-skills/contacts/tools/contact-merge.ts

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

package/src/config/bundled-skills/contacts/tools/contact-search.ts

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

package/src/config/bundled-skills/contacts/tools/contact-upsert.ts

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

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

@@ -0,0 +1,18 @@
+---
+name: "Document"
+description: "Document creation and editing for UI surfaces"
+metadata: {"vellum": {"emoji": "📄"}}
+---
+
+Create and edit long-form documents using the built-in rich text editor. Documents open in workspace mode with chat docked to the side.
+
+## Tools
+
+- **document_create** — Opens a new document editor with an optional title and initial Markdown content. Returns a `surface_id` for subsequent updates.
+- **document_update** — Updates content in an open document editor by `surface_id`. Supports `replace` (overwrite) and `append` (add to end) modes.
+
+## Usage Notes
+
+- Use `document_create` when the user asks to write a blog post, article, or any long-form content.
+- After creating a document, use `document_update` with the returned `surface_id` to stream or edit content.
+- The `mode` parameter on `document_update` defaults to `append`.

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

@@ -0,0 +1,53 @@
+{
+  "version": 1,
+  "tools": [
+    {
+      "name": "document_create",
+      "description": "Create a new long-form document with a rich text editor. Use this when the user asks to write a blog post, article, or any long-form content. The editor opens in workspace mode with chat docked to the side.",
+      "category": "document",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "title": {
+            "type": "string",
+            "description": "Initial title for the document (optional, can be updated later)"
+          },
+          "initial_content": {
+            "type": "string",
+            "description": "Initial Markdown content to populate the editor (optional)"
+          }
+        }
+      },
+      "executor": "tools/document-create.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "document_update",
+      "description": "Update content in an open document editor. Use this to stream generated content or apply edits.",
+      "category": "document",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "surface_id": {
+            "type": "string",
+            "description": "The ID of the document surface to update"
+          },
+          "content": {
+            "type": "string",
+            "description": "Markdown content to set or append"
+          },
+          "mode": {
+            "type": "string",
+            "enum": ["replace", "append"],
+            "description": "Whether to replace all content or append to the end. Defaults to append."
+          }
+        },
+        "required": ["surface_id", "content"]
+      },
+      "executor": "tools/document-update.ts",
+      "execution_target": "host"
+    }
+  ]
+}

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

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

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

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

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

@@ -7,33 +7,23 @@ metadata: {"vellum": {"emoji": "\uD83C\uDF55"}}
 
 You can order food from DoorDash for the user using the `vellum doordash` CLI.
 
+## CLI Setup
+
+**IMPORTANT: Always use `host_bash` (not `bash`) for all `vellum doordash` commands.** The DoorDash CLI needs host access for Chrome CDP, session cookies, and the `vellum` binary — none of which are available inside the sandbox.
+
+`vellum doordash` is a built-in subcommand of the Vellum assistant CLI — it is NOT a separate tool you need to find or install. It should already be on your PATH. If `vellum` is not found, prepend `PATH="$HOME/.local/bin:$PATH"` to the command. Do NOT search for the binary, inspect wrapper scripts, or try to discover how the CLI works. Just run the commands as documented below.
+
 ## Task Progress Widget
 
-When executing a food ordering flow, show live progress using the `task_progress` card template. Before starting, call `ui_show` with:
-```json
-{
-  "surface_type": "card",
-  "template": "task_progress",
-  "templateData": {
-    "title": "Ordering from DoorDash",
-    "status": "in_progress",
-    "steps": [
-      { "label": "Check session", "status": "in_progress" },
-      { "label": "Search restaurants", "status": "pending" },
-      { "label": "Browse menu", "status": "pending" },
-      { "label": "Add to cart", "status": "pending" },
-      { "label": "Place order", "status": "pending" }
-    ]
-  }
-}
-```
-As each step completes, call `ui_update` with the same surface ID to update step statuses. Add `detail` to completed steps (e.g. `"detail": "Found Andiamo's"`). Adapt the steps to the actual flow (e.g. skip "Search restaurants" if the user named a specific store).
+A task progress card is shown automatically when you run your first `vellum doordash` command. Its surface ID is `doordash-progress`. As each step completes, call `ui_update` with surface ID `doordash-progress` to update step statuses. Update `data.templateData.steps` — set completed steps to `"status": "completed"` with a `"detail"` string, the current step to `"status": "in_progress"`, and future steps to `"status": "pending"`. Adapt the steps to the actual flow (e.g. skip "Search restaurants" if the user named a specific store).
 
 ## Typical Flow
 
 When the user asks you to order food (e.g. "Order pizza from Andiamo's"):
 
-1. **Check session** — run `vellum doordash status --json`. If `loggedIn` is false or the session is expired, tell the user: "I need to capture your DoorDash session. A separate Chrome window will open — your existing Chrome and tabs are not affected. Please sign in to DoorDash when it opens, and I'll take it from there." Then run `vellum doordash refresh --json`. This starts a Ride Shotgun learn session that records your login and auto-stops once it detects you've signed in. The session is imported automatically. **This command blocks until login is complete — just wait for it.**
+1. **Check session** — run `vellum doordash status --json`. If `loggedIn` is false or the session is expired, tell the user: "A Chrome window will open to the DoorDash login page. Please sign in there — I'll detect your login automatically and minimize the window." Then run `vellum doordash refresh --json`. This starts a Ride Shotgun learn session that records your login and auto-stops once it detects you've signed in. The session is imported automatically. **This command blocks until login is complete — just wait for it.**
+
+   Keep the DoorDash Chrome window open in the background — it's needed for API requests.
 
 2. **Search** — run `vellum doordash search "<query>" --json` to find matching restaurants. Present the top results to the user with name, rating, and delivery info. If the user named a specific restaurant, pick the best match. If ambiguous, ask.
 
@@ -41,9 +31,14 @@ When the user asks you to order food (e.g. "Order pizza from Andiamo's"):
 
 3b. **Search within a retail store** — for convenience/pharmacy stores, run `vellum doordash store-search <storeId> "<query>" --json` to find specific products. This returns items with IDs, prices, and menuIds that can be added to cart directly.
 
-4. **Get item details** (if needed) — run `vellum doordash item <storeId> <itemId> --json` to see options/customizations. If the item has required options (like size or toppings), ask the user or pick sensible defaults.
+4. **Get item details** (if needed) — run `vellum doordash item <storeId> <itemId> --json` to see options/customizations. The response includes:
+   - `options`: each option group has `minSelections`/`maxSelections` indicating how many choices are required
+   - Each choice has `unitAmount` (price impact in cents), `defaultQuantity`, and possibly `nestedOptions` (sub-choices like milk type within a size selection)
+   - `specialInstructionsConfig`: whether special instructions are accepted, max length, and placeholder text
+
+   If the item has required options (like size or toppings), construct the `nestedOptions` JSON from the option/choice IDs and pass it via `--options`. Ask the user for preferences or pick sensible defaults.
 
-5. **Add to cart** — run `vellum doordash cart add --store-id <id> --menu-id <id> --item-id <id> --item-name "<name>" --unit-price <cents> --json`. For subsequent items at the same store, pass `--cart-id <id>` from the first add response.
+5. **Add to cart** — run `vellum doordash cart add --store-id <id> --menu-id <id> --item-id <id> --item-name "<name>" --unit-price <cents> [--options '<json>'] [--special-instructions "<text>"] --json`. For subsequent items at the same store, pass `--cart-id <id>` from the first add response. Use `--special-instructions` for requests like "extra hot", "no ice", etc. Use `--options` to pass customization choices (see Customization Options below).
 
 6. **Review cart** — run `vellum doordash cart view <cartId> --json` and show the user what's in their cart with prices. Ask if they want to add anything else or proceed.
 
@@ -61,6 +56,68 @@ When the user asks you to order food (e.g. "Order pizza from Andiamo's"):
 - **Show prices.** Always show prices when presenting items or the cart summary.
 - **Use `--json` flag** on all commands for reliable parsing.
 - **Do NOT use the browser skill.** All DoorDash interaction goes through the CLI, not browser automation.
+- **Rate limiting.** DoorDash rate-limits rapid sequential requests. When adding multiple items (e.g. a team order), wait 8–10 seconds between `cart add` calls. If you get a 403 error, wait 15–20 seconds and retry. For large orders (5+ items), consider running `vellum doordash refresh --json` midway through if you hit repeated 403s.
+- **Special instructions are unreliable.** Some merchants disable special instructions entirely. Always prefer `--options` for customizations (size, milk type, etc.). Only use `--special-instructions` for free-text requests that aren't covered by the item's option groups. If the merchant rejects special instructions, drop them and proceed without.
+- **Customization fallback.** If `cart add` with `--options` fails, or if the item details show options that are hard to construct (deeply nested, unusual format), proactively offer to use `cart learn` so the user can customize the item visually in the browser. Don't silently drop customizations — tell the user what happened and offer alternatives.
+- **Always-allow tip.** At the start of an ordering flow, suggest the user enable "always allow" for `vellum doordash` commands: "Tip: You can type 'a' to always allow `vellum doordash` commands for this session so you won't be prompted each time."
+- **Error attribution.** When errors occur, assume it's more likely a bug in our query/parsing than a DoorDash API change. Suggest running `vellum doordash record` to capture fresh queries before assuming the schema changed.
+
+## Customization Options
+
+Many items (especially coffee, boba, sandwiches) have required customization options like size, milk type, or toppings. Here's how to handle them:
+
+### Constructing nestedOptions JSON
+
+1. Run `vellum doordash item <storeId> <itemId> --json` to get the item's option groups
+2. Each option group has `id`, `name`, `required`, `minSelections`, `maxSelections`, and `choices`
+3. Build a JSON array of selections matching the DoorDash format:
+
+```json
+[
+  {
+    "optionId": "<option-group-id>",
+    "optionChoiceId": "<choice-id>",
+    "quantity": 1,
+    "nestedOptions": []
+  }
+]
+```
+
+For choices with nested sub-options (e.g., selecting "Oat Milk" under the "Milk" option within a size), add them to the `nestedOptions` array of the parent choice.
+
+4. Pass the JSON string to `cart add --options '<json>'`
+
+### Special Instructions
+
+Use `--special-instructions` on `cart add` for free-text requests like "extra hot", "no ice", "light foam". The `item` command response includes `specialInstructionsConfig` with the max length and whether instructions are supported.
+
+**Warning:** Some merchants disable special instructions entirely. If `specialInstructionsConfig.isEnabled` is false, or if the add-to-cart call returns an error about special requests, drop the instructions and retry without them. Always prefer `--options` for customizations — special instructions are a last resort for requests not covered by the item's option groups.
+
+### Learning Customizations via Ride Shotgun
+
+For complex items where constructing the JSON manually is difficult, use `cart learn`:
+
+1. Run `vellum doordash cart learn --json`
+2. A Chrome window opens — navigate to the item, customize it visually, and click "Add to Cart"
+3. The command auto-detects the `updateCartItem` operation and extracts the exact `nestedOptions` and `specialInstructions`
+4. Use the extracted options directly with `cart add --options '<json>'`
+
+You can also extract options from an existing recording with `vellum doordash inspect <recordingId> --extract-options --json`.
+
+### Coffee Order Example
+
+**User**: "Order a large oat milk latte with an extra shot from Blue Bottle"
+
+1. `vellum doordash search "Blue Bottle" --json` -> finds store
+2. `vellum doordash menu <storeId> --json` -> finds "Latte" item
+3. `vellum doordash item <storeId> <latteItemId> --json` -> returns options:
+   - Size (required, min:1, max:1): Small (id:101), Medium (id:102), Large (id:103, +$1.00)
+   - Milk (required, min:1, max:1): Whole (id:201), Oat (id:202, +$0.70), Almond (id:203, +$0.70)
+   - Extras (optional, min:0, max:5): Extra Shot (id:301, +$0.90), Vanilla Syrup (id:302, +$0.60)
+4. Construct options JSON and add to cart:
+```
+vellum doordash cart add --store-id <id> --menu-id <id> --item-id <id> --item-name "Latte" --unit-price 550 --options '[{"optionId":"size-group-id","optionChoiceId":"103","quantity":1,"nestedOptions":[]},{"optionId":"milk-group-id","optionChoiceId":"202","quantity":1,"nestedOptions":[]},{"optionId":"extras-group-id","optionChoiceId":"301","quantity":1,"nestedOptions":[]}]' --special-instructions "Extra hot" --json
+```
 
 ## Command Reference
 
@@ -73,10 +130,12 @@ vellum doordash search "<query>" --json    # Search restaurants
 vellum doordash menu <storeId> --json      # Get store menu (auto-detects retail stores)
 vellum doordash store-search <storeId> "<query>" --json  # Search items within a convenience/pharmacy store
 vellum doordash item <storeId> <itemId> --json  # Get item details + options
-vellum doordash cart add --store-id <id> --menu-id <id> --item-id <id> --item-name "<name>" --unit-price <cents> [--quantity <n>] [--cart-id <id>] --json
+vellum doordash cart add --store-id <id> --menu-id <id> --item-id <id> --item-name "<name>" --unit-price <cents> [--quantity <n>] [--cart-id <id>] [--options '<json>'] [--special-instructions "<text>"] --json
 vellum doordash cart remove --cart-id <id> --item-id <orderItemId> --json
 vellum doordash cart view <cartId> --json
 vellum doordash cart list [--store-id <id>] --json
+vellum doordash cart learn --json                 # Learn customization options by recording browser interaction
+vellum doordash inspect <recordingId> --extract-options --json  # Extract nestedOptions from a recording
 vellum doordash checkout <cartId> [--address-id <id>] --json
 vellum doordash payment-methods --json     # List saved payment methods
 vellum doordash order place --cart-id <id> --store-id <id> --total <cents> [--tip <cents>] [--delivery-option <type>] [--dropoff-option <id>] [--payment-uuid <uuid>] --json

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

@@ -0,0 +1,32 @@
+---
+name: "Followups"
+description: "Track sent messages awaiting responses across communication channels"
+metadata: {"vellum": {"emoji": "\ud83d\udce8"}}
+---
+
+Track messages sent on external channels (email, Slack, WhatsApp, etc.) that are awaiting a response.
+
+## Lifecycle
+
+Each follow-up moves through these states:
+
+- **pending** -- waiting for a response
+- **overdue** -- past the expected response deadline with no reply
+- **nudged** -- a reminder was sent after becoming overdue
+- **resolved** -- a response was received or the follow-up was manually closed
+
+## Auto-Deadline
+
+When `expected_response_hours` is set, the follow-up automatically becomes overdue after that window. If a `contact_id` is provided, the contact's importance score can inform grace period decisions.
+
+## Resolution
+
+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)
+
+## Tips
+
+- Use `followup_list` with `overdue_only: true` to find conversations that need attention.
+- Attach a `reminder_schedule_id` to link a recurring reminder schedule to a follow-up.
+- Filter by channel, status, or contact to narrow results.

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

@@ -0,0 +1,100 @@
+{
+  "version": 1,
+  "tools": [
+    {
+      "name": "followup_create",
+      "description": "Create a follow-up tracker for a sent message. Tracks conversations awaiting a response across channels (email, Slack, WhatsApp, etc.).",
+      "category": "followups",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "channel": {
+            "type": "string",
+            "description": "Communication channel (e.g. email, slack, whatsapp)"
+          },
+          "thread_id": {
+            "type": "string",
+            "description": "External thread or conversation identifier on that channel"
+          },
+          "contact_id": {
+            "type": "string",
+            "description": "Optional contact ID from the contact graph. Used for grace period context."
+          },
+          "expected_response_hours": {
+            "type": "number",
+            "description": "Hours to wait for a response before marking as overdue. If omitted, no deadline is set."
+          },
+          "reminder_schedule_id": {
+            "type": "string",
+            "description": "Optional recurrence schedule ID to fire a reminder when overdue"
+          },
+          "reminder_cron_id": {
+            "type": "string",
+            "description": "Deprecated alias for reminder_schedule_id. Use reminder_schedule_id instead."
+          }
+        },
+        "required": ["channel", "thread_id"]
+      },
+      "executor": "tools/followup-create.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "followup_list",
+      "description": "List follow-ups with optional filters by status, channel, or contact. Can also show only overdue follow-ups.",
+      "category": "followups",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "status": {
+            "type": "string",
+            "enum": ["pending", "resolved", "overdue", "nudged"],
+            "description": "Filter by status (pending, resolved, overdue, nudged)"
+          },
+          "channel": {
+            "type": "string",
+            "description": "Filter by communication channel (e.g. email, slack)"
+          },
+          "contact_id": {
+            "type": "string",
+            "description": "Filter by contact ID"
+          },
+          "overdue_only": {
+            "type": "boolean",
+            "description": "When true, return only pending follow-ups past their expected response deadline"
+          }
+        },
+        "required": []
+      },
+      "executor": "tools/followup-list.ts",
+      "execution_target": "host"
+    },
+    {
+      "name": "followup_resolve",
+      "description": "Manually resolve a follow-up by ID, or auto-resolve by channel + thread ID when a response is received.",
+      "category": "followups",
+      "risk": "low",
+      "input_schema": {
+        "type": "object",
+        "properties": {
+          "id": {
+            "type": "string",
+            "description": "Follow-up ID to resolve directly"
+          },
+          "channel": {
+            "type": "string",
+            "description": "Channel to match (used with thread_id for auto-resolution)"
+          },
+          "thread_id": {
+            "type": "string",
+            "description": "Thread ID to match (used with channel for auto-resolution)"
+          }
+        },
+        "required": []
+      },
+      "executor": "tools/followup-resolve.ts",
+      "execution_target": "host"
+    }
+  ]
+}

package/src/config/bundled-skills/followups/tools/followup-create.ts

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

package/src/config/bundled-skills/followups/tools/followup-list.ts

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

package/src/config/bundled-skills/followups/tools/followup-resolve.ts

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

package/src/config/bundled-skills/image-studio/tools/media-generate-image.ts

@@ -1,11 +1,8 @@
 import type { ToolContext, ToolExecutionResult } from '../../../../tools/types.js';
 import type { ImageContent } from '../../../../providers/types.js';
-import { eq } from 'drizzle-orm';
 import { getConfig } from '../../../../config/loader.js';
 import { generateImage, mapGeminiError } from '../../../../media/gemini-image-service.js';
 import { getAttachmentsByIds } from '../../../../memory/attachments-store.js';
-import { getDb } from '../../../../memory/db.js';
-import { conversationKeys } from '../../../../memory/schema.js';
 import { isAttachmentVisible, type AttachmentContext } from '../../../../daemon/media-visibility-policy.js';
 import { getConversationThreadType } from '../../../../memory/conversation-store.js';
 import { getAttachmentSourceConversations } from '../../../../tools/assets/search.js';
@@ -29,17 +26,6 @@ function isAttachmentAccessible(attachmentId: string, currentContext: Attachment
   );
 }
 
-/** Resolve the assistantId for the current conversation. */
-function getAssistantIdForConversation(conversationId: string): string | null {
-  const db = getDb();
-  const row = db
-    .select({ assistantId: conversationKeys.assistantId })
-    .from(conversationKeys)
-    .where(eq(conversationKeys.conversationId, conversationId))
-    .get();
-  return row?.assistantId ?? null;
-}
-
 export async function run(
   input: Record<string, unknown>,
   context: ToolContext,
@@ -64,15 +50,7 @@ export async function run(
   let sourceImages: Array<{ mimeType: string; dataBase64: string }> | undefined;
 
   if (attachmentIds && attachmentIds.length > 0) {
-    const assistantId = getAssistantIdForConversation(context.conversationId);
-    if (!assistantId) {
-      return {
-        content: 'Could not resolve assistant context for attachment lookup.',
-        isError: true,
-      };
-    }
-
-    const attachments = getAttachmentsByIds(assistantId, attachmentIds);
+    const attachments = getAttachmentsByIds(attachmentIds);
 
     // Build visibility context for the current conversation
     const threadType = getConversationThreadType(context.conversationId);

package/src/config/bundled-skills/messaging/tools/messaging-analyze-style.ts

@@ -6,6 +6,7 @@ import { computeMemoryFingerprint } from '../../../../memory/fingerprint.js';
 import { memoryItems } from '../../../../memory/schema.js';
 import { enqueueMemoryJob } from '../../../../memory/jobs-store.js';
 import { extractStylePatterns } from '../../../../messaging/style-analyzer.js';
+import { truncate } from '../../../../util/truncate.js';
 import { resolveProvider, withProviderToken, ok, err } from './shared.js';
 
 function clamp(value: number, min: number, max: number): number {
@@ -100,7 +101,7 @@ export async function run(input: Record<string, unknown>, context: ToolContext):
         upsertMemoryItem({
           kind: 'relationship',
           subject,
-          statement: `${contact.name} (${contact.email}): ${contact.toneNote}`.slice(0, 500),
+          statement: truncate(`${contact.name} (${contact.email}): ${contact.toneNote}`, 500, ''),
           importance: 0.6,
           scopeId,
         });

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

@@ -0,0 +1,31 @@
+---
+name: "Playbooks"
+description: "Trigger-action automation rules for handling incoming messages"
+metadata: {"vellum": {"emoji": "\ud83d\udcd6"}}
+---
+
+Playbooks are trigger-action automation rules that tell the assistant how to handle incoming messages matching a pattern.
+
+## Structure
+
+Each playbook has:
+
+- **Trigger**: Pattern or description that activates the rule (e.g. "meeting request", "from:ceo@*")
+- **Action**: What to do when triggered (natural language description)
+- **Channel**: Which channel the rule applies to ("*" = all channels, or specific like "email", "slack")
+- **Category**: Free-form grouping label (e.g. "scheduling", "triage")
+- **Autonomy level**: How much autonomy the assistant has
+  - `auto` -- execute immediately without asking
+  - `draft` -- prepare a response for user review (default)
+  - `notify` -- alert the user only
+- **Priority**: Numeric priority for overlapping rules (higher = takes precedence)
+
+## Lifecycle
+
+1. Create a playbook with `playbook_create` specifying trigger and action.
+2. List existing playbooks with `playbook_list`, optionally filtering by channel or category.
+3. Update rules with `playbook_update` or remove them with `playbook_delete`.
+
+## Storage
+
+Playbooks are stored as memory items with semantic retrieval, enabling fuzzy matching of incoming messages against trigger patterns.