import-audio
Moves audio files to the correct album location with proper path structure
Install / Use
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audioInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
OtherSupported Platforms
Our assessment of import-audio
import-audio scores 87/100 on our quality scale, 141st of 259 Other skills we index.
Its SKILL.md is 6.5 KB long, well organised into 16 sections with 16 code examples: a thorough specification that gives an agent plenty to work with.
It has 512 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated 28 days ago, so import-audio is actively maintained.
- It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-22. Automated pattern scan on 2026-10-22. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
import-audio compared with similar skills
All 4 of these similar skills score higher than import-audio; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| import-audio (this skill)by bitwize-music-studio | 87 | 512 | 28d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 100.7k | 1d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 77.4k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 47.5k | today | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 89.0k | today | MCP Server |
Frequently asked questions
- How do I install import-audio?
- Run
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio. The install tabs above show the steps for each supported agent. - Which AI agents does import-audio work with?
- It is written for Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is import-audio safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is CC0-1.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is import-audio still maintained?
- The repository was last updated 28 days ago, so import-audio is actively maintained.
Skill content
View source on GitHubname: import-audio description: Moves audio files to the correct album location with proper path structure. Use when the user has downloaded WAV files from Suno or other sources that need to be organized. argument-hint: <file-path> <album-name> [track-slug] model: haiku allowed-tools:
- Read
- Bash
- bitwize-music-mcp
Your Task
Input: $ARGUMENTS
Import an audio file (WAV, MP3, etc.) to the correct album location based on config.
Import Audio Skill
You move audio files to the correct location in the user's audio directory.
Step 1: Parse Arguments
Expected format: <file-path> <album-name> [track-slug]
The track-slug is optional — only needed for stems zip imports when the track can't be inferred from the filename.
Examples:
~/Downloads/track.wav sample-album~/Downloads/03-t-day-beach.wav sample-album~/Downloads/stems.zip sample-album 01-first-taste
If arguments are missing, ask:
Usage: /import-audio <file-path> <album-name> [track-slug]
Examples:
/import-audio ~/Downloads/track.wav sample-album
/import-audio ~/Downloads/stems.zip sample-album 01-first-taste
Step 2: Resolve Audio Path via MCP
- Call
resolve_path("audio", album_slug)— returns the full audio directory path - The resolved path uses the mirrored structure:
{audio_root}/artists/{artist}/albums/{genre}/{album}/
Example result: ~/bitwize-music/audio/artists/bitwize/albums/hip-hop/sample-album/
CRITICAL: Always use resolve_path — never construct paths manually.
Step 3: Detect File Type
Check the file extension and whether it's a stems zip:
| File Type | Action |
|-----------|--------|
| .wav, .mp3, .flac, .ogg, .m4a | Move to album audio dir (Step 4) |
| .zip (stems) | Extract to per-track stems subfolder (Step 4b) |
How to identify a stems zip: The user will say "stems" or the zip contains files like 0 Lead Vocals.wav, 1 Backing Vocals.wav, etc.
Step 4: Create Directory and Move File
mkdir -p {resolved_path}
mv "{source_file}" "{resolved_path}/{filename}"
Step 4b: Import Stems Zip
Stems must go into per-track subfolders to prevent filename collisions (every track has 0 Lead Vocals.wav, etc.):
{resolved_path}/
01-first-taste.wav
02-sugar-high.wav
stems/
01-first-taste/
0 Lead Vocals.wav
1 Backing Vocals.wav
2 Drums.wav
...
02-sugar-high/
0 Lead Vocals.wav
1 Backing Vocals.wav
...
Workflow:
- Determine the track slug from one of:
- The zip filename if it matches a track pattern (e.g.,
01-first-taste-stems.zip→01-first-taste) - The user specifying which track (e.g.,
/import-audio stems.zip sample-album 01-first-taste) - If neither: Ask the user which track the stems belong to
- The zip filename if it matches a track pattern (e.g.,
- Extract into the per-track subfolder:
mkdir -p {resolved_path}/stems/{track-slug} unzip "{source_file}" -d "{resolved_path}/stems/{track-slug}" - Update track metadata: Call
update_track_field(album_slug, track_slug, "stems", "Yes")
Argument format for stems: <zip-path> <album-name> [track-slug]
Step 5: Confirm
Report:
Moved: {source_file}
To: {resolved_path}/{filename}
For stems:
Extracted stems: {source_file}
To: {resolved_path}/stems/{track-slug}/
Files: {count} stem files extracted
Updated: {track-slug} stems → Yes
Error Handling
Source file doesn't exist:
Error: File not found: {source_file}
Config file missing:
Error: Config not found at ~/.bitwize-music/config.yaml
Run /configure to set up.
File already exists at destination:
Warning: File already exists at destination.
Overwrite? (The original was not moved)
MP3 Files
Suno allows downloading in both WAV and MP3 formats (WAV on Pro/Premier, web only). Always prefer WAV for mastering quality.
Downloads are metered since 2026-09-03. Free accounts get 7 lifetime trial downloads (personal use only — never releasable); Pro 20 a month; Premier 60 a month; the count resets on the billing date and does not roll over. One song is one download whatever the format, and its stems are included — download the WAV first, then pull stems later at no extra cost; re-downloading the same song is free. Premier's Suno Studio exports are uncapped and arrive as 32-bit float / 48 kHz WAV — the practical route for a full album in one month. Commercial rights attach only to a permitted download made on a paid plan.
If the user provides an MP3 file:
- Accept the MP3 and import it normally (same path logic)
- Warn the user:
Note: This is an MP3 file. For best mastering results, download the WAV
version from Suno instead. MP3 compression removes audio data that can't
be recovered during mastering.
If WAV isn't available, this MP3 will work but mastering quality may be limited.
- Import the file to the same destination path as WAV files
Supported formats: WAV (preferred), MP3, FLAC, OGG, M4A
Examples
/import-audio ~/Downloads/03-t-day-beach.wav sample-album
Config has:
paths:
audio_root: ~/bitwize-music/audio
artist:
name: bitwize
Result:
Moved: ~/Downloads/03-t-day-beach.wav
To: ~/bitwize-music/audio/artists/bitwize/albums/hip-hop/sample-album/03-t-day-beach.wav
Stems import example
/import-audio ~/Downloads/stems.zip sample-album 01-first-taste
Result:
Extracted stems: ~/Downloads/stems.zip
To: ~/bitwize-music/audio/artists/bitwize/albums/hip-hop/sample-album/stems/01-first-taste/
Files: 5 stem files extracted
Updated: 01-first-taste stems → Yes
Common Mistakes
❌ Don't: Manually read config and construct paths
Wrong:
cat ~/.bitwize-music/config.yaml
mv file.wav ~/music-projects/audio/artists/bitwize/albums/electronic/sample-album/
Right:
# Use MCP to resolve the correct path
resolve_path("audio", album_slug) → returns full path with artist folder
Why it matters: resolve_path reads config, resolves variables, and includes the artist folder automatically. No manual config parsing or path construction needed.
❌ Don't: Mix up content_root and audio_root
Path comparison:
- Content:
{content_root}/artists/{artist}/albums/{genre}/{album}/(markdown, lyrics) - Audio:
{audio_root}/artists/{artist}/albums/{genre}/{album}/(WAV files, stems) - Documents:
{documents_root}/artists/{artist}/albums/{genre}/{album}/(PDFs, research)
Use resolve_path with the appropriate path_type ("content", "audio", "documents") to get the right path.
Related Skills
Agent-Reach
100.7kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
77.4kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
47.5kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Scrapling
89.0k🕷️ A Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
