SkillAgentSearch skills...

setup

Detects your Python environment and guides you through installing plugin dependencies. Use on first-time setup or when MCP server fails to start.

Install / Use

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

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Claude Code

Our assessment of setup

setup scores 90/100 on our quality scale, 458th of 1,148 Content & Media skills we index (top 40%).

Its SKILL.md is 7.3 KB long, well organised into 26 sections with 5 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.

Substance
29/30
Structure
20/20
Description
15/15
Adoption
12/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so setup 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 found

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.

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.

setup compared with similar skills

All 4 of these similar skills score higher than setup; compare them before choosing.

SkillScoreStarsUpdatedFormat
setup (this skill)by bitwize-music-studio9051256d agoSKILL.md
Agent-Reachby Panniantong100113.0k10d agoCLAUDE.md
hyperframesby heygen-com10086.4ktodayCLAUDE.md
rufloby ruvnet10082.0ktodayCLAUDE.md
headroomby headroomlabs-ai10080.1ktodayCLAUDE.md

Frequently asked questions

How do I install setup?
Run npx skills add bitwize-music-studio/claude-ai-music-skills --skill setup. The install tabs above show the steps for each supported agent.
Which AI agents does setup work with?
It is written for Claude Code, as a SKILL.md file. Other agents that read the same format can often use it too.
Is setup 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 setup still maintained?
The repository was last updated about 2 months ago, so setup is actively maintained.

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:

# 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!

# 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.

# 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:
    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:

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

Related Skills

View on GitHub
GitHub Stars512
CategoryContent
Updated1mo ago
Forks120

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions