Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Ultimate Music Manager

v1.0.1

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

0· 76·0 current·0 all-time

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for drajb/ultimate-music-manager.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Ultimate Music Manager" (drajb/ultimate-music-manager) from ClawHub.
Skill page: https://clawhub.ai/drajb/ultimate-music-manager
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Required env vars: MUSIC_ROOT
Required binaries: python3.12, git
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install ultimate-music-manager

ClawHub CLI

Package manager switcher

npx clawhub@latest install ultimate-music-manager
Security Scan
Capability signals
Requires OAuth token
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name and description match what the skill asks for: it operates on a local MUSIC_ROOT and needs Python 3.12 and git to set up and run the pipeline. Optional env vars (Spotify credentials, FFmpeg path, data dir, etc.) align with the described optional features (Spotify sync, non‑MP3 decoding, token cache).
Instruction Scope
Runtime instructions direct the agent (and user) to run a sequence of local scripts that read and reorganize files under MUSIC_ROOT, produce JSON artifacts, and optionally call Shazam/Apple/Spotify APIs. The instructions also suggest adding a PreToolUse hook that relies on the CLAUDE_TOOL_INPUT environment variable — that is outside the skill's declared env list but is part of the hook mechanism; the hook script shown only prints warnings. The pipeline includes separate destructive utilities (05D, 05F, total_scrub, absolute_zero_sort) but marks them as opt‑in and provides a safety‑guard hook.
Install Mechanism
No arbitrary downloads or extract/install steps in the skill bundle. The SKILL.md recommends cloning the repo from GitHub (a normal release host). The package is instruction‑first with included scripts; the lack of an install spec is somewhat redundant (scripts are bundled but instructions still tell the user to git clone), but this is explainable and not inherently risky.
Credentials
Only one required environment variable (MUSIC_ROOT) is requested; other env vars are optional and correspond to optional features (Spotify OAuth credentials for sync, SHAZAM_CONCURRENCY, FFmpeg binary override, etc.). The safety hook references CLAUDE_TOOL_INPUT but that is a hook input rather than a secret the skill demands. No unrelated credentials (AWS, cloud provider keys, or broad secrets) are requested.
Persistence & Privilege
The skill is not always:true and does not auto‑enable itself. It does instruct the user to enable a PreToolUse hook (via editing .claude/settings.json or openclaw hooks enable) — enabling that hook will cause the included shell script to run on future PreToolUse events. That is a user action and not automatic, but it does grant the skill code the ability to run on agent tool invocations once enabled. The hook itself appears to be a benign safety prompt.
Assessment
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.

Like a lobster shell, security has layers — review code before you run it.

Runtime requirements

Binspython3.12, git
EnvMUSIC_ROOT
Primary envMUSIC_ROOT
latestvk978wb5vq1ddj4m7w1y7hjesxn84qqsx
76downloads
0stars
2versions
Updated 2w ago
v1.0.1
MIT-0

Sonic Phoenix

A multi-phase pipeline that transforms a disorganised local music collection into a pristine, fully-tagged library sorted by <Language>/<Artist>/<Album>/<Artist> - <Title>.<ext>. Works with any language — Hindi, English, Japanese, Spanish, or anything else your collection contains.

The pipeline never deletes audio files. Suspected duplicates are moved to a staging folder for manual review.

Quick Reference

SituationAction
First-time setupEnvironment Setup
Sort a messy music folderRun Phases 1-5 in order
Identify unknown songsRun Phase 1 (Shazam fingerprinting)
Find and remove duplicatesRun Phase 2 (SHA-256 catalog)
Fix bad/missing ID3 tagsRun Phase 4 (iTunes enrichment)
Sync library to SpotifyRun Phase 6 (requires Spotify app credentials)
Add language classification hintsCreate hint files in config/language_hints/
Check current configurationpython config.py

Environment Setup

Prerequisites

  • Python 3.12 (required — shazamio-core only ships wheels for 3.10-3.12)
  • Git (to clone the repo)
  • FFmpeg (optional — only needed if your collection contains non-MP3 formats like FLAC, OGG, or WMA that Shazam needs to decode)

Installation

# Clone into your music folder (recommended) or anywhere else
cd /path/to/your/music
git clone https://github.com/drajb/sonic-phoenix.git
cd sonic-phoenix

