playbooks
Playbooks define trigger-action automation rules that enable assistants to automatically respond to incoming messages matching specified patterns. Use playbooks to establish consistent handling workflows across channels, configure when the assistant should act autonomously versus draft responses for review, and organize message-handling logic by category and priority for complex routing scenarios.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/playbooks && cp -r /tmp/playbooks/assistant/src/config/bundled-skills/playbooks ~/.claude/skills/playbooksSKILL.md
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.Set up, authenticate, and run external coding agents (Claude Code, Codex) via the Agent Client Protocol
Shop on Amazon and Amazon Fresh through your browser
Record and analyze API surfaces of web services
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. A one-off diagram, chart, or explainer that just accompanies an answer belongs to the visualize skill (ui_show visual), not an app. 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
Migrate from ChatGPT, Claude, OpenClaw, Hermes, Manus, and other AI assistants into Vellum by inspecting their data exports, conversation archives, files, prompts, custom instructions, memory, saved memories, tools, GPTs, workflows, integrations, and relationships, then mapping as much as safely possible into Vellum primitives. Handles single-source and multi-source migrations with a unified, deduplicated inventory.
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready text for search, Q&A, and summarization without building a custom parsing pipeline.
Import conversation history from ChatGPT into Vellum