Followups

What the source does

• FilesystemDeclared5 observations
• NetworkNone observedNo outbound calls in the source
• ShellNone observedNo commands run in the source
• DependenciesPinnedNothing floats
• SecretsNone foundNo keys in source

Five audit layers

Gates applied: no behavioural pass.

assistant/CLAUDE.md

assistant/src/approvals/CLAUDE.md

assistant/src/notifications/CLAUDE.md

assistant/src/runtime/CLAUDE.md

gateway/CLAUDE.md

import { executeFollowupCreate } from "../../../../tools/followups/followup_create.js";

} from "../../../../tools/types.js";

import { executeFollowupList } from "../../../../tools/followups/followup_list.js";

} from "../../../../tools/types.js";

import { executeFollowupResolve } from "../../../../tools/followups/followup_resolve.js";

Audit 0.4.1 · source sha 19bc86343b63 · 14 Oct 2026Report an issue or request a re-scan

• Publishervellum-ai GitHub organizationOwner of the repository this skill is read from
• Source foldervellum-ai/vellum-assistant/assistant/src/config/bundled-skills/followupsThe exact folder we audited
• LicenceMITAs the repository states it
• Commit pinned for this verdict19bc86343b63A new audit runs when the source changes
• Repository statusNot archivedLast push 1 day ago
• Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

Its description: Track sent messages awaiting responses across communication channels

---
name: followups
description: Track sent messages awaiting responses across communication channels
compatibility: "Designed for Vellum personal assistants"
metadata:
  emoji: "📨"
  vellum:
    display-name: "Followups"
    category: "messaging"
---

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.

Excerpt, first 1,394 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

git clone https://github.com/vellum-ai/vellum-assistant
git -C vellum-assistant checkout 19bc86343b63

Works in

1. 2026-10-14
   ✓SAFE B 89 / 100

   first audit · source 19bc86343b63

Questions about Followups

• github.com/vellum-ai/vellum-assistant/tree/main/assistant/src/co — the audited source at commit 19bc86343b63 and every finding aboveObserved · 14 Oct 2026

Spotted something wrong? Report a correction · Methodology