configure
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.
Install / Use
npx skills add bitwize-music-studio/claude-ai-music-skills --skill configureInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Tags
Our assessment of configure
configure scores 90/100 on our quality scale, 1440th of 4,717 Development & Engineering skills we index (top 31%).
Its SKILL.md is 8.6 KB long, well organised into 17 sections with 9 code examples: a thorough specification that gives an agent plenty to work with.
It has 512 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so configure is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the CC0-1.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
configure compared with similar skills
All 4 of these similar skills score higher than configure; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| configure (this skill)by bitwize-music-studio | 90 | 512 | 56d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 118.3k | 10d ago | CLAUDE.md |
| hyperframesby heygen-com | 100 | 86.4k | today | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.4k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.4k | 4d ago | CLAUDE.md |
Frequently asked questions
- How do I install configure?
- Run
npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure. The install tabs above show the steps for each supported agent. - Which AI agents does configure work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is configure safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is CC0-1.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is configure still maintained?
- The repository was last updated about 2 months ago, so configure is actively maintained.
Skill content
View source on GitHubname: 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:
setupor no argument → Interactive first-time setupedit→ Edit specific settingsshow→ Display current configurationvalidate→ Check config for issuesreset→ 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:
- Check if
~/.bitwize-music/config.yamlexists - If exists, ask if they want to overwrite or edit instead
- If creating new:
- Create
~/.bitwize-music/directory if needed - Ask for each required setting interactively
- Write the config file
- Validate the result
- Create
Required 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:
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:
- Read existing config
- Show current values
- Ask what they want to change
- Update just that setting
- 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:
- Read
~/.bitwize-music/config.yaml - Display all settings in a formatted table
- 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:
- Config file exists
- All required fields present
- Paths are valid (directories exist or can be created)
- 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:
- Confirm user really wants to reset
- Back up existing config to
config.yaml.bak - Delete
~/.bitwize-music/config.yaml - 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:
# 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
Related Skills
taste-skill
118.3kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
hyperframes
86.4kAI video you can actually edit. HyperFrames is a free, open-source AI video editor. Describe any video and get a real project you can change down to the frame.
ai-job-search
72.4kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.4kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
