Vibe — reads your session and picks the perfect genre
Scanned 5/27/2026
Install via CLI
openskills install kennethleungty/claude-music---
name: vibe
description: "Vibe — reads your session and picks the perfect genre"
model: haiku
allowed-tools: Bash
---
This skill is part of the claude-music plugin. Only invoke when the user explicitly uses the slash command.
# Vibe
Auto-detect the right music based on what's happening in the current session. No user input needed — the DJ reads the room.
## Instructions
You have the full conversation context. Pick the best music and play it in ONE step. Do NOT spawn an agent or delegate.
### Step 1: Read the room and pick music
Read the genre metadata from sources.yml:
```bash
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()
"
```
Using the tags and descriptions, match the session context to the best genre. Consider:
- What the user has been working on (e.g. debugging, building a feature, reviewing code)
- The general mood/pace of the session
- Any explicit mood signals from the user
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.
### Step 2: Play it
Pick a specific station name from the matched genre, then:
```bash
"${CLAUDE_PLUGIN_ROOT}/scripts/music-controller.sh" play "<station name>"
```
### Step 3: Respond
Return a message in EXACTLY this format:
**♪ Now playing {genre} — {station name}. {one-liner reason tied to the session} ♪**
- If `takeover` is `true` in the JSON output: prefix with *Switched over from another session —*
- If error about no audio player: run the `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.
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.