voxtype-install
Guide the user through installing, configuring, and launching
git clone --depth 1 https://github.com/pchalasani/claude-code-tools /tmp/voxtype-install && cp -r /tmp/voxtype-install/plugins/voxtype/skills/voxtype-install ~/.claude/skills/voxtype-installSKILL.md
# voxtype Install Guide voxtype is a standalone PyPI package for fully on-device voice dictation on macOS. It types transcribed speech into whatever app has focus. No cloud, no accounts, no audio leaving the machine. ## Install One command; it picks the best engine for the machine automatically (Apple-GPU `parakeet-mlx` on Apple Silicon, CPU `parakeet` elsewhere): ```bash uv tool install voxtype ``` If the user doesn't have `uv`, either install it first (`curl -LsSf https://astral.sh/uv/install.sh | sh`) or use `pipx install voxtype`. Note: voxtype only works on macOS (it types via macOS accessibility APIs). Tell the user this up front if they are on Linux/Windows. ## Configure Run the interactive wizard — it asks a handful of explained questions (engine, activation mode, hotkey, ...) and writes `~/.config/voxtype/config.toml`: ```bash voxtype setup ``` This must run in the user's own terminal (it is interactive); do not run it through an agent shell. Alternative for hand-editors: `voxtype init` writes a fully commented sample config instead. ### Editing the config directly All settings live in `~/.config/voxtype/config.toml` — every key is optional and the file `voxtype init` writes is fully commented. You (the agent) can open and edit this file to help the user tune specific options; common ones: - `engine` — `parakeet-mlx` (Apple GPU), `parakeet` (CPU), or `moonshine`. - `mode` — `toggle` (hotkey), `wake` (wake word), or `vad` (always on). - `segmentation` — `hold` (whole take on toggle-off) or `vad` (per pause). - `hotkey` — toggle chord, e.g. `"<ctrl>+;"` (run `voxtype hotkey` to record one). - `sounds` — set `false` to silence the start/stop chimes. - `wake_word` / `wake_word_aliases`, `submit_phrases`, `overlay`, `paste_hotkey`, `cancel_hotkey`, `copy_to_clipboard`, and more. For the full list — every key, its default, and the engine comparison — read the **Configuration & CLI** reference: <https://pchalasani.github.io/claude-code-tools/tools/voxtype/configuration/> ## Launch ```bash voxtype ``` Then: press `Ctrl+;` (default hotkey), speak, press `Ctrl+;` again — the take is transcribed and typed at the cursor. `Esc` cancels a recording. Saying "go", "over", or "submit" alone presses Enter. First-run notes for the user: - macOS will prompt for **Microphone**, **Accessibility**, and **Input Monitoring** permissions for the terminal app — all three must be granted, then voxtype restarted. - The first launch downloads the speech model (up to ~2 GB for the default Apple-GPU engine, ~490 MB for the CPU engine); later launches skip the download and just load it onto the GPU (a few seconds, shown by a spinner). ## Reference - Config file: `~/.config/voxtype/config.toml` (fully commented; edit to tune any setting) - `voxtype --help` — all flags and subcommands - Config reference (every key + defaults): https://pchalasani.github.io/claude-code-tools/tools/voxtype/configuration/ - Overview & full docs: https://pchalasani.github.io/claude-code-tools/tools/voxtype/
Extract full context of the last task from the most recent parent session
For CLI agents WITHOUT subagent support (e.g., Codex CLI). Search previous code agent sessions for specific work, decisions, or code patterns.
Use this skill when you learn one or more design pattern(s) in the
Design patterns for the Langroid multi-agent LLM framework. Covers
>-
CLI utility to communicate with other CLI Agents or Scripts in other tmux panes; use it only when user asks you to communicate with other CLI Agents or Scripts in other tmux panes.
This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.
Use this when user wants you to walk through (code or text) files in a EDITOR to either explain how some code works, or to show the user what changes you made, etc. You would typically use this repeatedly to show the user your changes or code files one by one, sometimes with specific line-numbers. This way the user is easily able to follow along in their favorite EDITOR as you point at various files possibly at specific line numbers within those files.