Hume AI Octave TTS and EVI speech-to-speech configs: synthesize speech and manage EVI configs. Trigger phrases: hume, hume ai, octave tts, EVI config.
npx skills add https://github.com/Anil-matcha/awesome-muse-connectors --skill hume-ai
Synthesize speech with Hume's Octave TTS models and read EVI (Empathic Voice Interface) conversational configs. Reach for this when the user wants expressive TTS audio from text or wants to inspect an EVI voice-agent configuration.
All commands go through bin/hume-ai.py. REST auth uses the X-HUME-API-KEY header (not Bearer); the CLI wires it through the credential surrogate.
bin/hume-ai.py auth
# {"ok": true, "configs": 3} on success
bin/hume-ai.py configs
# list EVI configs (id, name)
bin/hume-ai.py config-get --id <CONFIG_ID>
# one EVI config
bin/hume-ai.py tts --text "Take a breath." --voice "Ava Song" --out calm.mp3
# synthesize with Octave TTS; prints the saved audio path
Notes:
tts sends POST /v0/tts with the text as an utterance and an optional Octave voice name. Audio (or the raw provider response when audio cannot be extracted) is written to --out (default hume-output.mp3); the CLI prints the resulting path.hume-ai (credential is collected as custom.hume-ai)credentials.request_api_access); create one in the Hume portalapi.hume.aicustom_header:X-HUME-API-KEY (the key goes in X-HUME-API-KEY, exactly; not a Bearer header)bin/hume-ai.py authtts call spends Hume credits; synthesize only what the user asked for.🧪 Draft: written from Hume's public API docs with the Octave TTS path cross-checked at build time; not yet live-tested end-to-end. EVI config create/update and voices listing are not yet in the CLI.
Take anil-matcha/hume-ai from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.