Agent skill

Configure

by bitwize-music-studio in bitwize-music-studio/claude-ai-music-skills

Sets up or edits the plugin configuration file interactively.

CC0-1.0Auto-check: notes

Install Configure

skills CLI

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

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/configure .claude/skills/configure && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .claude/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/configure .agents/skills/configure && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .agents/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

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

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/configure .cursor/skills/configure && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .cursor/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/bitwize-music-studio/claude-ai-music-skills.git --path skills/configure

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/configure .gemini/skills/configure && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .gemini/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/configure .github/skills/configure && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .github/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

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

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install bitwize-music-studio/claude-ai-music-skills configure --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/bitwize-music-studio/claude-ai-music-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/configure .opencode/skills/configure && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "configure" agent skill from https://github.com/bitwize-music-studio/claude-ai-music-skills/tree/main/skills/configure into .opencode/skills/configure/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "configure", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: configure
GitHub stars: 544
Token cost: ~2.2k tokens
SKILL.md length: 580 words
Files: 2
Skills in repo: 51
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: CC0-1.0

At a glance

Sets up or edits the plugin configuration file interactively.

Works in 3 steps: Check if ~/.bitwize-music/config.yaml… → If exists, ask if they want to overwrite… → If creating new
Wants to change settings
SKILL.md covers Your Task, Config Location, Commands and Config Template, plus 2 more sections
Reaches soundcloud.com

What it does

Configure is an agent skill from bitwize-music-studio/claude-ai-music-skills. 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.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `SETTINGS_REFERENCE.md`).

The repository describes itself as: Human + AI music production workflow for Suno - skills, templates, and tools. The licence is CC0-1.0.

When your agent uses it

Wants to change settings

Example prompts

“/configure”

Requirements

Pre-approved tools (allowed-tools): Read, Write, Bash, AskUserQuestion, Glob

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

Check if ~/.bitwize-music/config.yaml exists
If exists, ask if they want to overwrite or edit instead
If creating new

What it can do on your machine

Read from SKILL.md and the folder at commit 58f32c2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Write
- Bash
- AskUserQuestion
- Glob
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- soundcloud.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Configure loads about 2.2k tokens when it runs. Until then it costs about 41 tokens; SKILL.md has 580 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~41
When it runs · the whole SKILL.md, loaded when a task matches: ~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Write, Bash, AskUserQuestion, Glob
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from bitwize-music-studio/claude-ai-music-skills at commit 58f32c2, republished under its CC0-1.0 licence (© bitwize-music-studio). 580 words, ~2,214 tokens.

Download SKILL.mdSave it as .claude/skills/configure/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

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.
allowed-tools: Read, Write, Bash, AskUserQuestion, Glob
argument-hint: [setup | edit | show | validate | reset]
model: sonnet
effort: low

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:

Check if ~/.bitwize-music/config.yaml exists
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

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!

Show full SKILL.md (241 more words)Show less

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

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

Files

SKILL.md and 1 other file in skills/configure of bitwize-music-studio/claude-ai-music-skills.

SKILL.md
SETTINGS_REFERENCE.md

Open the folder on GitHubat commit 58f32c2

Compare with similar skills

Configure next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Configure compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Configure this skillbitwize-music-studio/claude-ai-music-skills	544	—	~2.2k	Automated safety check: Notes	CC0-1.0	2 days ago
Configuring Windows Defender Advanced Settingsmukul975/Anthropic-Cybersecurity-Skills	34k	—	~3.1k	Automated safety check: Pass	Apache-2.0	1 mo ago
Configure Channelopenclaw/openclaw	392k	—	~946	Automated safety check: Pass	MIT	today
Copy Editingcoreyhaines31/marketingskills	54k	1 repos	~4.5k	Automated safety check: Pass	MIT	yesterday
Warp Settings Editorwarpdotdev/warp	65k	1 repos	~675	Automated safety check: Pass	AGPL-3.0	today
Venice Image Editnexu-io/open-design	100k	—	~263	Automated safety check: Pass	Apache-2.0	today

