Roon Controller

**Quick judgment** A focused and practical skill for controlling a Roon Core: it covers the essential playback and zone-management functions, has a clean API and CLI, and already shows meaningful adoption (≈1900 downloads). It’s well-suited for home automation and voice/agent control of Roon, especially in environments with Chinese-speaking users. **Strengths** - Handles Roon Core discovery and token persistence automatically, reducing setup friction. - Provides all core playback controls plus current-track metadata in a structured response. - Remembers selected zones across restarts and offers default zone selection heuristics (e.g., zones ending with a specific suffix like "muspi"). - Chinese trigger word support makes it more accessible for Chinese-language commands. **Key risks / limitations** - Hard dependency on a reachable Roon Core and the `roonapi` library; in environments without Roon, all operations will fail. - Relies on naming conventions (e.g., zones ending with "muspi" or "[roon]") for auto-selection, which can cause confusion if user zones are not named accordingly. - Stores the Roon API token in `~/clawd/roon_config.json`; while typical for such tools, it’s a credential that must be protected with proper file permissions. - Exposes only basic playback and status features; no advanced queue management, library browsing, or search. **Recommended scenarios** - Home assistant / OpenClaw agents that need to control an existing Roon setup with simple commands and status queries. - Multilingual (especially Chinese + English) voice-control systems for household media playback. - Smart home workflows where an agent or automation script must start, pause, or skip tracks in specific Roon zones, remembering the last used zone. Overall, this is a solid, purpose-built skill for environments that already use Roon, with low inherent safety risk but a strong dependency on local network and configuration conventions.