Skip to main content
skill CX Codex

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

Checks the Python environment and plugin dependencies, then gives setup commands. Use it during first-time setup or when the MCP server will not start.

CC0-1.0 255 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 setup -a claude-code
Open on GitHub

What setup does

The skill inspects the Python version, platform, pipx, and venv support. It then checks the dedicated environment at ~/.bitwize-music/venv, including mcp, matchering, boto3, playwright, and package versions from requirements.txt.

Installation uses one shared virtual environment. Dependencies come from requirements.txt, while document hunter also needs Chromium installed through playwright. Restart Claude Code after installation and run /bitwize-music:setup again to verify the result. On native Windows, audio tooling requires WSL2.

What it helps with

  • check Python and venv support
  • locate missing plugin dependencies
  • compare installed packages with requirements.txt
  • install Chromium for document hunter
  • verify the MCP server setup

Example prompts for the agent

  • Run /bitwize-music:setup and check every component.
  • Run /bitwize-music:setup mcp to check the MCP dependencies.
  • After installing the packages, run /bitwize-music:setup again to verify them.

How to install setup

1Skills CLI (Vercel)

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

2Manually: put the files in place

~/.claude/skills/setup/SKILL.md

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

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

Questions about setup

How do I install setup in Claude Code?

Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill setup -a claude-code, then check ~/.claude/skills/setup/SKILL.md.

What does setup do?

It detects the Python environment, checks the plugin virtual environment, and looks for mcp, matchering, boto3, and playwright. It also shows commands for installing the dependencies.

What does setup need on Windows?

Native Windows uses py -3 and the ~/.bitwize-music/venv/Scripts/ path. Audio tooling requires WSL2.

Source text

SKILL.md · CC0-1.0
---
name: setup
description: Detects your Python environment and guides you through installing plugin dependencies. Use on first-time setup or when MCP server fails to start.
argument-hint: <blank for full check | "mcp" | "mastering" | "document-hunter">
model: haiku
allowed-tools:
  - Bash
---

Base directory for this skill: ${CLAUDE_PLUGIN_BASE_DIR}

## Your Task

Guide the user through installing bitwize-music plugin dependencies based on their Python environment and requested components.

---

# Setup Assistant

You help users install and verify plugin dependencies.

---

## Step 1: Detect Environment

**Run these checks in parallel:**

```bash
# Python version
python3 --version

# Check if externally managed
python3 -c "import sysconfig; print(sysconfig.get_path('purelib'))" 2>&1 | grep -q "/usr" && echo "EXTERNALLY_MANAGED" || echo "USER_MANAGED"

# Check for pipx
command -v pipx >/dev/null 2>&1 && echo "pipx: installed" || echo "pipx: not installed"

# Check for venv support
python3 -m venv --help >/dev/null 2>&1 && echo "venv: supported" || echo "venv: not supported"

# Platform
uname -s
```

---

## Step 2: Check Component Status

**IMPORTANT:** Run these checks **sequentially**, not in parallel. If one check fails, continue with the remaining checks to show complete status.

**CRITICAL:** Always check the venv, not system Python!

