setup
Acerca de
Esta habilidad de Claude detecta automáticamente tu entorno de Python y te guía en la instalación de las dependencias del complemento para el servidor MCP de bitwize-music. Úsala durante la configuración inicial o cuando el servidor MCP falle al iniciar, ya que verifica versiones de Python, gestión de paquetes y valida las instalaciones. La habilidad permite comprobaciones específicas de dependencias para componentes como "mcp" o "mastering" cuando sea necesario.
Instalación rápida
Claude Code
Recomendadonpx skills add bitwize-music-studio/claude-ai-music-skills -a claude-code/plugin add https://github.com/bitwize-music-studio/claude-ai-music-skillsgit clone https://github.com/bitwize-music-studio/claude-ai-music-skills.git ~/.claude/skills/setupCopia y pega este comando en Claude Code para instalar esta habilidad
Documentación
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
VENV_PYTHON=~/.bitwize-music/venv/bin/python3
# Check if venv exists
if [ -f "$VENV_PYTHON" ]; then
echo "✅ Venv exists at ~/.bitwize-music/venv"
# Check each component in the venv
$VENV_PYTHON -c "import mcp; print('✅ mcp installed')" 2>&1 || echo "❌ mcp not installed"
$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"
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
# Install ALL plugin dependencies
~/.bitwize-music/venv/bin/pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt
# Set up document hunter browser
~/.bitwize-music/venv/bin/playwright install chromium
That's it! The plugin automatically detects and uses ~/.bitwize-music/venv. No configuration needed.
Works on:
- ✅ Linux (externally-managed Python)
- ✅ macOS
- ✅ Windows (WSL)
- ✅ All other systems
Step 4: Installation Guide
Present a clear, simple installation guide:
- Environment detected: [Python version, Platform]
- Missing components: [list what needs to be installed]
- Installation commands:
python3 -m venv ~/.bitwize-music/venv ~/.bitwize-music/venv/bin/pip install -r ${CLAUDE_PLUGIN_ROOT}/requirements.txt ~/.bitwize-music/venv/bin/playwright install chromium - After installation:
- Restart Claude Code to reload the plugin
- MCP server should show as running in
/pluginstatus - Run
/bitwize-music:setupagain 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:
```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:
- Restart Claude Code
- All components will work automatically
- Run
/bitwize-music:setupto 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
Repositorio GitHub
Frequently asked questions
What is the setup skill?
setup is a Claude Skill by bitwize-music-studio. Skills package instructions and resources that Claude loads on demand, so Claude can perform setup-related tasks without extra prompting.
How do I install setup?
Use the install commands on this page: add setup to Claude Code as a plugin, or clone its repository into your skills directory, then restart Claude so it picks up the skill.
What category does setup belong to?
setup is in the Design category, tagged ai, mcp and design.
Is setup free to use?
Yes. setup is listed on AIMCP and free to install. It runs inside Claude, so no separate service account is required to use the skill itself.
Habilidades relacionadas
Utilice la habilidad executing-plans cuando tenga un plan de implementación completo para ejecutar en lotes controlados con puntos de revisión. Esta habilidad carga y revisa críticamente el plan, luego ejecuta tareas en pequeños lotes (por defecto 3 tareas) mientras reporta el progreso entre cada lote para la revisión del arquitecto. Esto asegura una implementación sistemática con puntos de control de calidad integrados.
Esta habilidad despacha un subagente revisor de código para analizar los cambios en el código frente a los requisitos antes de proceder. Debe usarse después de completar tareas, implementar funciones principales o antes de fusionar con la rama principal. La revisión ayuda a detectar problemas de forma temprana al comparar la implementación actual con el plan original.
Esta habilidad proporciona una guía integral para que los desarrolladores conecten servidores MCP a Claude Code mediante transportes HTTP, stdio o SSE. Cubre la instalación, configuración, autenticación y seguridad para integrar servicios externos como GitHub, Notion y APIs personalizadas. Úsala al configurar integraciones MCP, al configurar herramientas externas o al trabajar con el Protocolo de Contexto del Modelo de Claude.
Esta habilidad ayuda a los desarrolladores a elegir entre las interfaces web y CLI de Claude Code mediante el análisis de tareas, y luego permite la teletransportación fluida de sesiones entre estos entornos. Optimiza el flujo de trabajo gestionando el estado y el contexto de la sesión al cambiar entre web, CLI o móvil. Úsala para proyectos complejos que requieren diferentes herramientas en varias etapas.