# Create virtual environment with Python 3.12
python3.12 -m venv .venv

# Activate
source .venv/bin/activate          # macOS / Linux
# .venv\Scripts\activate           # Windows PowerShell
# .venv\Scripts\activate.bat       # Windows cmd

# Install dependencies
pip install -r requirements.txt

Configuration

Create a .env file in the repo root (copy from .env.example):

# REQUIRED — absolute path to the root of your music collection
MUSIC_ROOT=/path/to/your/music

# OPTIONAL — override any of these defaults:
# SORTED_ROOT=/path/to/your/music/Sorted
# DATA_DIR=/path/to/your/music/.data
# SHAZAM_CONCURRENCY=20
# ITUNES_COUNTRIES=US,GB

Verify configuration:

python config.py

This prints all resolved paths and confirms MUSIC_ROOT exists.

Directory Layout After Setup

<MUSIC_ROOT>/
├── sonic-phoenix/           # This repo
│   ├── config.py            # Central configuration (single source of truth)
│   ├── .env                 # Your local overrides (gitignored)
│   ├── 01A_extract_metadata.py
│   ├── 01D_shazam_all_files.py
│   ├── ...
│   └── config/
│       └── language_hints/  # Optional language classification overrides
│           └── examples/    # Templates to copy and customise
├── Sorted/                  # Pipeline output (auto-created)
│   ├── English/
│   │   ├── Adele/
│   │   │   └── 25/
│   │   │       └── Adele - Hello.mp3
│   │   └── ...
│   ├── Hindi/
│   └── <any language langdetect finds>/
├── .data/                   # Machine-generated JSON artifacts (auto-created)
│   ├── metadata_catalog.json
│   ├── shazam_final_results.json
│   ├── catalog.json
│   ├── final_catalog.json
│   └── ...
└── <your unsorted audio files>

The Pipeline

Happy Path (Minimum Viable Run)

For a quick, effective sort of your library, run these scripts in order:

python 01A_extract_metadata.py     # Extract ID3/FLAC tags
python 01D_shazam_all_files.py     # Acoustic fingerprint every file via Shazam
python 02A_catalog_music.py        # SHA-256 hash catalog + duplicate detection
python 02D_organize_music.py         # Sort into Language/Artist/Album hierarchy
python 03A_consolidate_by_artist.py --dry-run   # Preview artist folder merges
python 03A_consolidate_by_artist.py              # Execute merges
python 03D_titanium_resort.py      # Final structural enforcement pass
python 04I_polish_and_enrich_v6.py # Enrich tags via iTunes + embed artwork
python 05I_finalize_catalog.py     # Lock the master catalog

Each script is resumable — if interrupted, re-run it and it picks up where it left off.

Phase 1: Extraction and Identification

ScriptStatusPurpose
01A_extract_metadata.pyCANONICALReads existing ID3/FLAC/MP4 tags via Mutagen. Splits files into tagged_files and untagged_files in metadata_catalog.json.
01B_shazam_identify.pyUTILITYShazam-identify only the untagged files from 01A.
01C_shazam_by_hash.pyUTILITYPropagate a single Shazam match to all byte-identical copies (via hash groups from Phase 2).
01D_shazam_all_files.pyCANONICALForce every audio file through Shazam regardless of existing tags. Use this when tags are unreliable. 20-way concurrent by default.
01E_test_matching.pyUTILITYSpot-check a handful of files against Shazam to verify the pipeline is working.

When to use 01B vs 01D: If your collection has clean tags on most files, use 01A then 01B (faster — only fingerprints untagged files). If tags are unreliable (generic names like "Track 01", meaningless album fields, garbled metadata), use 01D to fingerprint everything and cross-validate against the acoustic results.

Shazam rate limiting: If you see HTTP 429 errors, lower SHAZAM_CONCURRENCY in your .env (try 5-10).

Phase 2: Cataloguing and Deduplication

ScriptStatusPurpose
02A_catalog_music.pyCANONICALSHA-256 hash every audio file. Writes catalog.json with duplicate groups.
02B_analyze_catalog.pyUTILITYAnalyses the hash catalog and prints duplicate statistics. Read-only reporter.
02C_organize_files.pyUTILITYOrganises files using the hash catalog and final catalog. Alternative to 02D.
02D_organize_music.pyCANONICALThe main sorter. Reads Shazam results and moves files into <SORTED_ROOT>/<Language>/<Artist>/<Album>/.

