Skip to main content
skill CX Codex

import-track — Claude Code skill: move tracks to album

import-track moves track markdown files from Downloads or other locations into the correct album directory structure. Use it when track files are scattered and need to be organized by your project layout.

CC0-1.0 250 installs ★ 686 updated 2026-10-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a claude-code
Open on GitHub

What import-track does

The skill takes a markdown track file, finds the album by name through MCP, and moves the file to the tracks folder within the album. It handles the genre-based directory structure: the track ends up at {content_root}/artists/{artist}/albums/{genre}/{album}/tracks/{number}-{name}.md. You can pass the track number as an argument or let it extract from the filename; the skill auto-formats with zero-padding (03 not 3).

It requires a config file at ~/.bitwize-music/config.yaml with content_root and artist name, plus the bitwize-music-mcp server to resolve paths and search for albums. If the album isn't found, the skill lists available albums or tells you how to create one.

What it helps with

  • move a track from Downloads into an album folder
  • organize track files according to project structure
  • rename track with zero-padded numbering
  • locate an album by name and place the track in its directory

Example prompts for the agent

  • Move ~/Downloads/t-day-beach.md into the sample-album as track 03
  • Add beach-vibes.md to sample-album when the number is already in the filename
  • Place a downloaded track file into its album folder by album name

How to install import-track

1Skills CLI (Vercel)

npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a claude-code

2Manually: put the files in place

~/.claude/skills/import-track/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/import-track/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about import-track

How do I install import-track in Claude Code?

Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a claude-code, then open ~/.claude/skills/import-track/SKILL.md.

What does import-track do?

It takes a track markdown file and moves it to the correct album folder following the structure {content_root}/artists/{artist}/albums/{genre}/{album}/tracks/. Track numbers are automatically formatted with zero-padding.

What do I need to use this skill?

You need a config file at ~/.bitwize-music/config.yaml with paths and artist name, and the bitwize-music-mcp server to find albums and resolve paths.

Source text

SKILL.md · CC0-1.0
---
name: import-track
description: Moves track markdown files to the correct album location. Use when the user has track files in Downloads or other locations that need to be placed in an album.
argument-hint: <file-path> <album-name> [track-number]
model: haiku
allowed-tools:
  - Read
  - Bash
  - Glob
  - bitwize-music-mcp
---

## Your Task

**Input**: $ARGUMENTS

Import a track markdown file (.md) to the correct album location based on config.

---

# Import Track Skill

You move track markdown files to the correct location in the user's content directory.

## Step 1: Parse Arguments

Expected format: `<file-path> <album-name> [track-number]`

Examples:
- `~/Downloads/track.md sample-album 03`
- `~/Downloads/t-day-beach.md sample-album 03`
- `~/Downloads/03-t-day-beach.md sample-album` (number already in filename)

If arguments are missing, ask:
```
Usage: /import-track <file-path> <album-name> [track-number]

Example: /import-track ~/Downloads/track.md sample-album 03
```

## Step 2: Find Album and Resolve Path via MCP

1. Call `find_album(album_name)` — fuzzy match by name, slug, or partial. Returns album metadata including genre.
2. Call `resolve_path("tracks", album_slug)` — returns the full tracks directory path

If album not found, MCP returns available albums:
```
Error: Album "{album-name}" not found.

Available albums:
[list from MCP response]

Create album first with: /new-album {album-name} <genre>
```

## Step 4: Construct Target Path

The target path is **ALWAYS**:

```
{content_root}/artists/{artist}/albums/{genre}/{album}/tracks/{XX}-{track-name}.md
```

Example with:
- `content_root: ~/bitwize-music`
- `artist: bitwize`
- `genre: electronic` (found from album location)
- `album: sample-album`
- `track-number: 03`
- `track-name: t-day-beach`

Result:
```
~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/03-t-day-beach.md
```

**Track numbering**:
- If track number provided, use it (zero-padded: `03`)
- If filename already has number prefix (e.g., `03-name.md`), preserve it
- If neither, ask user for track number

