Stats
Actions
Tags
From media-assistant-ops
Send a playback command to a Music Assistant player — play, pause, stop, next, previous, or set volume. Use when the user asks to control a specific player by name (e.g. "pause the living room", "skip track on kitchen", "set bedroom to 40%").
How this skill is triggered — by the user, by Claude, or both
Slash command
/media-assistant-ops:control-playerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
| Command | Endpoint | Args |
| Command | Endpoint | Args |
|---|---|---|
| play | POST /api/players/<id>/command/play | — |
| pause | POST /api/players/<id>/command/pause | — |
| stop | POST /api/players/<id>/command/stop | — |
| next | POST /api/players/<id>/command/next | — |
| previous | POST /api/players/<id>/command/previous | — |
| volume | POST /api/players/<id>/command/volume_set | {"volume": 0-100} |
| power | POST /api/players/<id>/command/power_toggle | — |
Load config per the reference skill.
Resolve the player. If the user gave a name (not an ID), GET /api/players, match case-insensitively on name, and use the player_id. If multiple match, ask which one.
POST the command with the Bearer token. For volume, include the JSON body {"volume": <int>}.
Report the new state (re-fetch the single player and print name + state + volume).
If the server returns 404 on the endpoint, fall back to the WebSocket command bus pattern described in the reference skill.
npx claudepluginhub danielrosehill/claude-code-plugins --plugin media-assistant-opsCreates bite-sized, testable implementation plans from specs or requirements, with file structure and task decomposition. Activates before coding multi-step tasks.