What problem does it solve? APX agents reply in text by default, and getting them to speak requires choosing a TTS engine, wiring API keys, handling audio formats, and debugging silent output. This Skill provides the operational knowledge to configure, test, and troubleshoot the full APX voice stack. ## Core Features & Use Cases - Multi-engine TTS configuration: Set up Piper (local/offline), ElevenLabs, OpenAI, Gemini, or custom OpenAI-compatible endpoints like QVox/Qwen3-TTS via voice.tts.* config keys. - Emotion tags and voice channel: Enable per-engine [tag] emotion markers, and use the unified POST /api/voice/turn endpoint for mic-to-speaker round trips combining Whisper STT, the agent loop, and TTS. - Use Case: You want APX to read Telegram replies aloud while driving. Configure the Gemini engine with an API key, enable mobility replies, and every automatic reply goes out as an OGG/Opus voice note followed by a text transcript. ## Quick Start Ask the agent to configure Piper as the local TTS engine and run a test phrase with apx voice say to confirm spoken output works.