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.
>
>
>
>
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.