- name
- quick-voice
- description
- Spin up an instant browser voice session (OpenAI Realtime gpt-realtime-2) to close a topic in a short conversation instead of working through documents. Generic & white-label - works for any process. Supports live data work (read/update files, JSON, run commands), and distill mode (no tools, ends with a structured deliverable). Has a generic canvas that can display images, markdown, code, html, json, video, audio - perfect for "let's go over X" flows where the agent shows you items one by one and you react in real time. Use when user says "let's close this in a voice call", "run a quick voice session about X", "ืชืคืขืื ืฉืืื ืงืืืืช", "let's go over the [images/leads/PRs/files/notes]", or when a task is faster as a 3-minute conversation than as a document edit.
- allowed-tools
- Read, Write, Edit, Bash, Glob, AskUserQuestion
# quick-voice
White-label voice session generator. Each invocation produces a per-session web app that opens a WebRTC voice channel to OpenAI Realtime (`gpt-realtime-2`) with **context-specific instructions, tools, and canvas behavior**.
## When to use
- "ืชืคืขืื ืืืชื ืฉืืื ืงืืืืช ืขื X" / "let's have a quick voice call about X"
- Going through a list of items where speaking is faster than reading + clicking
- Closing a topic that needs a few decisions + updates (not a long-form plan)
- Producing a structured output (decisions / action items / notes) from a free-form discussion
## Two modes
| Mode | Tools | Output |
|---|---|---|
| **live** | File / JSON / bash tools available โ agent updates real data during the call | A summary of changes made (in `output.md`) |
| **distill** | No data-mutation tools; canvas + `save_note` + `end_session` only | A long structured deliverable (decisions, notes, action items) in `output.md` |
The canvas is available in **both** modes.
## How to run a session
### Step 1 โ figure out context
Look at the conversation. The user said one of:
- **Explicit:** "let's close the freelancer reviews" โ topic = freelancer reviews
- **Implicit:** earlier in the conversation we generated 10 images โ topic = "go over generated images"
- **Vague:** "ืชืคืขืื ืฉืืื ืงืืืืช" โ call AskUserQuestion (single Q) to clarify topic + mode
### Step 2 โ pick a runtime directory + generate the session config
Each session has its own **runtime directory** holding `config.json`, `output.md`,
`server.log`, `done.flag`. The runtime dir lives **outside the skill** so the
skill itself stays code-only and project data stays with the project.
Pick a session id: `id=$(date +%Y%m%d-%H%M%S)`.
Choose the runtime directory:
- **Inside a project** (git repo / codebase you're working in):
put it at `<project-root>/.quick-voice/<id>/`. Add `.quick-voice/` to the
project's `.gitignore` so session data never gets committed.
- **No project context:**
use `/tmp/quick-voice-$USER/<id>/`.
Create the directory and write `config.json` into it:
```json
{
"mode": "live",
"topic": "Short Hebrew topic title",
"instructions": "Full Hebrew system prompt for the realtime agent. Tell it what to do, what to ask, when to use the canvas, when to call save_note, when to call end_session. Be specific about the flow.",
"voice": "ash",
"cwd": "/absolute/path/used/as/root/for/relative/file/ops",
"tools": ["canvas_show", "canvas_clear", "save_note", "end_session", "read_file", "list_dir", "update_json"],
"canvas_hints": [
{ "type": "image", "source": "/abs/path/to/image1.png", "title": "Image 1" },
{ "type": "image", "source": "/abs/path/to/image2.png", "title": "Image 2" }
],
"output_template": "# Session output\n\n## Decisions\n\n## Action items\n\n## Notes\n"
}
```
**Fields:**
- `mode`: `"live"` or `"distill"`.
- `topic`: shown in the page header.
- `instructions`: the system prompt. Write it in Hebrew (Aviz prefers Hebrew). Be specific โ describe the flow you want the agent to follow.
- `voice`: `"ash"` (default), `"alloy"`, `"cedar"`, etc.
- `cwd`: directory the file tools are scoped to. **Required** if any file tool is enabled.
- `tools`: whitelist of tool names from the full set (see `lib/tool-defs.js`). For **distill mode** use only: `canvas_show`, `canvas_clear`, `save_note`, `end_session`. For **live mode** add file / JSON / bash tools as needed.
- `canvas_hints`: optional. If you pre-load items the agent should walk through, list them here. Otherwise the agent decides what to show.
- `output_template`: seeds `output.md` so the agent has a structure to fill in via `save_note`.
### Step 3 โ launch
```bash
node ~/.claude/skills/quick-voice/scripts/launch.js <runtime-dir>
```
`<runtime-dir>` is the absolute path to the directory you created in Step 2.
The launcher reads `<runtime-dir>/config.json` and writes `output.md`,
`server.log`, `done.flag` back into the same directory.
Cross-platform (macOS / Linux / Windows). This:
1. Verifies `OPENAI_API_KEY` (from env or `~/.claude/skills/quick-voice/.env`)
2. Runs `npm install` once if `node_modules` is missing
3. Finds a free port in 3031-3040 (uses `net.createServer` โ no shell needed)
4. Spawns `server.js`, polls `/config` until ready
5. Opens the default browser at `http://localhost:<port>` (`open` on macOS, `xdg-open` on Linux, `start` on Windows)
6. Waits for the user to end the session (close browser โ `/done` is hit, or the agent calls `end_session`)
7. Prints `output.md` and exits
### Step 4 โ surface the output
After the launcher returns, read `runtime/<id>/output.md` and present it to the user. Do NOT delete the runtime dir automatically โ the user may want to re-open or audit it. The session log is in `runtime/<id>/server.log`.
## Available tools (full set)
See `lib/tool-defs.js` for OpenAI Realtime tool definitions and `lib/tools.js` for implementations. Whitelist via `config.json.tools`.
**Canvas (both modes):**
- `canvas_show({ type, source, title?, content? })` โ display in canvas. `type` โ `image|markdown|html|code|json|video|audio|text|url`.
- For **media** (`image`, `video`, `audio`): pass `source` (file path or URL).
- For **text-like** (`markdown`, `html`, `code`, `json`, `text`): pass either `content` (inline string) OR `source` (file path โ the client fetches the file via `/file` and renders it). If you have a long block already on disk, prefer `source`; if you're generating short content inline, use `content`.
- For `url`: pass `source` (iframe src).
- `canvas_clear()` โ clear canvas.
**Output / control (both modes):**
- `save_note({ heading, content })` โ append a section to `output.md`.
- `end_session({ summary? })` โ finalize and close. `summary` is appended to output.md.
**Data (live mode only):**
- `read_file({ path })` โ read file under `cwd`.
- `write_file({ path, content })` โ write file under `cwd`.
- `append_file({ path, content })` โ append.
- `update_json({ path, patch })` โ shallow-merge `patch` into a JSON file (object root only).
- `list_dir({ path })` โ list directory contents.
- `run_bash({ cmd })` โ run a shell command in `cwd`. Use sparingly.
## Examples
### Example 1 โ "let's go over the images you just created" (distill)
```json
{
"mode": "distill",
"topic": "ืกืงืืจืช ืชืืื ืืช",
"instructions": "ืืชื ืืฆืื ืืืฉืชืืฉ ืชืืื ืืช ืืืช ืืืช. ืขืืืจ ืื ืชืืื ื: 1) ืงืจื ื-canvas_show ืขื ืื ืชืื ื-canvas_hints, 2) ืฉืื 'ืื ืืขืชื?', 3) ืืงืฉื ืืชืืืื, 4) ืงืจื ื-save_note ืขื heading='[ืฉื ืชืืื ื]' ื-content=[ืชืืืืช ืืืฉืชืืฉ]. ืืฉืืกืืืืื ืืช ืื ืืชืืื ืืช โ ืงืจื ื-end_session.",
"voice": "ash",
"tools": ["canvas_show", "canvas_clear", "save_note", "end_session"],
"canvas_hints": [
{ "type": "image", "source": "/Users/aviz/aviz-crm/output/img-001.png", "title": "1" },
{ "type": "image", "source": "/Users/aviz/aviz-crm/output/img-002.png", "title": "2" }
],
"output_template": "# ืคืืืืง ืขื ืชืืื ืืช\n\n"
}
```
### Example 2 โ "review pending freelancer scores" (live)
```json
{
"mode": "live",
"topic": "ืกืงืืจืช ืคืจืืื ืกืจืื",
"instructions": "ืคืชื ืืงืจืืื ื-read_file({path: 'data/freelancers.json'}). ืืฆื ืื ืคืจืืื ืกืจ ืืงื ืืก (canvas_show type=json). ืฉืื ืืช ืืืืฅ ืืขืืืื ืฆืืื. ืขืืื ืขื update_json. ืชืขื ื-save_note. ืกืืื ืขื end_session.",
"voice": "ash",
"cwd": "/Users/aviz/aviz-crm",
"tools": ["canvas_show", "canvas_clear", "save_note", "end_session", "read_file", "update_json", "list_dir"],
"output_template": "# Freelancer review session\n\n## Updates made\n\n"
}
```
### Example 3 โ vague invocation
User says only "ืชืคืขืื ืฉืืื ืงืืืืช". Call AskUserQuestion once:
> Question: "ืขื ืื ืืฉืืื?"
> Options: [explicit topic the user types in via 'Other'], "ืกืงืืจื ืืืคืฉืืช โ distill ืืืื"
Then build the config from the answer.
## Anti-patterns
- **Don't bake secrets.** `OPENAI_API_KEY` comes from `~/.claude/skills/quick-voice/.env` (or the project's `.env`). Never inline.
- **Don't generate huge instructions.** Keep `instructions` โค 2KB. The agent needs to act fast.
- **Don't skip `cwd`** when enabling file tools โ it scopes the blast radius.
- **Don't enable `run_bash` unless really needed.** Prefer specific tools.
- **Don't auto-delete `runtime/<id>/`.** The user may want to re-open or audit.
## Files in this skill
- `server.js` โ Express server. Reads `$QV_RUNTIME_DIR/config.json`, vends OpenAI ephemeral tokens, executes tool calls server-side, serves files via `/file?path=...`.
- `public/index.html`, `public/app.js` โ WebRTC client + generic canvas renderer (markdown/html/code/json/text can be loaded from `source` paths in addition to inline `content`).
- `lib/tool-defs.js` โ OpenAI Realtime tool schemas.
- `lib/tools.js` โ server-side tool implementations.
- `scripts/launch.js` โ cross-platform Node launcher: takes an absolute `<runtime-dir>` path, finds free port, spawns server, opens browser, waits for done.
Per-session files (`config.json`, `output.md`, `server.log`, `done.flag`) live in the runtime directory you picked โ typically `<project>/.quick-voice/<id>/` or `/tmp/quick-voice-$USER/<id>/`.
View on GitHub