```bash
# Set venv path (macOS/Linux/WSL uses bin/python3; native Windows uses Scripts/python.exe)
VENV_PYTHON=~/.bitwize-music/venv/bin/python3
[ -f "$VENV_PYTHON" ] || VENV_PYTHON=~/.bitwize-music/venv/Scripts/python.exe

# Check if venv exists
if [ -f "$VENV_PYTHON" ]; then
    echo "✅ Venv exists at ~/.bitwize-music/venv"

    # Check each component in the venv
    # 2.x serves MCPServer from mcp.server.mcpserver, 1.x serves FastMCP from
    # mcp.server.fastmcp; the server takes either, so probe both (#537).
    $VENV_PYTHON -c "import mcp.server.mcpserver" 2>/dev/null || $VENV_PYTHON -c "import mcp.server.fastmcp" 2>/dev/null && echo "✅ mcp installed" || echo "❌ mcp not installed (need mcp[cli]>=1.28.1,<3)"
    $VENV_PYTHON -c "import matchering; print('✅ matchering installed')" 2>&1 || echo "❌ matchering not installed"
    $VENV_PYTHON -c "import boto3; print('✅ boto3 installed')" 2>&1 || echo "❌ boto3 not installed"
    $VENV_PYTHON -c "from playwright.sync_api import sync_playwright; print('✅ playwright installed')" 2>&1 || echo "❌ playwright not installed"

    # Check for version drift against requirements.txt
    $VENV_PYTHON -c "
import importlib.metadata, pathlib
reqs = pathlib.Path('${CLAUDE_PLUGIN_ROOT}/requirements.txt').read_text()
stale = []
for line in reqs.splitlines():
    line = line.split('#')[0].strip()
    if not line or '==' not in line:
        continue
    name, _, ver = line.partition('==')
    name = name.split('[')[0].strip()
    try:
        installed = importlib.metadata.version(name)
        if installed != ver:
            stale.append(f'  {name}: {installed} → {ver}')
    except importlib.metadata.PackageNotFoundError:
        stale.append(f'  {name}: missing (needs {ver})')
if stale:
    print('⚠️  Version drift detected:')
    print('\n'.join(stale))
else:
    print('✅ All package versions match requirements.txt')
" 2>&1
else
    echo "❌ Venv not found at ~/.bitwize-music/venv"
    echo "   Run: python3 -m venv ~/.bitwize-music/venv   # macOS/Linux/WSL"
    echo "   Or:  py -3 -m venv ~/.bitwize-music/venv      # Windows"
fi
```

All components are installed together in the venv via requirements.txt.

---

## Step 3: Show Installation Commands

**Always use the unified venv approach** — it works on all platforms and is automatically detected by the plugin.

```bash
# Create unified venv (if it doesn't exist)
python3 -m venv ~/.bitwize-music/venv                                                    # macOS/Linux/WSL
py -3 -m venv ~/.bitwize-music/venv                                                       # Windows (native)

# Install ALL plugin dependencies
~/.bitwize-music/venv/bin/pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt                     # macOS/Linux/WSL
~/.bitwize-music/venv/Scripts/python.exe -m pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt   # Windows (native)

# Set up document hunter browser
~/.bitwize-music/venv/bin/playwright install chromium                                     # macOS/Linux/WSL
~/.bitwize-music/venv/Scripts/playwright.exe install chromium                             # Windows (native)
```

**That's it!** The plugin automatically detects and uses the platform venv (`~/.bitwize-music/venv` on macOS/Linux/WSL, `%USERPROFILE%\.bitwize-music\venv` on native Windows). No configuration needed.

**Works on:**
- ✅ Linux (externally-managed Python)
- ✅ macOS
- ✅ Windows (native — Core tier, best-effort; audio tooling needs WSL2)
- ✅ Windows (WSL)
- ✅ All other systems

---

## Step 4: Installation Guide

Present a clear, simple installation guide:

1. **Environment detected**: [Python version, Platform]
2. **Missing components**: [list what needs to be installed]
3. **Installation commands**:
   ```bash
   python3 -m venv ~/.bitwize-music/venv                                                  # macOS/Linux/WSL
   ~/.bitwize-music/venv/bin/pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt         # macOS/Linux/WSL
   ~/.bitwize-music/venv/bin/playwright install chromium                                   # macOS/Linux/WSL

   py -3 -m venv ~/.bitwize-music/venv                                                               # Windows (native)
   ~/.bitwize-music/venv/Scripts/python.exe -m pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt # Windows (native)
   ~/.bitwize-music/venv/Scripts/playwright.exe install chromium                                     # Windows (native)
   ```
4. **After installation**:
   - Restart Claude Code to reload the plugin
   - MCP server should show as running in `/plugin` status
   - Run `/bitwize-music:setup` again to verify

---

## Step 5: Verify Installation (if requested)

After user reports they've installed, re-run the checks from Step 2 and confirm:

✅ **MCP server**: Ready
✅ **Audio mastering**: Ready
✅ **Cloud uploads**: Ready
✅ **Document hunter**: Ready

**Next steps**: Run `/bitwize-music:configure` to set up your workspace paths.

---

## Output Format

Use clear sections with checkboxes for status:

```markdown
## bitwize-music Setup

### Environment
- Python: 3.12.3
- System: Linux

### Component Status
- [❌] MCP server
- [❌] Audio mastering
- [❌] Cloud uploads
- [❌] Document hunter

### Installation

Run these commands to install all plugin dependencies (macOS/Linux/WSL shown; see Step 3 for the Windows native `py -3` / `Scripts\` equivalents):

```bash
# Create unified venv
python3 -m venv ~/.bitwize-music/venv

