How this skill is triggered — by the user, by Claude, or both
Slash command
/claude-music:djhaikuThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is part of the claude-music plugin. Only invoke when the user explicitly uses the slash command.
This skill is part of the claude-music plugin. Only invoke when the user explicitly uses the slash command.
Alias for /vibe. Auto-detect the right music based on what's happening in the current session.
You have the full conversation context. Pick the best music and play it in ONE step. Do NOT spawn an agent or delegate.
Read the genre metadata from sources.yml:
python3 -c "
import sys
try:
import yaml
with open('${CLAUDE_PLUGIN_ROOT}/config/sources.yml') as f:
data = yaml.safe_load(f)
except ImportError:
sys.exit(1)
for genre, info in data.items():
print(f'{genre}:')
for s in info.get('stations', []):
tags = ', '.join(s.get('tags', []))
print(f' - {s[\"name\"]}: {s.get(\"description\", \"\")}')
print(f' tags: {tags}')
print()
" > /dev/null 2>&1
Using the tags and descriptions, match the session context to the best genre. Consider:
When in doubt, lean towards relaxing genres (lofi, ambient, classical). The user prefers a chill atmosphere. Only pick high-energy genres if the session strongly suggests it.
Pick a specific station name from the matched genre, then:
"${CLAUDE_PLUGIN_ROOT}/scripts/music-controller.sh" play "<station name>"
Return a message in EXACTLY this format:
♪ Now playing {genre} — {station name}. {one-liner reason tied to the session} ♪
takeover is true in the JSON output: prefix with Switched over from another session —install_command (if has_sudo is true) or nosudo_hint (if false) from the JSON, then retry play automatically.Keep it to one line. Do not explain your reasoning.
npx claudepluginhub kennethleungty/claude-musicGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Enforces test-driven development: write failing test first, then minimal code to pass. Use when implementing features or bugfixes.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.