Skip to content
import-track logo

Import Track Skill

import-track

Move track markdown files to the correct album location

SKILL.md

Full skill instructions

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: Read Config (REQUIRED)

ALWAYS read the config file first. Never skip this step.

cat ~/​.bitwize-music/​config.yaml

Extract:

  • paths.content_root → The base content directory
  • artist.name → The artist name (e.g., "bitwize")

Step 3: Find Album and Determine Genre

Search for the album directory to find its genre:

find {content_root}/​artists/​{artist}/​albums -type d -name "{album-name}" 2>/​dev/​null

If album not found:

Error: Album "{album-name}" not found.

Available albums:
[list albums found in artists/​{artist}/​albums/]

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

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:

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: Skip reading config

Wrong:

# Assuming content_root path
mv track.md ~/​music-projects/​artists/​bitwize/​albums/​...

Right:

# Always read config first
cat ~/​.bitwize-music/​config.yaml
# Use paths.content_root and artist.name from config

❌ Don't: Search from wrong location

Wrong:

# Searching from current directory
find . -name "README.md" -path "*albums/​$album_name*"

Right:

# Search from content_root
content_root=$(yq '.paths.content_root' ~/​.bitwize-music/​config.yaml)
find "$content_root" -name "README.md" -path "*albums/​$album_name*"

Why it matters: Album might not be in current working directory.

❌ 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: Use hardcoded artist name

Wrong:

# Assuming artist is bitwize
find ~/​music-projects/​artists/​bitwize/​albums -name "README.md"

Right:

# Read artist.name from config
artist=$(yq '.artist.name' ~/​.bitwize-music/​config.yaml)
find "$content_root/​artists/​$artist/​albums" -name "README.md"

❌ Don't: Skip track number validation

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.

❌ Don't: Assume album location without searching

Wrong:

# Guessing album is in electronic genre
mv track.md ~/​music-projects/​artists/​bitwize/​albums/​electronic/​sample-album/​tracks/

Right:

# Search for album across all genres
find "$content_root/​artists/​$artist/​albums" -type d -name "$album_name"
# Album might be in hip-hop, electronic, folk, etc.

Why it matters: Albums are organized by genre. You need to find the album first, not assume its genre.

More Other skills

Delegate independent tasks to specialized agents working concurrently with isolated context.

295.4K 206.3K
View

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

179.7K 100.1K
View

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

179.7K 89.5K
View

A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).

179.7K 76.1K
View

Fundamental design principles for writing maintainable, testable Python code.

40.2K 21.9K
View

Modern responsive layouts using container queries, fluid typography, CSS Grid, and mobile-first strategies.

40.2K 20K
View

Generate Playwright tests from scenarios using interactive browser exploration and validation.

39.7K 18.2K
View

Modern React state management with Redux Toolkit, Zustand, Jotai, and React Query for every state category.

40.2K 14.7K
View

GDPR-compliant data handling with consent management, data subject rights, and privacy controls.

40.2K 14.3K
View

Python error handling patterns including input validation, exception hierarchies, and partial failure handling. Use when implementing validation logic, designing exception strategies, handling batch processing failures, or building robust APIs.

40.2K 13.5K
View

Detailed multi-file refactor planning with safety checks and rollback guidance.

39.7K 13K
View