Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From wispr-pack
Guides cost tuning for Wispr Flow voice-to-text API integrations using WebSocket or REST, with auth, audio formats, error handling, and dev context tips.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wispr-pack:wispr-cost-tuningThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Guidance for cost tuning with Wispr Flow voice-to-text API.
Guidance for cost tuning with Wispr Flow voice-to-text API.
wss://api.wisprflow.ai/api/v1/ws (recommended, low latency)POST /api/v1/transcribe (simpler, higher latency)| Error | Cause | Solution |
|---|---|---|
401 Unauthorized | Invalid key | Check at wisprflow.ai/developers |
| WebSocket closed | Network issue | Reconnect with backoff |
| Poor accuracy | Wrong context | Set context to 'programming' for code |
See related Wispr Flow skills for more patterns.
npx claudepluginhub fleet-to-force/claude-code-plugins-plus --plugin wispr-pack7plugins reuse this skill
First indexed Jul 10, 2026
Showing the 6 earliest of 7 plugins
Guides cost tuning for Wispr Flow voice-to-text API integrations using WebSocket or REST, with auth, audio formats, error handling, and dev context tips.
Optimize Deepgram costs and usage for budget-conscious deployments. Use when reducing transcription costs, implementing usage controls, or optimizing pricing tier utilization. Trigger: "deepgram cost", "reduce deepgram spending", "deepgram pricing", "deepgram budget", "optimize deepgram usage", "deepgram billing".
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.