YouTube Music ULTRA

Control YouTube Music with natural language. Play, pause, skip, search, manage playlists, and queue tracks. Full playback control via browser automation.

This skill appears to do what it says (control YouTube Music via OpenClaw's browser), but review the code before installing: 1) Confirm you trust the OpenClaw CLI and the 'openclaw browser' commands the skill runs (it can start the browser and open arbitrary URLs). 2) The metadata asks for YOUTUBE_MUSIC_BROWSER_PROFILE but the scripts default to 'openclaw' — either remove the unused env requirement or update scripts to respect it. 3) The Node.js and bash code build shell commands and write cache files from user-provided queries (echo into files, execSync/fastExec). These are correctness/privacy risks: unsanitized input could cause shell injection or malformed cache content; cache files store listening history. Inspect/validate or sanitize input handling (or run the skill in an isolated environment) before granting it access. 4) If you allow autonomous invocation, consider the privacy implications (local cache, ability to open URLs) and whether you prefer to keep the skill user-invocable only. Recommended actions: run the bundled test.sh in a sandbox, audit usages of execSync/fastExec/echo for proper escaping, and remove or correctly implement the YOUTUBE_MUSIC_BROWSER_PROFILE requirement. If you are not comfortable auditing the code yourself, run the skill in a restricted container or decline installation.

Type: OpenClaw Skill Name: youtube-music Version: 3.0.0 The skill's core purpose is benign: controlling YouTube Music via OpenClaw browser automation. However, the Node.js scripts (`scripts/control.js`, `scripts/direct-play.js`, `scripts/ultra-play.js`) contain shell injection vulnerabilities. They use `child_process.execSync` to construct and execute shell commands with user-controlled input (e.g., song queries, video IDs) without proper shell escaping. This allows an attacker to inject arbitrary commands or arguments to the `openclaw browser` CLI, posing a significant risk of remote code execution. This is a critical vulnerability, not intentional malice.