about
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or…
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.
$ npx -y skills add bitwize-music-studio/claude-ai-music-skills --skill import-track --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/import-trackContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
**Input**: $ARGUMENTS
Import a track markdown file (.md) to the correct album location based on config.
---
You move track markdown files to the correct location in the user's content directory.
Expected format: `<file-path> <album-name> [track-number]`
Examples:
If arguments are missing, ask:
Usage: /import-track <file-path> <album-name> [track-number] Example: /import-track ~/Downloads/track.md sample-album 03
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>The target path is **ALWAYS**:
{content_root}/artists/{artist}/albums/{genre}/{album}/tracks/{XX}-{track-name}.mdExample with:
Result:
~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/03-t-day-beach.md
**Track numbering**:
mv "{source_file}" "{target_path}"Report:
Moved: {source_file}
To: {target_path}**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)
---
/import-track ~/Downloads/t-day-beach.md sample-album 03
Config has:
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
---
**Wrong:**
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.
**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.
**Wrong:**
# 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:**
# 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.
**Wrong:**
# 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.
I love music but never learned an instrument. AI became the creative outlet that was always out of reach. This project started as a way to go deep on Claude Code plugin architecture, agentic workflows, multi-model orchestration, and MCP tooling.
Repo: bitwize-music-studio/claude-ai-music-skills
Provides information about the bitwize-music plugin, its version, and its creator. Use when the user asks about the plugin, its purpose, version, or…
Creates visual concepts for album artwork and generates AI art prompts. Use during planning for concept discussion, or after all tracks are Final for actual…
Designs album concepts, tracklist architecture, and thematic planning through 7 structured phases. Use when planning a new album or reworking an existing album…
Shows a structured progress dashboard for an album with percentage complete per phase, blocking items, and status breakdown. Use for a quick visual overview of…
Tracks and manages album ideas including brainstorming, planning, and status updates. Use when the user wants to add, review, or organize their album idea…
Copies track content (lyrics, style prompts, streaming lyrics) to the system clipboard. Use when the user needs to paste lyrics or style prompts into Suno or…