conversation-groups
Organize conversations into custom sidebar groups — list groups, create new ones, and file conversations into them
git clone --depth 1 https://github.com/vellum-ai/vellum-assistant /tmp/conversation-groups && cp -r /tmp/conversation-groups/assistant/src/config/bundled-skills/conversation-groups ~/.claude/skills/conversation-groupsSKILL.md
Organize the user's conversations into sidebar groups. Groups are the sections shown in the conversation sidebar; each conversation belongs to exactly one group.
## Groups
- **Custom groups** are user-defined sections (e.g. "Work", "Travel planning"). Create them with `conversation_group_create` and file conversations with `conversation_move_to_group`.
- **System groups** are built in and cannot be created, renamed, or deleted:
- `system:pinned` (Pinned) — moving a conversation here pins it; moving it elsewhere unpins it.
- `system:all` (Recents) — the default ungrouped section. Move a conversation here to "remove" it from a custom group.
- `system:scheduled` (Scheduled) and `system:background` (Background) — hold automated conversations. Moving a conversation into these demotes it out of the Recents listing; avoid unless the user explicitly asks.
## Usage
- `conversation_move_to_group` defaults to the **current** conversation, so "file this chat under Work" needs no conversation id.
- Groups can be referenced by name (case-insensitive) or id. Prefer names; fall back to ids when names are ambiguous.
- When the user asks to organize their conversations, check the existing groups first (`conversation_group_list`) and reuse a fitting group rather than creating near-duplicates ("Work" vs "Work stuff").
- Creating a group whose name already exists reuses the existing group instead of creating a duplicate.
- Moves only affect sidebar organization — no conversation content changes, and every move is reversible.
- Subagent and background conversations are hidden from the sidebar regardless of group; moving them has no visible effect.>
>
>
>
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.