← Back to Skills Marketplace
YouTube Music ULTRA
by
om yarewara
· GitHub ↗
· v3.0.0
470
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install youtube-music
Description
Control YouTube Music with natural language. Play, pause, skip, search, manage playlists, and queue tracks. Full playback control via browser automation.
Usage Guidance
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.
Capability Analysis
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.
Capability Assessment
Purpose & Capability
Name/description, scripts, and runtime instructions all describe browser automation for YouTube Music and the required 'node' binary is justified by the included Node.js scripts. However, the declared required env var YOUTUBE_MUSIC_BROWSER_PROFILE is not actually used by the scripts (they hardcode or default to the 'openclaw' profile). This is a mismatch that should be clarified.
Instruction Scope
SKILL.md and the scripts limit actions to controlling https://music.youtube.com via the OpenClaw browser (open/start/status, open targetUrl). The skill also stores listening/cache data (in ~/.openclaw workspace and /tmp cache files) and can auto-start the browser. Those behaviors are consistent with a playback controller, but the presence of persistent caching and a claimed 'listening history' means the skill will collect and store local user activity (privacy consideration).
Install Mechanism
There is no external download/install spec (instruction-only + shipped scripts). Nothing is pulled from arbitrary remote URLs during install, so install risk is low. The code will be written into the skill workspace when added, which is expected for a script-based skill.
Credentials
The declared env var (YOUTUBE_MUSIC_BROWSER_PROFILE) appears unnecessary (unused) — mismatch is suspicious but low risk. No API keys or unrelated credentials are requested. However, the skill requires access to the OpenClaw CLI and can start/open the browser and open arbitrary targetUrl values derived from user queries; combined with several places where shell commands are built from query text (execSync / fastExec / echo into cache files), this introduces potential for command-injection or shell-escaping issues if queries are not sanitized.
Persistence & Privilege
always:false (no forced inclusion). The skill writes cache files (e.g. /tmp/yt_music_v3_cache.json, /tmp/yt_music_v3.json and files under ~/.openclaw/workspace/skills/youtube-music) and can start the OpenClaw browser/gateway. Writing local caches and auto-starting the browser are proportionate for this purpose, but remember these artifacts persist locally and could contain user activity; also the skill can autonomously open URLs (default agent invocation allowed), which expands its operational reach — worth limiting if you don't want autonomous web actions.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install youtube-music - After installation, invoke the skill by name or use
/youtube-music - Provide required inputs per the skill's parameter spec and get structured output
Version History
v3.0.0
v3.0 ULTRA FAST: 95% faster, direct video ID support, smart caching, atomic play actions, fuzzy matching
Metadata
Frequently Asked Questions
What is YouTube Music ULTRA?
Control YouTube Music with natural language. Play, pause, skip, search, manage playlists, and queue tracks. Full playback control via browser automation. It is an AI Agent Skill for Claude Code / OpenClaw, with 470 downloads so far.
How do I install YouTube Music ULTRA?
Run "/install youtube-music" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is YouTube Music ULTRA free?
Yes, YouTube Music ULTRA is completely free (open-source). You can download, install and use it at no cost.
Which platforms does YouTube Music ULTRA support?
YouTube Music ULTRA is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created YouTube Music ULTRA?
It is built and maintained by om yarewara (@oki3505f); the current version is v3.0.0.
More Skills