Skip to main content
skill CX Codex

configure · bitwize-music-studio — Claude Code skill: what it does, how to install

configure is a Claude Code skill that interactively creates, edits, and checks the ~/.bitwize-music/config.yaml configuration file.

CC0-1.0 247 installs ★ 686 updated 2026-10-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a claude-code
Open on GitHub

What configure does

The skill manages ~/.bitwize-music/config.yaml for bitwize-music tools. When run without arguments or with setup, it prompts for the artist name, storage paths for projects, mastered audio, and documentation files. It also accepts optional items like SoundCloud profile links and music genres.

Under the hood, the skill relies on tools like Read, Write, AskUserQuestion, and Bash. It supports checking paths and YAML syntax with validate, inspecting active values via show, modifying individual keys with edit, or wiping everything with reset. Validation will fail if required paths or artist names are missing from the YAML file.

What it helps with

  • set up ~/.bitwize-music/config.yaml through an interactive prompt
  • update single config keys without editing YAML manually
  • check directory paths and YAML syntax with validation checks
  • display current music workspace paths and artist settings

Example prompts for the agent

  • /configure setup
  • /configure show
  • /configure validate

How to install configure

1Skills CLI (Vercel)

npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a claude-code

2Manually: put the files in place

~/.claude/skills/configure/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/configure/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about configure

How to install configure in Claude Code?

Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a claude-code in your terminal.

What does the configure skill do?

It steps through an interactive questionnaire to generate or modify your ~/.bitwize-music/config.yaml setup.

Which settings are required during setup?

You must provide artist.name, paths.content_root, paths.audio_root, and paths.documents_root.

Source text

SKILL.md · CC0-1.0
---
name: configure
description: 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.
argument-hint: "[setup | edit | show | validate | reset]"
model: sonnet
effort: low
allowed-tools:
  - Read
  - Write
  - Bash
  - AskUserQuestion
  - Glob
---

## Your Task

**Input**: $ARGUMENTS

Route based on argument:
- `setup` or no argument → Interactive first-time setup
- `edit` → Edit specific settings
- `show` → Display current configuration
- `validate` → Check config for issues
- `reset` → Delete config and start fresh

---

# Plugin Configuration Skill

You help users set up and manage their `~/.bitwize-music/config.yaml` configuration.

## Config Location

```
~/.bitwize-music/config.yaml
```

## Commands

### `/configure` or `/configure setup`

Interactive first-time setup. Guide user through creating their config.

**Steps:**

1. Check if `~/.bitwize-music/config.yaml` exists
2. If exists, ask if they want to overwrite or edit instead
3. If creating new:
   - Create `~/.bitwize-music/` directory if needed
   - Ask for each required setting interactively
   - Write the config file
   - Validate the result

**Required settings to ask:**
1. `artist.name` - "What's your artist/project name?"
2. `paths.content_root` - "Where should albums and projects be stored? (e.g., ~/music-projects)"
3. `paths.audio_root` - "Where should mastered audio files go? (e.g., ~/music-projects/audio)"
4. `paths.documents_root` - "Where should research documents/PDFs go? (e.g., ~/music-projects/documents)"

**Optional settings:**
5. `artist.genres` - "What are your primary genres? (comma-separated, or skip)"
6. `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:
- Add to config: `paths.overrides: "[user-path]"`

If user presses Enter (accepts default):
- Add to config: `paths.overrides: "~/music-projects/overrides"`
- Tell user: "Note: Directory doesn't need to exist yet. Create override files when you want to customize."

**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:
- Add to config: `paths.ideas_file: "[user-path]"`

If user presses Enter (accepts default):
- Add to config: `paths.ideas_file: "~/music-projects/IDEAS.md"`
- Tell user: "Note: File doesn't need to exist yet. The album-ideas skill creates it when first used."

**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 edit`

Edit specific settings without recreating the whole config.

**Steps:**
1. Read existing config
2. Show current values
3. Ask what they want to change
4. Update just that setting
5. Validate and save

**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 show`

Display the current configuration in a readable format.

**Steps:**
1. Read `~/.bitwize-music/config.yaml`
2. Display all settings in a formatted table
3. Note any missing required settings

**Example 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 validate`

Check the config for issues.

**Checks:**
1. Config file exists
2. All required fields present
3. Paths are valid (directories exist or can be created)
4. No syntax errors in YAML

