import-art — Claude Code skill: what it does, how to install
import-art distributes album artwork into audio and content folders using standard naming conventions. Useful right after generating or downloading a cover.
CC0-1.0 252 installs ★ 686 updated 2026-10-22
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a claude-codeWhat import-art does
The skill accepts an image path along with an album name. It calls the bitwize-music-mcp tool functions find_album and resolve_path to locate metadata, artist subdirectories, and genre paths without guessing folder structures manually.
Two targets receive the file during each run. The audio directory gets album.png for digital stores and mastering packages. Meanwhile, the documentation directory gets album-art.{ext} while keeping the original file extension.
Execution relies strictly on the bitwize-music-mcp tool and an existing ~/.bitwize-music/config.yaml file: path resolution will fail if the configuration is missing.
What it helps with
- place album artwork into both audio and content folders at once
- standardize art filenames to
album.pngandalbum-art.{ext}automatically - create missing artist and genre directories before file transfers
Example prompts for the agent
- /import-art ~/Downloads/album-art.jpg sample-album
- Save the artwork from ~/Downloads/cover.png to the album sample-album
How to install import-art
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a claude-code2Manually: put the files in place
~/.claude/skills/import-art/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/import-art/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a codex2Manually: put the files in place
.agents/skills/import-art/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a cursor2Manually: put the files in place
.cursor/skills/import-art/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install bitwize-music-studio/claude-ai-music-skills skills/import-art2Manually: put the files in place
.github/skills/import-art/SKILL.md1Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a gemini-cli2Platform CLI
gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills --path skills/import-artManually: put the files in place
.devin/skills/import-art/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about import-art
How to install import-art in Claude Code?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill import-art -a claude-code in your terminal.
What does import-art do?
It uses an MCP server to look up album paths and duplicates the given artwork file into your audio and content directories.
What dependencies does import-art require?
You need the bitwize-music-mcp server configured, plus a valid ~/.bitwize-music/config.yaml settings file.
Source text
SKILL.md · CC0-1.0
---
name: import-art
description: 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.
argument-hint: <file-path> <album-name>
model: haiku
allowed-tools:
- Read
- Bash
- Glob
- bitwize-music-mcp
---
## Your Task
**Input**: $ARGUMENTS
Import album art to both the audio folder and album content folder.
---
# Import Art Skill
You copy album art to both required locations based on config.
## Step 1: Parse Arguments
Expected format: `<file-path> <album-name>`
Examples:
- `~/Downloads/album-art.jpg sample-album`
- `~/Downloads/cover.png sample-album`
If arguments are missing, ask:
```
Usage: /import-art <file-path> <album-name>
Example: /import-art ~/Downloads/album-art.jpg sample-album
```
## Step 2: Find Album and Resolve Paths via MCP
1. Call `find_album(album_name)` — fuzzy match, returns album metadata including genre
2. Call `resolve_path("audio", album_slug)` — returns audio directory path
3. Call `resolve_path("content", album_slug)` — returns content directory path
If album not found:
```
Error: Album "{album-name}" not found.
Create it first with: /new-album {album-name} <genre>
```
## Step 3: Construct Target Paths
**TWO destinations required** (paths from MCP `resolve_path` calls):
1. **Audio folder** (for platforms/mastering): `{audio_path}/album.png`
2. **Content folder** (for documentation): `{content_path}/album-art.{ext}`
**CRITICAL**: `resolve_path` includes the artist folder automatically.
## Step 4: Create Directories and Copy Files
```bash
# Create audio directory (includes artist folder!)
mkdir -p {audio_root}/artists/{artist}/albums/{genre}/{album}
# Copy to audio folder as album.png
cp "{source_file}" "{audio_root}/artists/{artist}/albums/{genre}/{album}/album.png"
# Copy to content folder preserving extension
cp "{source_file}" "{content_root}/artists/{artist}/albums/{genre}/{album}/album-art.{ext}"
```
## Step 5: Confirm
Report:
```
Album art imported for: {album-name}
Copied to:
1. {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png (for platforms)
2. {content_root}/artists/{artist}/albums/{genre}/{album}/album-art.{ext} (for docs)
```
## 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>
```
**Not an image file:**
```
Warning: File doesn't appear to be an image: {source_file}
Expected: .jpg, .jpeg, .png, .webp
Continue anyway? (y/n)
```
---
## Examples
```
/import-art ~/Downloads/sample-album-cover.jpg sample-album
```
Config has:
```yaml
paths:
content_root: ~/bitwize-music
audio_root: ~/bitwize-music/audio
artist:
name: bitwize
```
Album found at: `~/bitwize-music/artists/bitwize/albums/electronic/sample-album/`
Result:
```
Album art imported for: sample-album
Copied to:
1. ~/bitwize-music/audio/artists/bitwize/albums/electronic/sample-album/album.png (for platforms)
2. ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/album-art.jpg (for docs)
```
---
## Common Mistakes
### ❌ Don't: Manually read config and construct paths
**Wrong:**
```bash
cat ~/.bitwize-music/config.yaml
cp art.png ~/music-projects/audio/sample-album/
```
**Right:**
```
# Use MCP to find album and resolve both paths
find_album(album_name) → returns album metadata
resolve_path("audio", album_slug) → audio path with artist folder
resolve_path("content", album_slug) → content path with genre
```
**Why it matters:** `resolve_path` handles config reading, artist folder, and genre resolution automatically.
### ❌ Don't: Place art in only one location
**Wrong:**
```bash
# Only copying to audio folder
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
# Missing: content folder copy
```
**Right:**
```bash
# Copy to BOTH locations
# 1. Audio location (for streaming platforms)
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
# 2. Content location (for documentation)
cp art.jpg {album_path}/album-art.jpg
```
**Why it matters:** Album art needs to be in both locations - audio folder for release, content folder for documentation.
### ❌ Don't: Mix up the filenames
**Wrong:**
```bash
# Using same filename in both locations
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album-art.png
cp art.png {album_path}/album.png
```
**Correct naming:**
```
Audio location: album.png (or album.jpg)
Content location: album-art.jpg (or album-art.png)
```
**Why it matters:** Different locations use different naming conventions to avoid confusion.
### ❌ Don't: Search for albums manually
**Wrong:**
```bash
find . -name "README.md" -path "*albums/$album_name*"
```
**Right:**
```
find_album(album_name) → returns album data including path and genre
```
### ❌ Don't: Forget to create directories
**Wrong:**
```bash
# Copying without ensuring directory exists
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
# Fails if directory doesn't exist
```
**Right:**
```bash
# Create directory first
mkdir -p {audio_root}/artists/{artist}/albums/{genre}/{album}/
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
```
**Why it matters:** Audio directory might not exist yet, especially for new albums.
© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills