import-audio — скилл для Claude Code: импорт аудио
Скилл import-audio для Claude Code переносит аудиофайлы в папку альбома и раскладывает stems по трекам. Обрабатывает WAV, MP3 и другие поддерживаемые форматы.
CC0-1.0 257 установок ★ 686 обновлён 2026-10-22
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a claude-codeЧто делает import-audio
Скилл принимает путь к файлу, имя альбома и необязательный track-slug. Через resolve_path("audio", album_slug) он получает путь из конфигурации, создаёт каталог и перемещает WAV, MP3, FLAC, OGG или M4A в аудиопапку альбома.
ZIP со stems распаковывается в отдельную папку трека, чтобы одинаковые имена файлов не конфликтовали. После распаковки скилл вызывает update_track_field и отмечает stems как Yes. Для работы нужен MCP-сервер bitwize-music-mcp и настроенный ~/.bitwize-music/config.yaml; без конфига импорт остановится. Если файл уже есть, исходник не перемещается до подтверждения перезаписи.
Какие задачи решает
- переместить WAV в папку нужного альбома
- разложить ZIP со stems по папке трека
- определить аудиопуть через конфигурацию
- обновить метаданные трека после импорта
- предупредить о сжатии MP3
Примеры запросов агенту
- Импортируй
~/Downloads/03-t-day-beach.wavв альбомsample-album. - Распакуй
~/Downloads/stems.zipв stems трека01-first-tasteальбомаsample-album. - Перемести
~/Downloads/track.flacв правильную папку альбомаsample-album.
Как установить import-audio
1Через Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a claude-code2Вручную: положить файлы
~/.claude/skills/import-audio/SKILL.mdПапка скилла целиком; для одного проекта — .claude/skills/import-audio/
1Через Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a codex2Вручную: положить файлы
.agents/skills/import-audio/SKILL.mdДля всех проектов — ~/.agents/skills/
1Через Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a cursor2Вручную: положить файлы
.cursor/skills/import-audio/SKILL.mdCursor читает и .agents/skills/, и .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills skills/import-audio2Вручную: положить файлы
.github/skills/import-audio/SKILL.md1Через Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a gemini-cli2Командой платформы
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/import-audioВручную: положить файлы
.devin/skills/import-audio/SKILL.mdСтарый путь .windsurf/skills/ тоже читается
Через Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a opencodeClaude.ai
Упакуйте папку в zip и загрузите в Settings → Capabilities → Skills
По шагам, с командами для каждой платформы: Как установить скилл в Claude Code: пять способов
Вопросы об import-audio
Как установить import-audio в Claude Code?
Выполните npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-audio -a claude-code. Файл скилла появится по пути ~/.claude/skills/import-audio/SKILL.md.
Что делает import-audio?
Скилл находит аудиопуть альбома через MCP, перемещает обычные аудиофайлы и распаковывает stems в папку нужного трека. Для ZIP он также обновляет поле stems в метаданных.
Какие форматы поддерживает import-audio?
Он принимает WAV, MP3, FLAC, OGG, M4A и ZIP со stems. WAV указан как предпочтительный формат для мастеринга.
Исходный текст
SKILL.md · CC0-1.0
---
name: 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
1. Call `resolve_path("audio", album_slug)` — returns the full audio directory path
2. 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
```bash
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:**
1. **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
2. **Extract** into the per-track subfolder:
```bash
mkdir -p {resolved_path}/stems/{track-slug}
unzip "{source_file}" -d "{resolved_path}/stems/{track-slug}"
```
3. **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:**
1. Accept the MP3 and import it normally (same path logic)
2. 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.
```
3. 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:
```yaml
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:**
```bash
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.
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills