@vellumai/assistant 0.4.37 → 0.4.41

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

@@ -99,7 +99,7 @@ Trusted contacts control who is allowed to send messages to the assistant throug
 Use this to show the user who currently has access, or to look up a specific contact.
 
 ```bash
-vellum contacts list --json
+assistant contacts list --json
 ```
 
 Optional query parameters for filtering:
@@ -111,7 +111,7 @@ Optional query parameters for filtering:
 Example:
 
 ```bash
-vellum contacts list --role contact --json
+assistant contacts list --role contact --json
 ```
 
 The response contains `{ ok: true, contacts: [...] }` where each contact has:
@@ -172,7 +172,7 @@ Use this when the user wants to remove someone's access. **Always confirm with t
 
 Ask the user: _"I'll revoke access for [name/identifier]. They will no longer be able to message the assistant. Should I proceed?"_
 
-First, list contacts to find the channel's `id` (each entry in a contact's `channels` array has an `id` field -- visible in `GET /v1/contacts` or `vellum contacts list --json` output), then revoke:
+First, list contacts to find the channel's `id` (each entry in a contact's `channels` array has an `id` field -- visible in `GET /v1/contacts` or `assistant contacts list --json` output), then revoke:
 
 **Important**: Before revoking, check the channel's current `status`. If the channel is **blocked**, do not attempt to revoke it -- blocking is stronger than revoking. Inform the user that the contact is already blocked and revoking is not applicable. Only channels with `active` or `pending` status can be revoked.
 
@@ -198,14 +198,14 @@ curl -s -X PATCH "$INTERNAL_GATEWAY_BASE_URL/v1/contact-channels/<channel_id>" \
   -d '{"status": "blocked", "reason": "<optional reason>"}'
 ```
 
-Replace `<channel_id>` with the channel's `id` from the contact's `channels` array (visible in `GET /v1/contacts` or `vellum contacts list --json` output).
+Replace `<channel_id>` with the channel's `id` from the contact's `channels` array (visible in `GET /v1/contacts` or `assistant contacts list --json` output).
 
 ## Channel Readiness
 
 Before creating an invite for any channel, check whether that channel is ready to accept messages. Creating an invite for an unready channel produces an unusable invite — the invitee redeems the code but cannot actually reach the assistant.
 
 ```bash
-vellum channels readiness --json
+assistant channels readiness --json
 ```
 
 The response contains `{ success: true, snapshots: [...] }` where each snapshot has:
@@ -262,7 +262,7 @@ fi
 
 # Prefer backend-provided canonical link when available.
 if [ -z "$INVITE_URL" ]; then
-  BOT_CONFIG_JSON=$(vellum integrations telegram config --json)
+  BOT_CONFIG_JSON=$(assistant integrations telegram config --json)
   BOT_USERNAME=$(printf '%s' "$BOT_CONFIG_JSON" | tr -d '\n' | sed -n 's/.*"botUsername"[[:space:]]*:[[:space:]]*"\([^"]*\)".*/\1/p')
   if [ -z "$BOT_USERNAME" ]; then
     echo "error:no_share_url_or_bot_username"
@@ -496,22 +496,22 @@ If the Slack bot is not available (Slack credentials not configured), tell the g
 Use this to show the guardian their active (and optionally all) invite links.
 
 ```bash
-vellum contacts invites list --source-channel telegram --json
+assistant contacts invites list --source-channel telegram --json
 ```
 
 For voice invites:
 
 ```bash
-vellum contacts invites list --source-channel voice --json
+assistant contacts invites list --source-channel voice --json
 ```
 
 For email, WhatsApp, SMS, or Slack invites:
 
 ```bash
