followups
The followups skill manages message tracking across communication channels like email, Slack, and WhatsApp, monitoring whether sent messages receive responses. It automatically transitions follow-ups through states (pending, overdue, nudged, resolved) based on expected response windows and can resolve them either individually or by conversation, making it useful for identifying conversations requiring immediate attention or needing reminders.
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/followups && cp -r /tmp/followups/assistant/src/config/bundled-skills/followups ~/.claude/skills/followupsSKILL.md
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 conversation** -- provide channel + conversation_id to auto-resolve all matching pending follow-ups (useful when a response arrives on a conversation) ## 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.
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