# Install ALL dependencies
~/.bitwize-music/venv/bin/pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt

# Set up browser
~/.bitwize-music/venv/bin/playwright install chromium
```

**After installation:**
1. Restart Claude Code
2. All components will work automatically
3. Run `/bitwize-music:setup` to verify

The plugin automatically detects `~/.bitwize-music/venv` — everything just works!
```

---

## Remember

- **Be specific** - show exact commands for their environment
- **Prioritize user install** for externally-managed Python
- **Explain what each component does** so they can decide what to install
- **Test commands work** before suggesting them
- **Clear next steps** after installation

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

Similar skills

SKILL.md skills catalog →

setup by other authors comes first.

setup official anthropics setup is a Claude Code skill that checks connected tools, learns your writing style from sent email, and builds a starter dashboard without a questionnaire. For first run. CX Codex +1 371installs setup Alireza Rezvani setup sets up an autoresearch experiment by collecting its target file, evaluation command, metric, and optimization direction. Use it before starting an optimization loop. CX Codex +1 1,480installs setup aws This skill kicks off the connection setup for AWS DevOps Agent and AWS Security Agent. Reach for it when MCP tools go missing or you are wiring the toolkit up for the first time. CX Codex +1 1,600installs setup marketcalls setup sets up a Python backtesting environment with VectorBT and OpenAlgo. It configures the virtual environment, installs dependencies, and prepares .env. CX Codex +1 2,100installs setup assistant-ui setup is a Claude Code skill that installs and configures assistant-ui through its CLI. It covers new projects, existing Next.js apps, and package updates. CX Codex +1 6,400installs setup-matt-pocock-skills Matt Pocock The setup-matt-pocock-skills skill configures a repository for Matt Pocock's engineering skills by setting its issue tracker, triage labels, and domain docs layout. Run it before using the other skills. CX Codex +1 1,052,851installs setup-pre-commit Matt Pocock The setup-pre-commit skill configures pre-commit checks for a JavaScript repository, running Prettier, type checking, and tests before each commit. CX Codex +1 489,289installs prisma-database-setup prisma prisma-database-setup is a deprecated compatibility name for the prisma-orm-setup skill, which handles Prisma setup and database connection repair. CX Codex +1 439,300installs prisma-postgres-setup prisma prisma-postgres-setup provisions or connects a Prisma Postgres database and links it to your app. Useful for spinning up dev databases quickly or wiring connections in Vercel and v0. CX Codex +1 425,700installs xcode-project-setup Google LLC xcode-project-setup is a Claude Code skill that adds Swift Packages and links modules in .pbxproj via a native Swift script. It activates for iOS dependency installation requests. CX Codex +1 141,900installs caveman-setup JuliusBrussee caveman-setup routes LLM API calls through the Caveman Cloud gateway to measure token costs without altering app behavior. Useful for tracking model spend across a repo. CX Codex +1 127,300installs

From the same set52

The whole set →
promo-writer promo-writer creates platform-specific social copy from album material and lyrics. Use it before release when promo/ templates need campaign content. CX Codex +1 259installs tutorial tutorial guides new users through album creation, from the initial idea and sound to the tracklist, artwork concept, and final plan. CX Codex +1 259installs import-audio import-audio moves downloaded audio into the right album folder and separates stem archives by track. Useful for WAV, MP3, and other supported files. CX Codex +1 257installs document-hunter document-hunter searches and downloads primary public records, court dockets, and government reports using Playwright browser automation. CX Codex +1 256installs researchers-security The researchers-security skill investigates malware, CVEs, threat actors, and incident reports. Use it to check cybersecurity topics or verify a track before writing about it. CX Codex +1 255installs researchers-biographical researchers-biographical researches the lives, interviews, motives, and personal details of people connected to an album’s subject. Designed for research in documentary music projects. CX Codex +1 254installs researchers-journalism researchers-journalism — a skill for locating and analyzing investigative journalism, interviews, and news coverage. Use it when you need credible sources to verify facts or add context to music projects. CX Codex +1 254installs album-ideas album-ideas is a Claude Code skill that organizes music concepts before an album repository is created, tracking genres and development status in IDEAS.md. CX Codex +1 254installs

Project sponsors

Companies that keep this analytics open