Similar skills

Configuring Windows Defender Advanced Settings
mukul975/Anthropic-Cybersecurity-Skills
Configures Microsoft Defender for Endpoint (MDE) advanced protection settings including attack surface reduction rules, controlled folder access, network protection, and exploit protection.
34k GitHub stars~3.1k tokensUpdated 1 mo ago
SecurityAuto-check passed
Configure Channel
openclaw/openclaw
Configure and prove a chat channel with non-interactive one-liners; secrets only as SecretRefs.
392k GitHub stars~946 tokensUpdated today
Auto-check passed
Copy Editing
coreyhaines31/marketingskills
When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content.
54k GitHub starsUsed in 1 repo~4.5k tokens
Writing & ContentAuto-check passed
Warp Settings Editor
warpdotdev/warp
Finds and changes Warp application settings by searching a bundled JSON schema and editing the matching TOML settings file at the right nesting depth.
65k GitHub starsUsed in 1 repo~675 tokens
Productivity & AutomationAuto-check passed
Venice Image Edit
nexu-io/open-design
Image edits, upscaling, and background removal via the Venice.ai API.
100k GitHub stars~263 tokensUpdated today
Media & CreativeAuto-check passed
Fal Image Edit
nexu-io/open-design
AI-powered image editing with style transfer, background removal, object removal, and inpainting via fal.ai hosted models.
100k GitHub stars~301 tokensUpdated today
Media & CreativeAuto-check passed

Questions about Configure

What does Configure do?

Sets up or edits the plugin configuration file interactively. Configure is an agent skill from bitwize-music-studio/claude-ai-music-skills. Sets up or edits the plugin configuration file interactively.

When should I use Configure?

Configure fits situations like: wants to change settings.

How do I install Configure in Claude Code?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a claude-code`. Or copy the skill folder (skills/configure in bitwize-music-studio/claude-ai-music-skills) into .claude/skills/configure in your project. Claude Code loads it when a task matches its description.

How do I install Configure in Codex?

Run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a codex`. Or copy the skill folder (skills/configure in bitwize-music-studio/claude-ai-music-skills) into .agents/skills/configure in your project. Codex loads it when a task matches its description.

Can I use Configure in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add bitwize-music-studio/claude-ai-music-skills --skill configure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/configure, .gemini/skills/configure, .github/skills/configure and .opencode/skills/configure in your project.

What does Configure need to run?

SKILL.md names no scripts, command-line tools or credentials: Configure is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Bash, AskUserQuestion, Glob.

Does Configure access the network?

SKILL.md names 1 domain. In commands or code: soundcloud.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Configure safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Configure use?

Configure is published under the CC0-1.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Configure use?

About 2.2k tokens (SKILL.md is roughly 8.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Configure?

Skills that share tags, products or a category with Configure: Configuring Windows Defender Advanced Settings (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Configure Channel (openclaw/openclaw, 392k stars), Copy Editing (coreyhaines31/marketingskills, 54k stars) and Warp Settings Editor (warpdotdev/warp, 65k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Configure?

bitwize-music-studio (a GitHub organization) maintains it in bitwize-music-studio/claude-ai-music-skills, which has 544 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 7, 2026.

Source: bitwize-music-studio/claude-ai-music-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Configure

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Your Task

Plugin Configuration Skill

Config Location

Commands

/configure or /configure setup

/configure edit

/configure show

/configure validate

/configure reset

Config Template

Edge Cases

Config exists but is invalid YAML

Directory doesn't exist

User provides relative path

Remember

Files

Compare with similar skills

Similar skills

More from bitwize-music-studio/claude-ai-music-skills

Questions about Configure

`/configure` or `/configure setup`

`/configure edit`

`/configure show`

`/configure validate`

`/configure reset`