Youtube Music

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

What to check before installing: - Confirm you have and trust the OpenClaw CLI/browser tool: scripts call openclaw browser commands and will try to start a browser. If you don't have OpenClaw installed, parts will fail. - The skill writes caches (e.g., /tmp/yt_music_v3_cache.json and /tmp/yt_music_v3.json). These files may contain mapping of queries to URLs/video IDs; review or clear them if you are concerned about local persistence. The skill does not exfiltrate data to external servers. - The package declares YOUTUBE_MUSIC_BROWSER_PROFILE but the v3 scripts default to the 'openclaw' profile and don't read that env var; if you expect the skill to use a different browser profile, either set the profile manually in scripts or confirm how your OpenClaw environment should expose it. - The Node scripts use child_process.execSync to call openclaw; this is expected for a browser-control skill but means commands run with the agent's privileges. Only install/run this skill in an environment you trust. - If you want lower footprint, inspect or run the bundled scripts manually first (they are contained in the skill folder) rather than enabling autonomous invocation. Overall: behavior is coherent with the stated purpose and no obvious data-exfiltration or unrelated credential access was found — treat it as functionally appropriate but verify OpenClaw tooling and the cache behavior before enabling.

Type: OpenClaw Skill Name: youtube-music-ultra Version: 3.0.0 The skill contains multiple critical shell injection vulnerabilities in its Node.js scripts (`scripts/control.js`, `scripts/direct-play.js`, `scripts/ultra-play.js`). These scripts use `child_process.execSync` to execute `openclaw browser` commands, but user-controlled input (e.g., song queries, video IDs) is directly embedded into the shell command strings without proper shell escaping. While URL encoding is applied, it does not prevent shell metacharacters from being interpreted by `execSync`, potentially allowing arbitrary command execution on the host system. There is no evidence of intentional malicious behavior, classifying this as suspicious due to severe vulnerabilities.