Agent skill · Audited from source
Import Track
skill · bitwize-music-studio/claude-ai-music-skillsCC0-1.0 licenceAudited 31 Oct 2026 · source 3e049bfcc994
Is it safe? Yes — SAFE, grade B (89/100). We read this skill's source at commit 3e049bfcc994 and found no filesystem, network or shell access and no hard-coded secrets. What it does: 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.
Cite
Cite this page
ModelsAtlas. “Import Track (bitwize-music-studio/claude-ai-music-skills)”. Retrieved 31 Oct 2026. https://modelsatlas.com/skills/bitwize-music-studio/import-track
Trust audit
Audit 0.4.1 · source read 31 Oct 2026
SAFE means nothing in the source contradicts what the skill says it does. Grade B is shared by 16,667 of 17,602 audited skills.
What the source does
- FilesystemNone observedNo reads or writes in the source
- NetworkNone observedNo outbound calls in the source
- ShellNone observedNo commands run in the source
- DependenciesPinnedNothing floats
- SecretsNone foundNo keys in source
Five audit layers
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | PASS | 0 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (0)
No findings at any severity. We re-audit when the source changes.
Audit 0.4.1 · source sha 3e049bfcc994 · 31 Oct 2026Report an issue or request a re-scan
Provenance
Who published it, and what the verdict is pinned to
- Publisherbitwize-music-studio GitHub organizationOwner of the repository this skill is read from
- Source folderbitwize-music-studio/claude-ai-music-skills/skills/import-trackThe exact folder we audited
- LicenceCC0-1.0As the repository states it
- Commit pinned for this verdict3e049bfcc994A new audit runs when the source changes
- Repository statusNot archivedLast push 2 days ago
- Sandboxed runNot runSkills are read, not executed; layer L4 is skipped
What it tells the agent
Full source on GitHub ↗Its 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.
---
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
---
## 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.Excerpt, first 4,931 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.
Install
Pinned to the audited commit 3e049bf
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills git -C claude-ai-music-skills checkout 3e049bfcc994
The author documents no install command, so this uses the repository directly. Our verdict covers commit 3e049bfcc994 only.
Works in
The author has not said which agents this skill supports, and we have not tested it in any.
Audit history
Every audit, every source change
- ✓SAFE B 89 / 100
first audit · source
3e049bfcc994
Similar skills
bitwize-music-studio/claude-ai-music-skills
Searches and retrieves documents from free public sources using automated browser navigation. Use when research needs primary source documents like court filings, government reports, or public records.
bitwize-music-studio/claude-ai-music-skills
Scans lyrics for explicit content and verifies that explicit flags match actual content. Use before Suno generation or release to ensure accurate content ratings.
bitwize-music-studio/claude-ai-music-skills
Shows available skills, common workflows, and quick reference for the plugin. Use when the user asks for help, what skills are available, or how to do something.
bitwize-music-studio/claude-ai-music-skills
Places album art files in the correct audio and content directory locations. Use when the user has generated or downloaded album artwork that needs to be saved.
bitwize-music-studio/claude-ai-music-skills
Moves audio files to the correct album location with proper path structure. Use when the user has downloaded WAV files from Suno or other sources that need to be organized.
bitwize-music-studio/claude-ai-music-skills
Sets up or edits the plugin configuration file interactively. Use on first-time setup, when config is missing, or when the user wants to change settings.
Questions about Import Track
What does the Import Track skill do?
Is Import Track safe to install?
What can Import Track access on my machine?
How current is this page?
Sources
- github.com/bitwize-music-studio/claude-ai-music-skills/tree/main — the audited source at commit 3e049bfcc994 and every finding aboveObserved · 31 Oct 2026
Spotted something wrong? Report a correction · Methodology
Keep going in your AI
Opens with this page as the source. We add nothing else to the prompt.
- What does the Import Track skill do?
- Is Import Track safe to install?
- What can Import Track access on my machine?