Ultimate Music Manager

Organises a messy local music library into a clean Language/Artist/Album hierarchy using acoustic fingerprinting, deduplication, metadata enrichment, and opt...

This skill appears to be what it says: a local music‑library pipeline that fingerprints, deduplicates, enriches metadata, and optionally syncs to Spotify. Before installing or running it: (1) Backup your music folder (MUSIC_ROOT) or test on a copy — the pipeline moves files and there are separate destructive utilities (opt‑in) even though the canonical pipeline claims not to delete files. (2) Inspect config.py and the bundled scripts yourself — scripts are executed locally and will read/write under MUSIC_ROOT and the DATA_DIR. (3) Run scripts in a virtualenv per the README and use preflight.sh and --dry-run modes first. (4) Only provide Spotify credentials if you intend to use Phase 6; OAuth tokens are cached locally. (5) Be careful when enabling the suggested hook: enabling it modifies your agent hook configuration and will execute the provided shell script on PreToolUse events — review the hook code and enable it only if you trust it. (6) Note the minor oddity that the package bundles scripts but also instructs you to git clone the repo — this is not dangerous but redundant; you can inspect/compare the bundled files before cloning. If you want additional assurance, share config.py or any other script you’re unsure about and I can re-check for hidden network calls, writes outside MUSIC_ROOT, or suspicious behavior.

Type: OpenClaw Skill Name: ultimate-music-manager Version: 1.0.1 The bundle contains a shell injection vulnerability in 'scripts/status.sh' where 'eval' is used on configuration values (like MUSIC_ROOT) derived from environment variables, which could lead to arbitrary command execution if a user provides a malformed .env file. Additionally, the skill references several destructive scripts (e.g., 'total_scrub.py', '05D_force_delete_residue.py') that perform bulk file deletions. While the bundle includes a defensive PreToolUse hook ('hooks/safety-guard.sh') designed to warn the AI agent before running these destructive tools, the presence of critical vulnerabilities and high-risk file-deletion capabilities warrants a suspicious classification.