Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
.claude/skills/bitwize-music-studio-configure/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-04 | ✗→✓ | ▲ Improved | 201% | 0% |
| case-05 | ✗→✓ | ▲ Improved | 58% | 0% |
| case-07 | ✗→✓ | ▲ Improved | 113% | 0% |
| case-09 | ✗→✓ | ▲ Improved | 115% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 141% | 0% |
Input: $ARGUMENTS
Route based on argument:
setup or no argument → Interactive first-time setupedit → Edit specific settingsshow → Display current configurationvalidate → Check config for issuesreset → Delete config and start freshYou help users set up and manage their ~/.bitwize-music/config.yaml configuration.
~/.bitwize-music/config.yaml/configure or /configure setupInteractive first-time setup. Guide user through creating their config.
Steps:
~/.bitwize-music/config.yaml exists~/.bitwize-music/ directory if neededRequired settings to ask:
artist.name - "What's your artist/project name?"paths.content_root - "Where should albums and projects be stored? (e.g., ~/music-projects)"paths.audio_root - "Where should mastered audio files go? (e.g., ~/music-projects/audio)"paths.documents_root - "Where should research documents/PDFs go? (e.g., ~/music-projects/documents)"Optional settings:
artist.genres - "What are your primary genres? (comma-separated, or skip)"urls.soundcloud - "SoundCloud profile URL? (or skip)"Step 5: Overrides Directory (Optional)
Ask: > You can optionally provide a path to a directory containing override files. > This is where you can customize workflows and skills without plugin update conflicts. > > Override files you can create: > - CLAUDE.md (custom workflow instructions) > - pronunciation-guide.md (artist names, character names) > - explicit-words.md (custom explicit word list) > > Default: ~/music-projects/overrides > > Enter path (or press Enter to use default):
If user provides path:
paths.overrides: "[user-path]"If user presses Enter (accepts default):
paths.overrides: "~/music-projects/overrides"Step 6: Album Ideas File (Optional)
Ask: > You can optionally provide a path to a file for tracking album ideas. > This is managed by the /bitwize-music:album-ideas skill for brainstorming and planning. > > Default: ~/music-projects/IDEAS.md > > Enter path (or press Enter to use default):
If user provides path:
paths.ideas_file: "[user-path]"If user presses Enter (accepts default):
paths.ideas_file: "~/music-projects/IDEAS.md"Example interaction:
Let's set up your bitwize-music configuration.
What's your artist/project name?
> Neon Circuits
Where should albums and projects be stored?
(This is where your album folders, lyrics, and research will live)
> ~/music-projects
Where should mastered audio files go?
> ~/music-projects/audio
Where should research documents/PDFs go?
> ~/music-projects/documents
What are your primary genres? (comma-separated, or press Enter to skip)
> electronic, synthwave
SoundCloud profile URL? (or press Enter to skip)
> https://soundcloud.com/neon-circuits
Overrides directory path? (press Enter for default: ~/music-projects/overrides)
> [Enter]
Album ideas file path? (press Enter for default: ~/music-projects/IDEAS.md)
> [Enter]
Creating config at ~/.bitwize-music/config.yaml...
✓ Configuration saved!
Your settings:
Artist: Neon Circuits
Content: ~/music-projects
Audio: ~/music-projects/audio
Documents: ~/music-projects/documents
Genres: electronic, synthwave
SoundCloud: https://soundcloud.com/neon-circuits
Overrides: ~/music-projects/overrides (will be used if created)
Ideas File: ~/music-projects/IDEAS.md (will be created when first used)
You're ready to start creating albums!/configure editEdit specific settings without recreating the whole config.
Steps:
Example:
Current configuration:
artist.name: Neon Circuits
paths.content_root: ~/music-projects
paths.audio_root: ~/music-projects/audio
paths.documents_root: ~/music-projects/documents
artist.genres: [electronic, synthwave]
urls.soundcloud: https://soundcloud.com/neon-circuits
What would you like to change?/configure showDisplay the current configuration in a readable format.
Steps:
~/.bitwize-music/config.yamlExample output:
bitwize-music Configuration
Location: ~/.bitwize-music/config.yaml
┌─────────────────────┬────────────────────────────────────┐
│ Setting │ Value │
├─────────────────────┼────────────────────────────────────┤
│ artist.name │ Neon Circuits │
│ artist.genres │ electronic, synthwave │
│ paths.content_root │ ~/music-projects │
│ paths.audio_root │ ~/music-projects/audio │
│ paths.documents_root│ ~/music-projects/documents │
│ paths.overrides │ ~/music-projects/overrides │
│ paths.ideas_file │ ~/music-projects/IDEAS.md │
│ urls.soundcloud │ https://soundcloud.com/neon-circuits│
│ generation.service │ suno │
└─────────────────────┴────────────────────────────────────┘
✓ All required settings present/configure validateCheck the config for issues.
Checks:
Example output:
Validating ~/.bitwize-music/config.yaml...
✓ Config file exists
✓ artist.name: Neon Circuits
✓ paths.content_root: ~/music-projects (exists)
✓ paths.audio_root: ~/music-projects/audio (exists)
✓ paths.documents_root: ~/music-projects/documents (will be created)
✓ paths.overrides: ~/music-projects/overrides (will be used if created)
✓ paths.ideas_file: ~/music-projects/IDEAS.md (will be created when first used)
✓ generation.service: suno
All checks passed!Or with issues:
Validating ~/.bitwize-music/config.yaml...
✓ Config file exists
✓ artist.name: Neon Circuits
✗ paths.content_root: not set (required)
✓ paths.audio_root: ~/music-projects/audio
✗ paths.documents_root: /invalid/path (directory doesn't exist)
2 issues found. Run /configure edit to fix./configure resetDelete config and optionally start fresh.
Steps:
config.yaml.bak~/.bitwize-music/config.yamlExample:
⚠️ This will delete your configuration at ~/.bitwize-music/config.yaml
Current config will be backed up to config.yaml.bak
Are you sure you want to reset? (yes/no)If yes:
✓ Backed up to ~/.bitwize-music/config.yaml.bak
✓ Deleted ~/.bitwize-music/config.yaml
Config has been reset.
Would you like to set up a new config now? (yes/no)When creating a new config, use this structure:
yaml# bitwize-music Plugin Configuration # Generated by /configure artist: name: "{artist_name}" genres: - "{genre1}" - "{genre2}" paths: content_root: "{content_root}" audio_root: "{audio_root}" documents_root: "{documents_root}" overrides: "{overrides}" ideas_file: "{ideas_file}" urls: soundcloud: "{soundcloud_url}" generation: service: suno
config.yaml.bak./projects → /Users/name/projects~ prefix: ~/projects~ in paths for display| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 7,262 | 5,486 | -24% | 1 | 1 | 0% | 1,151 | 2,976 | +159% | 0 | 0 | — |
case-02 | fail→fail | 13,798 | 3,475 | -75% | 1 | 1 | 0% | 2,743 | 2,711 | -1% | 0 | 0 | — |
case-03 | fail→fail | 4,547 | 2,862 | -37% | 1 | 1 | 0% | 832 | 2,601 | +213% | 0 | 0 | — |
case-04 | fail→pass | 5,971 | 7,098 | +19% | 1 | 1 | 0% | 1,253 | 3,772 | +201% | 0 | 0 | — |
case-05 | fail→pass | 12,375 | 3,976 | -68% | 1 | 1 | 0% | 1,868 | 2,954 | +58% | 0 | 0 | — |
case-06 | fail→fail | 8,221 | 4,069 | -51% | 1 | 1 | 0% | 1,586 | 3,097 | +95% | 0 | 0 | — |
case-07 | fail→pass | 7,986 | 3,293 | -59% | 1 | 1 | 0% | 1,298 | 2,763 | +113% | 0 | 0 | — |
case-08 | pass→pass | 11,189 | 5,018 | -55% | 1 | 1 | 0% | 1,985 | 3,209 | +62% | 0 | 0 | — |
case-09 | fail→pass | 9,705 | 5,746 | -41% | 1 | 1 | 0% | 1,553 | 3,335 | +115% | 0 | 0 | — |
case-10 | fail→pass | 7,542 | 4,277 | -43% | 1 | 1 | 0% | 1,230 | 2,969 | +141% | 0 | 0 | — |
case-11 | fail→pass | 10,768 | 2,381 | -78% | 1 | 1 | 0% | 1,699 | 2,760 | +62% | 0 | 0 | — |
case-12 | fail→pass | 9,112 | 2,473 | -73% | 1 | 1 | 0% | 1,372 | 2,776 | +102% | 0 | 0 | — |
case-13 | fail→pass | 9,791 | 5,328 | -46% | 1 | 1 | 0% | 923 | 3,329 | +261% | 0 | 0 | — |
case-14 | fail→pass | 5,602 | 2,792 | -50% | 1 | 1 | 0% | 831 | 2,746 | +230% | 0 | 0 | — |
case-15 | fail→pass | 7,394 | 2,152 | -71% | 1 | 1 | 0% | 1,181 | 2,709 | +129% | 0 | 0 | — |
case-16 | fail→pass | 7,078 | 1,845 | -74% | 1 | 1 | 0% | 1,086 | 2,633 | +142% | 0 | 0 | — |
case-17 | pass→pass | 11,576 | 3,428 | -70% | 1 | 1 | 0% | 1,906 | 2,963 | +55% | 0 | 0 | — |
case-18 | fail→fail | 3,975 | 2,379 | -40% | 1 | 1 | 0% | 533 | 2,669 | +401% | 0 | 0 | — |
case-19 | pass→pass | 7,808 | 1,498 | -81% | 1 | 1 | 0% | 1,412 | 2,495 | +77% | 0 | 0 | — |
case-20 | pass→pass | 13,604 | 17,153 | +26% | 1 | 1 | 0% | 2,180 | 5,329 | +144% | 0 | 0 | — |
case-21 | pass→pass | 12,722 | 8,438 | -34% | 1 | 1 | 0% | 2,090 | 3,752 | +80% | 0 | 0 | — |
case-22 | pass→pass | 12,743 | 11,685 | -8% | 1 | 1 | 0% | 2,002 | 3,846 | +92% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +50 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.