vellum-assistant

>

>

>

>

Check Vellum Assistant architecture and package boundaries. Use when editing imports, moving code, adding endpoints, touching assistant/gateway/client/skill boundaries, or reviewing architecture-sensitive changes.

Review Vellum Assistant code changes for correctness, repo-specific quality rules, security risks, and missing validation. Use when reviewing diffs, preparing a PR, finishing implementation work, or when the user asks for a code review, quality pass, or pre-merge check in this repository.

Guide Vellum Assistant feature flag changes and rollout hygiene. Use when adding, editing, reviewing, or documenting assistant feature flags, rollout-gated behavior, or platform flag follow-up work.

Validate Vellum Assistant database and workspace migrations. Use when adding, editing, reviewing, or testing migrations, release-note migrations, persisted schemas, workspace file formats, or data backfills.

Prepare Vellum Assistant branches for review by checking git hygiene, PR scope, tests, docs, migrations, Linear linking, and companion repo needs. Use before creating a pull request, splitting work into PRs, or asking whether a branch is ready.

Author and review first-party Vellum skills in the repository. Use when editing files under skills/, assistant bundled skills, skill manifests, tool definitions, SKILL.md files, or first-party skill portability and isolation behavior.

Select focused verification commands for Vellum Assistant changes. Use when deciding what tests, typechecks, lints, or smoke checks to run after editing this repository, especially before commits and pull requests.

Review Vellum Assistant user-facing copy, examples, docs, CLI output, UI strings, and assistant-facing release notes. Use when editing text users may read, including README files, SKILL.md files, CLI messages, route errors, update bulletins, and client UI labels.

Spawn external coding agents via the Agent Client Protocol (ACP)

Build and edit small, personal visual tools and artifacts — dashboards, trackers, calculators, data visualizations, charts, simple landing pages, and slide decks the user wants for THEMSELVES. This is the right skill whenever the user asks to "visualize this," "make a chart," or "build an artifact" for their own use, or to edit an app they already built here. Do NOT reach for a ui_show dynamic_page to fake an artifact — build a real persistent app here. NOT for complex, multi-user, or shippable products — those go to a real project folder with a coding agent (see Scope below).

Drive a specific named macOS app via raw input bypassing the Accessibility tree

Control the macOS desktop

Manage contacts, communication channels, access control, and invite links

Use whenever the user wants to write or draft an article, blog post, essay, report, or any long-form content. Creates the content in a rich text editor instead of dumping it in chat, so it can be streamed, reviewed, edited, and exported.

Track sent messages awaiting responses across communication channels

Create images from a text description, or edit photos and graphics the user provides (remove backgrounds or watermarks, retouch, restyle, in-paint). Can produce multiple variants when the user wants options to choose from.

Ingest and process media files (video, audio, image)

Read, search, send, and manage messages across Gmail, Outlook, Telegram, and other platforms

Make outgoing phone calls, receive incoming calls, and pull up past call transcripts

Trigger-action automation rules for handling incoming messages