import-art
npx machina-cli add skill bitwize-music-studio/claude-ai-music-skills/import-art --openclawYour 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
- Call
find_album(album_name)— fuzzy match, returns album metadata including genre - Call
resolve_path("audio", album_slug)— returns audio directory path - 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):
- Audio folder (for platforms/mastering):
{audio_path}/album.png - Content folder (for documentation):
{content_path}/album-art.{ext}
CRITICAL: resolve_path includes the artist folder automatically.
Step 4: Create Directories and Copy Files
# 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:
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:
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:
# Only copying to audio folder
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
# Missing: content folder copy
Right:
# 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:
# 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:
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:
# Copying without ensuring directory exists
cp art.png {audio_root}/artists/{artist}/albums/{genre}/{album}/album.png
# Fails if directory doesn't exist
Right:
# 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.
Source
git clone https://github.com/bitwize-music-studio/claude-ai-music-skills/blob/main/skills/import-art/SKILL.mdView on GitHub Overview
Imports album art to both the audio folder and the album content folder. It uses MCP to locate the album, resolve the audio and content paths, and then copies the image to album.png in the audio directory and album-art.ext in the content directory, preserving the artist/album structure.
How This Skill Works
Parse the input as <file-path> <album-name>, locate the album with find_album, resolve both paths with resolve_path for audio and content, then copy the source image to the audio path as album.png and to the content path as album-art.ext. The MCP workflow automatically includes the artist folder and genre in the target paths.
When to Use It
- You downloaded or generated album art and want to save it in both audio and documentation folders for an existing album.
- You are adding art for a new or existing album and need the artwork placed consistently in both platforms.
- You want the audio copy to be named album.png while the docs copy preserves the original extension as album-art.ext.
- You are scripting a batch import for multiple albums and require MCP to resolve paths for each one.
- You need to verify that artwork will be stored under the correct artist/genre/album structure automatically.
Quick Start
- Step 1: /import-art <file-path> <album-name>
- Step 2: If album not found, create it with /new-album <album-name> <genre> and retry
- Step 3: Confirm the output shows both targeted paths for audio and content
Best Practices
- Ensure the source file exists and is an image with an allowed extension (.jpg, .jpeg, .png, .webp).
- Let find_album and resolve_path handle metadata and path construction rather than manual path building.
- Copy to audio as album.png and to content as album-art.{ext} to maintain consistency.
- After import, confirm that both destinations exist and reflect the new artwork.
- If the album is not found, create it first with /new-album <album-name> <genre> before retrying.
Example Use Cases
- /import-art ~/Downloads/sample-album-cover.jpg sample-album
- /import-art ~/Downloads/cover.png sample-album
- Album found at: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/; art imported for: sample-album
- Copied to audio: ~/bitwize-music/audio/artists/bitwize/albums/electronic/sample-album/album.png
- Copied to docs: ~/bitwize-music/artists/bitwize/albums/electronic/sample-album/album-art.jpg