**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 reset`

Delete config and optionally start fresh.

**Steps:**
1. Confirm user really wants to reset
2. Back up existing config to `config.yaml.bak`
3. Delete `~/.bitwize-music/config.yaml`
4. Ask if they want to run setup now

**Example:**
```
⚠️  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)
```

---

## Config Template

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
```

---

## Edge Cases

### Config exists but is invalid YAML
- Back up the existing file: `config.yaml.bak`
- Offer to create fresh config

### Directory doesn't exist
- Offer to create it: "Directory ~/music-projects doesn't exist. Create it?"

### User provides relative path
- Expand to absolute: `./projects` → `/Users/name/projects`
- Or use `~` prefix: `~/projects`

---

## Remember

- **Preserve exact casing** - If user says "bitwize", write "bitwize" not "Bitwize"
- Always expand `~` in paths for display
- Create directories if they don't exist (with permission)
- Back up existing config before overwriting
- Validate after any changes
- Be friendly and explain what each setting does

© bitwize-music-studio · CC0-1.0 · bitwize-music-studio/claude-ai-music-skills

Similar skills

All skills for Agent setup: memory, context, orchestration →

configure by other authors comes first.

configure official anthropics configure saves a Telegram bot token and reviews access policy. Use it when setting up the channel or checking who can reach the bot. CX Codex +1 3,861installs configure official anthropics configure is a Claude Code skill that checks iMessage setup and audits access rules. It helps diagnose messages that fail to reach the assistant and identify allowed contacts. CX Codex +1 3,861installs configure official anthropics configure sets up the Discord channel for Claude Code by storing the bot token and enforcing allowlist access rules. CX Codex +1 3,861installs configure OrchestKit Interactive wizard for OrchestKit settings: MCP servers, hook permissions, keybindings, presets. Runs on first install and via /orchestkit:configure. CX Codex +1 196installs configure Rich627 Configures WhatsApp channel connections via Baileys linked devices or the official Cloud API directly in the terminal. CX Codex +1 ★ 127repo stars codometer-configure organizzolini The codometer-configure skill edits codometer.config.ts for Codometer, covering inputs, metric limits, exclusions, and report destinations. CX Codex +1 363installs openspec-bootstrap sammcj openspec-bootstrap sets up OpenSpec in a repository by preparing its schema and config. Use it for a first-time setup or edits to openspec/config.yaml. CX Codex +1 ★ 173repo stars grepai-config-reference yoanbernabeu grepai-config-reference documents every option in the .grepai/config.yaml file: embedder, storage backend, chunking, call-graph tracing and ignore rules. CX Codex +1 727installs config calesthio Covers how ManimGL reads custom_config.yml: output folders, camera and window options, styles. An agent edits the right keys instead of guessing. CX Codex +1 ★ 78,316repo stars confdiff-mcp esperanza-volkov confdiff-mcp diffs config files by parsed data instead of characters. Your agent sees the real changes and never gets the secrets. CX Codex +1 ★ 41repo stars ce-setup EveryInc ce-setup — a Claude Code skill that inspects Compound Engineering tools, fixes repository configuration, scaffolds packs, and refreshes code standards. Runs during setup or as a scheduled CI job. CX Codex +1 3,600installs

From the same set52

The whole set →
genre-creator The genre-creator skill builds documentation for a music genre and updates the library index and mastering presets. Use it when adding a genre to bitwize-music. CX Codex +1 248installs validate-album validate-album is a Claude Code skill that checks album directories, audio file paths, and track metadata before release. CX Codex +1 248installs researchers-financial researchers-financial is a Claude Code skill that researches financial records and market data for music projects about companies, financial crime, or market events. It gathers sources and marks claims for human review. CX Codex +1 248installs next-step next-step analyzes music album progress and recommends the single best next action with the exact command to run. CX Codex +1 247installs cloud-uploader cloud-uploader is a skill for uploading album promo videos and samplers to Cloudflare R2 or AWS S3 after the videos are created. CX Codex +1 247installs resume resume finds an album by name and displays its status with a concrete next step. Use when returning to an unfinished project or checking where an album stands in its workflow. CX Codex +1 246installs researchers-primary-source The researchers-primary-source skill gathers statements from tweets, blogs, forums and chat logs. Use it when you need direct quotes or first-hand accounts instead of paraphrased reporting. CX Codex +1 246installs promote-idea promote-idea turns a pending album concept in IDEAS.md into a project with one command. Use it when an idea is ready to move into album planning. CX Codex +1 188installs

Project sponsors

Companies that keep this analytics open