## Step 5: Move File

```bash
mv "{source_file}" "{target_path}"
```

## Step 6: Confirm

Report:
```
Moved: {source_file}
   To: {target_path}
```

## 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.
```

**Album not found:**
```
Error: Album "{album-name}" not found.
Create it first with: /new-album {album-name} <genre>
```

**Track already exists:**
```
Warning: Track already exists at destination.
Overwrite? (The original was not moved)
```

---

## Examples

```
/import-track ~/Downloads/t-day-beach.md sample-album 03
```

Config has:
```yaml
paths:
  content_root: ~/bitwize-music
artist:
  name: bitwize
```

Album found at: `~/bitwize-music/artists/bitwize/albums/electronic/sample-album/`

Result:
```
Moved: ~/Downloads/t-day-beach.md
   To: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/03-t-day-beach.md
```

---

## Common Mistakes

### ❌ Don't: Manually read config and search for albums

**Wrong:**
```bash
cat ~/.bitwize-music/config.yaml
find . -name "README.md" -path "*albums/$album_name*"
```

**Right:**
```
# Use MCP to find album and resolve path
find_album(album_name) → returns album metadata with genre
resolve_path("tracks", album_slug) → returns full tracks directory path
```

**Why it matters:** MCP handles config reading, fuzzy matching, and path resolution in single calls.

### ❌ Don't: Forget the tracks/ subdirectory

**Wrong destination:**
```
{album_path}/01-track.md
# Example: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/01-track.md
```

**Correct destination:**
```
{album_path}/tracks/01-track.md
# Example: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/01-track.md
```

**Why it matters:** Tracks always go in the `tracks/` subdirectory within the album folder.

### ❌ Don't: Skip track number validation

**Wrong:**
```bash
# Not validating track number format
mv track.md {album_path}/tracks/$track_num-track.md
# Could result in: 3-track.md instead of 03-track.md
```

**Right:**
```bash
# Ensure zero-padding
track_num=$(printf "%02d" $track_num)
mv track.md {album_path}/tracks/$track_num-track.md
# Results in: 03-track.md
```

**Why it matters:** Track numbers must be zero-padded (01, 02, 03...) for proper sorting.

### ❌ Don't: Assume album location without searching

**Wrong:**
```bash
# Guessing album is in electronic genre
mv track.md ~/music-projects/artists/bitwize/albums/electronic/sample-album/tracks/
```

**Right:**
```
# Use MCP to find the album (handles genre resolution)
find_album(album_name) → returns album metadata including genre and path
```

**Why it matters:** Albums are organized by genre. `find_album` resolves the genre automatically.

© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

From the same set52

The whole set →
session-start session-start starts a fresh coding session by checking the setup, loading project state, and showing the work context. It helps restore where the project left off. CX Codex +1 251installs explicit-checker explicit-checker scans song lyrics for profanity and verifies explicit flags before Suno generation or distributor release. CX Codex +1 251installs promo-reviewer promo-reviewer reviews album promo copy by platform and helps polish it before release. Use it to check populated promo/ files and revise posts interactively. CX Codex +1 250installs voice-checker The voice-checker skill scans song lyrics and prose for seven hallmarks of machine-generated text: stacked abstractions, over-explained metaphors, clichéd phrases, missing specifics, perfect grammar instead of natural speech. CX Codex +1 250installs researchers-verifier researchers-verifier is a Claude Code skill that checks research sources, quotes, and claims before a person reviews the work. It produces a report of issues and warnings. CX Codex +1 249installs verify-sources verify-sources guides human review of track citations before Suno music generation. It extracts source links, awaits manual confirmation, and dates track records. CX Codex +1 249installs rename Renames music albums and tracks while synchronizing slugs, folder structures, and metadata. Handy for organizing studio catalog assets. CX Codex +1 249installs about The about skill displays the bitwize-music plugin version and creator details. Trigger it when you need to verify plugin capabilities or check which version is installed. CX Codex +1 248installs

Project sponsors

Companies that keep this analytics open