Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Transform verbose voice input into structured, token-efficient Claude prompts. Use when cleaning up voice memos, dictation output, or speech-to-text transcriptions that contain filler words, repetitions, and unstructured thoughts.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -11% | 0% |
| case-08 | ✗→✓ | ▲ Improved | 34% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 63% | 0% |
| case-13 | ✗→✓ | ▲ Improved | -56% | 0% |
| case-14 | ✗→✓ | ▲ Improved | 8% | 0% |
Transform verbose, stream-of-consciousness voice dictation into structured, token-efficient prompts for Claude Code.
1. DEDUPE → Remove repetitions and filler words
2. EXTRACT → Identify core requirements and constraints
3. STRUCTURE → Organize into standard sections
4. COMPRESS → Reduce to ~30% of original while preserving intentmarkdown## Contexte [Project context, existing stack, relevant files] ## Objectif [Single sentence: what needs to be built/changed] ## Contraintes - [Constraint 1] - [Constraint 2] - [etc.] ## Output attendu [Expected deliverables: files, format, tests]
| Flag | Effect | |------|--------| | --confirm | Show refined prompt before sending to Claude (default) | | --direct | Send refined prompt directly without confirmation | | --verbose | Keep more detail, less compression | | --en | Output in English (default: matches input language) |
/voice-refine
Alors euh j'aimerais que tu m'aides à faire un truc, en fait j'ai une API
qui renvoie des données utilisateurs et je voudrais les afficher dans un
tableau React, mais attention il faut que ça soit paginé parce que y'a
beaucoup de données, genre des milliers d'utilisateurs, et aussi faudrait
pouvoir trier par nom ou par date d'inscription, ah et on utilise Tailwind
dans le projet donc faut que ça matche avec ça.../voice-refine --direct --en
[voice input in any language → sends English prompt directly]| Metric | Target | |--------|--------| | Token reduction | 60-70% | | Information retention | >95% | | Structure clarity | High |
Remove: filler words ("euh", "um", "like", "basically"), repetitions, tangents, hedging ("maybe", "probably" unless relevant), politeness padding ("please", "could you").
Preserve: technical requirements, constraints, existing code context, expected output format, edge cases, business logic rules.
guide/ecosystem/ai-ecosystem.md - Voice-to-Text Tools sectionexamples/before-after.md - Full transformation examplesOther measured skills in the registry, with their headline benchmark lift.