Offers
sickn33/agentic-awesome-skills
When the user wants to design, construct, or improve an offer — the thing they actually sell — including value framing, bonus stacking, guarantee design, scarcity/urgency, naming, and payment…
Offer the user several spin-off conversations as clickable buttons on a single persistent card.
MITAuto-check passed
Install Conversation Launcher
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install vellum-ai/vellum-assistant conversation-launcher --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/conversation-launcher .claude/skills/conversation-launcher && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .claude/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcherType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install vellum-ai/vellum-assistant conversation-launcher --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/conversation-launcher .agents/skills/conversation-launcher && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .agents/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install vellum-ai/vellum-assistant conversation-launcher --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/conversation-launcher .cursor/skills/conversation-launcher && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .cursor/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/vellum-ai/vellum-assistant.git --path skills/conversation-launcher--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install vellum-ai/vellum-assistant conversation-launcher --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/conversation-launcher .gemini/skills/conversation-launcher && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .gemini/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install vellum-ai/vellum-assistant conversation-launcherInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/conversation-launcher .github/skills/conversation-launcher && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .github/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install vellum-ai/vellum-assistant conversation-launcher --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/vellum-ai/vellum-assistant.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/conversation-launcher .opencode/skills/conversation-launcher && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "conversation-launcher" agent skill from https://github.com/vellum-ai/vellum-assistant/tree/main/skills/conversation-launcher into .opencode/skills/conversation-launcher/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "conversation-launcher", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
conversation-launcher- GitHub stars
- 1.4k
- Token cost
- ~1.2k tokens
- SKILL.md length
- 514 words
- Files
- 1
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Offer the user several spin-off conversations as clickable buttons on a single persistent card.
- You want to branch into N focused threads (research directions
- SKILL.md covers When this fits, When this does NOT fit, How to render and Do nothing else, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Pending replies
What it does
Conversation Launcher is an agent skill from vellum-ai/vellum-assistant. Offer the user several spin-off conversations as clickable buttons on a single persistent card. Each click spawns a fresh seeded conversation in the sidebar; the user keeps their place in the current conversation. Use when you want to branch into N focused threads (research directions, draft choices, pending replies, triage of N items) without losing the current context. Not for single-destination pivots — just reply inline.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Designed for Vellum personal assistants
The repository describes itself as: An AI Assistant that’s easy to setup, does your work 24/7, knows your preferences and gets better over time. The licence is MIT.
When your agent uses it
- You want to branch into N focused threads (research directions
- Pending replies
- Triage of N items) without losing the current context
Example prompts
- “/conversation-launcher”
Requirements
- Compatibility (from SKILL.md): Designed for Vellum personal assistants
What it can do on your machine
Read from SKILL.md and the folder at commit 33cc983. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Vellum personal assistants
From compatibility in the SKILL.md frontmatter.
Context cost
Conversation Launcher loads about 1.2k tokens when it runs. Until then it costs about 113 tokens; SKILL.md has 514 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from vellum-ai/vellum-assistant at commit 33cc983, republished under its MIT licence (© vellum-ai). 514 words, ~1,211 tokens.
Download SKILL.mdSave it as
.claude/skills/conversation-launcher/SKILL.md (or your agent's skills folder).- name
- conversation-launcher
- description
- Offer the user several spin-off conversations as clickable buttons on a single persistent card. Each click spawns a fresh seeded conversation in the sidebar; the user keeps their place in the current conversation. Use when you want to branch into N focused threads (research directions, draft choices, pending replies, triage of N items) without losing the current context. Not for single-destination pivots — just reply inline.
- compatibility
- Designed for Vellum personal assistants
- metadata.emoji
- 🧭
Use this skill when you want to offer the user several spin-off conversations from the current one. You render one persistent card. Each button on the card spawns its own seeded conversation in the sidebar. The user can click multiple buttons without losing their place — the origin conversation (this one) keeps focus.
When this fits
- Research branches — "here are three angles to pursue"
- Draft choices — "here are the reply drafts I could write"
- Triaging N items — "here are the five threads with pending replies"
- Pending-reply fan-out — each sender gets their own drafting conversation
When this does NOT fit
- Single-destination pivots — if there's one obvious next conversation, just reply inline or navigate there directly. One button is not a menu.
- Options that share context and should stay in one thread — keep them here.
- Inline Q&A the user can skim in place — answer; don't fan out.
How to render
Emit exactly one ui_show call with a card shaped like this, then end your turn:
{
"surface_type": "card",
"display": "inline",
"persistent": true,
"await_action": false,
"data": {
"title": "<framing headline>",
"body": "<one short sentence framing the choice>"
},
"actions": [
{
"id": "opt-1",
"label": "<short button label>",
"style": "primary",
"data": {
"_action": "launch_conversation",
"title": "<short conversation title>",
"seedPrompt": "<full first-user-message seed>",
"anchorMessageId": "<optional anchor message id from this conversation>"
}
},
{
"id": "opt-2",
"label": "<short button label>",
"style": "secondary",
"data": {
"_action": "launch_conversation",
"title": "<short conversation title>",
"seedPrompt": "<full first-user-message seed>"
}
}
]
}Field notes:
persistent: truekeeps the card visible after a click so the user can fire more buttons.await_action: falselets the turn end without reserving the interactive-surface slot — the launcher dispatches its action directly, so blocking other surfaces is unnecessary.- Each action's
datamust contain_action: "launch_conversation",title, andseedPrompt.anchorMessageIdis optional — include it when the spawned conversation should thread off a specific message in this one. labelis the button text (short, ≤ 4 words, ≤ 30 chars).titleis the new conversation's sidebar name (3–5 words, specific not generic).seedPromptis the first user message of the new conversation — written in first-person as if the user typed it, with enough context that the new conversation can pick up without re-asking.- Use
style: "primary"for the recommended option (at most one),style: "secondary"for the rest.
Show full SKILL.md (215 more words)Show less
Do nothing else
After rendering the card, end your turn. The click pipeline handles everything:
- Do NOT run a follow-up step, issue any HTTP request, or write any file.
- Do NOT send a chat message after the card. The card is the response.
- Do NOT re-render the card on each click — it stays visible.
UX contract the client enforces
- The card stays open and clickable for the lifetime of the live conversation — multiple buttons can be fired in succession without losing the user's place. If the conversation is closed and reopened later from history, the restored card reverts to single-click behavior (history rehydration drops the
persistentflag — out of scope for this skill). - Each
action.idfires at most once per card lifetime; sibling actions remain clickable. - Each spawned conversation inherits this conversation's guardian / trust context automatically.
- Sidebar focus stays on this conversation. The user sees new entries appear and can navigate in at their pace.
Authoring tips
- Don't invent options. Only surface branches the user has actually discussed or implied.
- 2–5 buttons is the sweet spot. One option? Just reply inline. More than five? Trim or group.
- Keep the card body to one sentence. The buttons carry the payload; the body just frames the choice.
- Conversation titles should be highly concise, context-specific, and 3–5 words.
© vellum-ai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/conversation-launcher of vellum-ai/vellum-assistant.
Open the folder on GitHubat commit 33cc983
Compare with similar skills
Conversation Launcher next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Conversation Launcher this skillvellum-ai/vellum-assistant | 1.4k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Offerssickn33/agentic-awesome-skills | 47k | 1 repos | ~2.4k | Automated safety check: Pass | MIT | |
| Modeling Conversion MetricsPostHog/posthog | 40k | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Offer Appointmentsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.9k | Automated safety check: Pass | MIT | |
| Cost Conversationruvnet/ruflo | 74k | — | ~407 | Automated safety check: Notes | MIT | |
| Conversation Memorydavila7/claude-code-templates | 33k | 4 repos | ~440 | Automated safety check: Pass | MIT |
Similar skills
- Official
Modeling Conversion Metrics
PostHog/posthog
Build reusable conversion models — funnel/step conversion rates, drop-off, and time-to-convert — on either PostHog data-warehouse views (HogQL) or an external dbt project.
Offer Appointment
sickn33/agentic-awesome-skills
Offer register: candidate, position, department, employment type, offered salary and currency, offer date and expiry, joining date, probation, approver and sign-off.
Cost Conversation
ruvnet/ruflo
Per-conversation cost view — list every session in cost-tracking with started-at, message count, top model, and total cost
Conversation Memory
davila7/claude-code-templates
Persistent memory systems for LLM conversations including short-term, long-term, and entity-based memory Use when: conversation memory, remember, memory persistence, long-term memory, chat history.
Conversation Archive
garrytan/gbrain
Import AI-assistant chat exports (ChatGPT, Claude, Perplexity) and agent session transcripts into the brain as one dated page per conversation under conversations/, validate each page against the…
More from vellum-ai/vellum-assistant
All 108 skills in this repoVellum GitHub App Setup
vellum-ai/vellum-assistant
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity.
Discord App Setup
vellum-ai/vellum-assistant
Connect a Discord bot to the assistant via the Discord Gateway with guided application creation and intent configuration
Sentry App Setup
vellum-ai/vellum-assistant
Create and configure a Sentry internal integration so the assistant can manage issues, alerts, and releases under its own identity
Memory Corpus Ingest
vellum-ai/vellum-assistant
Ingest a large dataset into memory as a skimmed map. An agent skill from vellum-ai/vellum-assistant.
Plugin Builder
vellum-ai/vellum-assistant
A skill your agent uses when the user wants to build, scaffold, ship, or edit a Vellum plugin that bundles multiple surfaces (hooks, tools, skills, and more) into one installable package.
Slack App Setup
vellum-ai/vellum-assistant
Connect a Slack app to the Vellum Assistant via Socket Mode.
Questions about Conversation Launcher
What does Conversation Launcher do?
Offer the user several spin-off conversations as clickable buttons on a single persistent card. Conversation Launcher is an agent skill from vellum-ai/vellum-assistant. Offer the user several spin-off conversations as clickable buttons on a single persistent card.
When should I use Conversation Launcher?
Conversation Launcher fits situations like: you want to branch into N focused threads (research directions; pending replies; triage of N items) without losing the current context.
How do I install Conversation Launcher in Claude Code?
Run `npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a claude-code`. Or copy the skill folder (skills/conversation-launcher in vellum-ai/vellum-assistant) into .claude/skills/conversation-launcher in your project. Claude Code loads it when a task matches its description.
How do I install Conversation Launcher in Codex?
Run `npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a codex`. Or copy the skill folder (skills/conversation-launcher in vellum-ai/vellum-assistant) into .agents/skills/conversation-launcher in your project. Codex loads it when a task matches its description.
Can I use Conversation Launcher in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add vellum-ai/vellum-assistant --skill conversation-launcher -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/conversation-launcher, .gemini/skills/conversation-launcher, .github/skills/conversation-launcher and .opencode/skills/conversation-launcher in your project.
What does Conversation Launcher need to run?
SKILL.md names no scripts, command-line tools or credentials: Conversation Launcher is instructions for the agent only. Compatibility (from SKILL.md): Designed for Vellum personal assistants.
Does Conversation Launcher access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Conversation Launcher safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Conversation Launcher use?
Conversation Launcher is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Conversation Launcher use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Conversation Launcher?
Skills that share tags, products or a category with Conversation Launcher: Offers (sickn33/agentic-awesome-skills, 47k stars), Modeling Conversion Metrics (PostHog/posthog, 40k stars), Offer Appointment (sickn33/agentic-awesome-skills, 47k stars) and Cost Conversation (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Conversation Launcher?
vellum-ai (a GitHub organization) maintains it in vellum-ai/vellum-assistant, which has 1,408 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on October 9, 2026.
Source: vellum-ai/vellum-assistant on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.