Phase 3: Consolidation and Structural Cleanup

ScriptStatusPurpose
03A_consolidate_by_artist.pyUTILITYMerge fragmented artist folders (e.g. "Akon feat Eminem" into "Akon"). Supports --dry-run.
03D_titanium_resort.pyCANONICALFinal structural enforcer. Any file not matching Language/Artist/Album/ gets re-sorted.
03F_reorganize_binary.pyUTILITYResolve near-duplicate files via binary comparison.

Phase 4: Metadata Enrichment

ScriptStatusPurpose
04I_polish_and_enrich_v6.pyCANONICALThe single enrichment entry point. Cleans junk from tags (quality markers, description artifacts, miscellaneous noise), enriches via iTunes Search API (artist, title, album, release date, artwork), fetches synchronized lyrics from LrcLib, embeds cover art into ID3 tags.

iTunes rate limiting: The script rotates queries across country codes (default: US, GB). Add more via ITUNES_COUNTRIES=US,GB,AU,CA in .env.

Phase 5: Finalization

ScriptStatusPurpose
05I_finalize_catalog.pyCANONICALMerges ID3 tags, Shazam results, and NLP language classification into final_catalog.json. This is the read-only master snapshot of the library.

Supporting utilities: 05A (JSON repair), 05B (sanitize results), 05C (confidence audit), 05D (residue purge), 05E/05H (empty-folder vacuum).

Phase 6: Spotify Sync (Optional)

Requires a free Spotify Developer account.

ScriptStatusPurpose
06B_spotify_setup.pyCANONICALOAuth handshake — run once to cache the token.
06C_spotify_backup.pyCANONICALSnapshot all existing playlists before making changes.
06D_spotify_sync_engine.pyCANONICALCreates per-language playlists mirroring your local library. Resumable.
06E_spotify_discovery_sync.pyCANONICALCross-references local artists with Spotify listening history and generates genre-based "Essentials" playlists.

Spotify setup:

  1. Create an app at https://developer.spotify.com/dashboard
  2. Set Redirect URI to http://127.0.0.1:8888/callback
  3. Add to .env:
    SPOTIFY_CLIENT_ID=your_client_id
    SPOTIFY_CLIENT_SECRET=your_client_secret
    
  4. Run python 06B_spotify_setup.py — browser opens, approve scopes, token is cached.

Language Classification

The pipeline uses langdetect (NLP) to classify tracks by language automatically. No hardcoded language list — it creates whatever folders your collection needs.

Language Hints (Optional)

For artists that NLP can't classify from Latin-script titles (e.g. Bollywood artists romanised as "Arijit Singh"), create hint files:

config/language_hints/
├── examples/           # Copy and customise these templates
│   ├── English.json
│   ├── Hindi.json
│   └── README.md       # Full schema reference
├── Hindi.json          # Your custom hints (create from examples)
└── Spanish.json

Hint file schema:

{
  "artists": ["Arijit Singh", "A.R. Rahman", "Shreya Ghoshal"],
  "dna": ["bollywood", "bhangra", "desi"],
  "keywords": ["ishq", "dil", "pyaar"],
  "lang_codes": ["hi", "pa"]
}
  • artists — exact artist names to classify into this language
  • dna — substrings to match in folder/file paths
  • keywords — substrings to match in track titles
  • lang_codes — ISO 639-1 codes that langdetect might return for this language

Configuration Reference

All configuration lives in config.py and is driven by environment variables (set in .env or your shell).

VariableRequiredDefaultPurpose
MUSIC_ROOTYesParent of repo dirRoot of your music collection
SORTED_ROOTNo<MUSIC_ROOT>/SortedDestination for sorted files
DATA_DIRNo<MUSIC_ROOT>/.dataMachine-generated JSON artifacts
DUPLICATES_STAGINGNo<repo>/Duplicates_StagingQuarantine for suspected duplicates
UNIDENTIFIED_DIRNo<SORTED_ROOT>/UnidentifiedFiles Shazam couldn't identify
FFMPEG_BINNo<MUSIC_ROOT>/ffmpeg/binPortable FFmpeg path (Windows)
SHAZAM_CONCURRENCYNo20Parallel Shazam calls (lower if rate-limited)
ITUNES_COUNTRIESNoUS,GBCountry codes for iTunes API rotation
SPOTIFY_CLIENT_IDPhase 6 onlySpotify app client ID
SPOTIFY_CLIENT_SECRETPhase 6 onlySpotify app client secret
SPOTIFY_REDIRECT_URINohttp://127.0.0.1:8888/callbackSpotify OAuth redirect

