- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-track -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/HEAD/skills/import-trackFrom the publisher
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:
~/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
find_album(album_name) — fuzzy match by name, slug, or partial. Returns album metadata including genre.resolve_path("tracks", album_slug) — returns the full tracks directory pathIf 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}.md
Example with:
content_root: ~/bitwize-musicartist: bitwizegenre: electronic (found from album location)album: sample-albumtrack-number: 03track-name: t-day-beachResult:
~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/03-t-day-beach.md
Track numbering:
03)03-name.md), preserve itmv "{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.
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-trackdescription: Moves track markdown files to the correct album location. Use when the user has track files in Downloads or…---# skills/import-track/SKILL.mdFAQ
Download skills/import-track/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/bitwize-music-studio/claude-ai-music-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.