Import Track logo

Import Track

Organization
bitwize-music-studio
import-track

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.

Overview

Publisherbitwize-music-studio
Repositoryclaude-ai-music-skills
Skill nameimport-track
Stars
546
Forks
130
Bundled files
Instructions only
LicenseCC0-1.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by bitwize-music-studio on GitHub. Read the source before you install it.

Installation

Install the Import Track AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/import-track
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git /tmp/claude-ai-music-skills
mkdir -p .claude/skills
cp -r /tmp/claude-ai-music-skills/skills/import-track .claude/skills/import-track
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Import Track in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Import Track on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Import Track is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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.

Frequently asked questions

What does the Import Track AI skill do?

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.

Why use Import Track on TypingMind?

Because you install it once and use it with any model. Import Track is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Import Track in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/import-track. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Import Track?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Import Track?

As many as you like. As long as a model supports skills, you can use Import Track with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Import Track AI skill free?

Yes. It is published on GitHub by bitwize-music-studio under the CC0-1.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