skills/import-art/SKILL.md
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.
npx skillsauth add bitwize-music-studio/claude-ai-music-skills import-artInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Input: $ARGUMENTS
Import album art to both the audio folder and album content folder.
You copy album art to both required locations based on config.
Expected format: <file-path> <album-name>
Examples:
~/Downloads/album-art.jpg sample-album~/Downloads/cover.png sample-albumIf arguments are missing, ask:
Usage: /import-art <file-path> <album-name>
Example: /import-art ~/Downloads/album-art.jpg sample-album
find_album(album_name) — fuzzy match, returns album metadata including genreresolve_path("audio", album_slug) — returns audio directory pathresolve_path("content", album_slug) — returns content directory pathIf album not found:
Error: Album "{album-name}" not found.
Create it first with: /new-album {album-name} <genre>
TWO destinations required (paths from MCP resolve_path calls):
{audio_path}/album.png{content_path}/album-art.{ext}CRITICAL: resolve_path includes the artist folder automatically.
# 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}"
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)
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)
/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)
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.
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.
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.
Wrong:
find . -name "README.md" -path "*albums/$album_name*"
Right:
find_album(album_name) → returns album data including path and genre
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.
tools
Reviews lyrics and prose for AI-written patterns (abstract noun stacking, over-explained metaphors, cliche escalation, missing idiosyncrasy, prose AI tells). Advisory Warning/Info severity — flags issues, does not block or rewrite. Use when reviewing lyrics for authenticity or before generation to catch AI-sounding language.
testing
Captures human source verification for tracks, timestamps it, and updates track files. Use when sources need human review before generation.
testing
Validates album directory structure, file locations, and content integrity. Use before release or whenever the user wants to check an album's structural health.
tools
Provides interactive guided album creation for new users. Use when the user is new to the plugin or asks for a walkthrough of the album creation process.