import-track
Skill589 starsChanged 9 months agoCC0-1.0View on GitHub
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.
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 4 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Import a track markdown file (.md) to the correct album location based on config.
- Distinctive: line 34
If arguments are missing, ask:
- Very specific: line 43
Call find_album(album_name) — fuzzy match by name, slug, or partial.
- Very specific: line 44
Call resolve_path("tracks", album_slug) — returns the full tracks directory path
- Distinctive: line 46
If album not found, MCP returns available albums:
- Very specific: line 78
If track number provided, use it (zero-padded: 03)
- Very specific: line 79
If filename already has number prefix (e.g., 03-name.md), preserve it
- Distinctive: line 80
If neither, ask user for track number
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 03Step 2: Find Album and Resolve Path via MCP
- Call
find_album(album_name)— fuzzy match by name, slug, or partial. Returns album metadata including genre. - 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}.mdExample with:
content_root: ~/bitwize-musicartist: bitwizegenre: electronic(found from album location)album: sample-albumtrack-number: 03track-name: t-day-beach
Result:
~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/03-t-day-beach.mdTrack 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 03Config has:
paths:
content_root: ~/bitwize-music
artist:
name: bitwizeAlbum 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.mdCommon Mistakes
❌ Don't: Manually read config and search for albums
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 pathWhy 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.mdCorrect destination:
{album_path}/tracks/01-track.md
# Example: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/tracks/01-track.mdWhy it matters: Tracks always go in the tracks/ subdirectory within the album folder.
❌ 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.mdRight:
# Ensure zero-padding
track_num=$(printf "%02d" $track_num)
mv track.md {album_path}/tracks/$track_num-track.md
# Results in: 03-track.mdWhy 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:
# Use MCP to find the album (handles genre resolution)
find_album(album_name) → returns album metadata including genre and pathWhy it matters: Albums are organized by genre. find_album resolves the genre automatically.
In this repository53 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- aboutSkill
- album-art-directorSkill
- album-conceptualizerSkill
- album-dashboardSkill
- album-ideasSkill
- clipboardSkill
- cloud-uploaderSkill
- configureSkill
- document-hunterSkill
- explicit-checkerSkill
- genre-creatorSkill
- health-checkSkill
- helpSkill
- import-artSkill
- import-audioSkill
- lyric-refinerSkill
- lyric-reviewerSkill
- lyric-writerSkill
- mastering-engineerSkill
- mix-engineerSkill
- new-albumSkill
- next-stepSkill
- plagiarism-checkerSkill
- pre-generation-checkSkill
- promo-directorSkill
- promo-reviewerSkill
- promote-ideaSkill
- promo-writerSkill
- pronunciation-specialistSkill
- release-directorSkill
- renameSkill
- researchers-biographicalSkill
- researchers-financialSkill
- researchers-govSkill
- researchers-historicalSkill
- researchers-journalismSkill
- researcherSkill
- researchers-legalSkill
- researchers-primary-sourceSkill
- researchers-securitySkill
- researchers-techSkill
- researchers-verifierSkill
- resumeSkill
- session-startSkill
- setupSkill
- sheet-music-publisherSkill
- suno-engineerSkill
- testSkill
- tutorialSkill
- validate-albumSkill
- verify-sourcesSkill
- voice-checkerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