Supported Audio Formats

.mp3, .m4a, .flac, .wav, .ogg, .wma, .aac, .opus

Safety Guarantees

  • No deletion. Audio files are never deleted. Duplicates are moved to Duplicates_Staging/ for manual review.
  • No writes into the music hierarchy. All working state lives in <DATA_DIR> or the repo directory.
  • Resumable. Every script can be interrupted and re-run safely.
  • Non-destructive tags. Enrichment writes new tags but does not remove existing valid data.

Troubleshooting

ProblemFix
shazamio-core fails to installYou're on Python 3.13+. Use Python 3.12: python3.12 -m venv .venv
Shazam returns HTTP 429Lower SHAZAM_CONCURRENCY to 5-10 in .env
iTunes returns 403Add more country codes: ITUNES_COUNTRIES=US,GB,AU,CA,DE
MUSIC_ROOT does not existSet MUSIC_ROOT in .env to the absolute path of your music folder
Tags still show junk after enrichmentRe-run 04I_polish_and_enrich_v6.py — it's idempotent
Spotify 403 on playlist creationAdd your Spotify account under "Users and Access" in the Developer Dashboard (Development Mode restriction)
langdetect misclassifies a languageCreate a hint file in config/language_hints/ for that language
Empty artist/album folders after sortingRun 05E_final_cleanup.py or 05H_final_vacuum.py to vacuum empties

Scripts

Helper scripts that automate common workflows. Run from the repo root.

ScriptPurpose
ultimate-music-manager/scripts/preflight.shValidates Python 3.12, venv, dependencies, .env, MUSIC_ROOT, FFmpeg. Run before first pipeline execution.
ultimate-music-manager/scripts/run-pipeline.shExecutes the happy-path sequence (Phases 1-5) with progress and timing. Supports --skip-shazam, --spotify, --dry-run.
ultimate-music-manager/scripts/status.shDashboard showing file counts, language breakdown, data file status, and pipeline progress.

Usage

# Check environment is ready
bash ultimate-music-manager/scripts/preflight.sh

# Preview what the pipeline will do
bash ultimate-music-manager/scripts/run-pipeline.sh --dry-run

# Run the full pipeline
bash ultimate-music-manager/scripts/run-pipeline.sh

# Run including Spotify sync
bash ultimate-music-manager/scripts/run-pipeline.sh --spotify

# Check pipeline status at any time
bash ultimate-music-manager/scripts/status.sh

Hook Integration

A safety guard hook prevents accidental execution of destructive utility scripts.

Setup (Claude Code)

Add to .claude/settings.json:

{
  "hooks": {
    "PreToolUse": [{
      "matcher": "Bash",
      "hooks": [{
        "type": "command",
        "command": "./ultimate-music-manager/hooks/safety-guard.sh"
      }]
    }]
  }
}

The hook intercepts commands referencing 05D_force_delete_residue, 05F_final_scrub, total_scrub, or absolute_zero_sort and injects a warning requiring explicit user confirmation. Silent (zero overhead) for all other commands.

See hooks/HOOK.md for details.

References

Detailed documentation for deeper dives:

DocumentContents
references/data-files.mdSchema and lineage for every JSON artifact — which script writes it, which scripts read it, full data flow diagram.
references/language-hints-guide.mdHow to create language hint files, full schema, examples for Hindi/Japanese/Spanish, tips for getting classification right.

Design Principles

  1. Config-driven. One config.py module, one .env file. No hardcoded paths anywhere.
  2. Language-agnostic. No baked-in language lists. langdetect + optional hint files handle any language.
  3. Phased and incremental. Each phase builds on the previous. You can stop after any phase and have a useful result.
  4. Auditable. Every move, merge, and enrichment decision is logged to JSON in <DATA_DIR>.
  5. Zero-config happy path. Clone into your music folder, create a .env with MUSIC_ROOT, and run.

Comments

Loading comments...