-vellum contacts invites list --source-channel email --json
-vellum contacts invites list --source-channel whatsapp --json
-vellum contacts invites list --source-channel sms --json
-vellum contacts invites list --source-channel slack --json
+assistant contacts invites list --source-channel email --json
+assistant contacts invites list --source-channel whatsapp --json
+assistant contacts invites list --source-channel sms --json
+assistant contacts invites list --source-channel slack --json
 ```
 
 Optional query parameters:

package/src/config/bundled-skills/doordash/lib/client.ts

@@ -5,6 +5,7 @@
  */
 
 import {
+  ADD_CART_ITEM_QUERY,
   CREATE_ORDER_FROM_CART_QUERY,
   DETAILED_CART_QUERY,
   DROPOFF_OPTIONS_QUERY,
@@ -17,7 +18,6 @@ import {
   RETAIL_STORE_FEED_QUERY,
   SEARCH_QUERY,
   STORE_PAGE_QUERY,
-  UPDATE_CART_ITEM_QUERY,
 } from "./queries.js";
 import { loadCapturedQueries } from "./query-extractor.js";
 import { type DoorDashSession, loadSession } from "./session.js";
@@ -583,14 +583,13 @@ export async function addToCart(opts: {
   nestedOptions?: string;
   specialInstructions?: string;
 }): Promise<CartSummary> {
-  // Use updateCartItemV2 — DoorDash now uses this for both adding and updating cart items
-  const data = await graphql<{ updateCartItemV2: DDCart }>(
-    "updateCartItem",
-    getQuery("updateCartItem", UPDATE_CART_ITEM_QUERY),
+  // Use addCartItemV2 for adding items to cart (proper mutation for restaurant items)
+  const data = await graphql<{ addCartItemV2: DDCart }>(
+    "addCartItem",
+    getQuery("addCartItem", ADD_CART_ITEM_QUERY),
     {
-      updateCartItemApiParams: {
+      addCartItemInput: {
         cartId: opts.cartId ?? "",
-        cartItemId: "",
         itemId: opts.itemId,
         itemName: opts.itemName,
         itemDescription: opts.itemDescription ?? "",
@@ -612,7 +611,6 @@ export async function addToCart(opts: {
         isAdsItem: false,
         isBundle: false,
         bundleType: "BUNDLE_TYPE_UNSPECIFIED",
-        cartFilter: null,
       },
       fulfillmentContext: {
         shouldUpdateFulfillment: false,
@@ -622,7 +620,7 @@ export async function addToCart(opts: {
       shouldKeepOnlyOneActiveCart: false,
     },
   );
-  return extractCartSummary(data.updateCartItemV2);
+  return extractCartSummary(data.addCartItemV2);
 }
 
 export async function removeFromCart(

package/src/config/bundled-skills/email-setup/SKILL.md

@@ -16,7 +16,7 @@ Only proceed if the user explicitly asks you to create or set up **your own** (t
 Before doing anything, check whether you already have an email address configured:
 
 ```bash
-vellum email status
+assistant email status
 ```
 
 Inspect `addresses` in the response. If at least one address exists, tell the user the existing address and stop — do NOT create another one.
@@ -26,7 +26,7 @@ Inspect `addresses` in the response. If at least one address exists, tell the us
 Create a new inbox through the CLI:
 
 ```bash
-vellum email inbox create --username <your-username>
+assistant email inbox create --username <your-username>
 ```
 
 For `<your-username>`, use your assistant name (lowercased, alphanumeric only). Check your identity from `IDENTITY.md` or `USER.md` to determine your name. If you don't have a name yet, ask the user what username they'd like for your email.
@@ -36,7 +36,7 @@ Use the returned `inbox.address` (or `inbox.id` if `address` is empty) as the cr
 ## Step 3: Verify Status
 
 ```bash
-vellum email status
+assistant email status
 ```
 
 Confirm the created inbox appears in `addresses`.
@@ -53,7 +53,7 @@ After the inbox is created and visible in status:
 - **One-time only.** If an inbox already exists (Step 1), do not create another. Inform the user of the existing address.
 - **User-initiated only.** Never run this skill unless the user asks you to set up or create an email.
 - **No custom domains.** Use the default provider domain. Do not attempt domain setup.
-- **No API key prompting.** The email API key should already be configured. If the `vellum email` command fails with an API key error, tell the user the email integration is not yet configured and ask them to set it up.
+- **No API key prompting.** The email API key should already be configured. If the `assistant email` command fails with an API key error, tell the user the email integration is not yet configured and ask them to set it up.
 
 ## Troubleshooting
 

package/src/config/bundled-skills/frontend-design/icon.svg

@@ -0,0 +1,16 @@
+<svg viewBox="0 0 16 16" xmlns="http://www.w3.org/2000/svg">
+  <rect x="0" y="0" width="16" height="16" fill="#f5f5f5"/>
+  <rect x="2" y="2" width="12" height="11" fill="#ffffff" stroke="#333333" stroke-width="1"/>
+  <rect x="2" y="2" width="12" height="2" fill="#ff6b6b"/>
+  <rect x="3" y="3" width="10" height="1" fill="#ffffff"/>
+  <rect x="3" y="5" width="2" height="1" fill="#4ecdc4"/>
+  <rect x="6" y="5" width="2" height="1" fill="#4ecdc4"/>
+  <rect x="9" y="5" width="2" height="1" fill="#4ecdc4"/>
+  <rect x="3" y="7" width="4" height="1" fill="#95e1d3"/>
+  <rect x="3" y="8" width="4" height="1" fill="#95e1d3"/>
+  <rect x="3" y="9" width="3" height="1" fill="#95e1d3"/>
+  <rect x="8" y="7" width="5" height="1" fill="#ffd93d"/>
+  <rect x="8" y="8" width="5" height="1" fill="#ffd93d"/>
+  <rect x="8" y="9" width="3" height="1" fill="#ffd93d"/>
+  <rect x="3" y="11" width="10" height="1" fill="#e8e8e8"/>
+</svg>