Interface with a Music Assistant server via its local API — control players, manage queues, and save/update DSP settings.
Apply a recommended parametric-EQ DSP preset tuned for spoken-word / podcast listening to a Music Assistant player. Tames sub-bass rumble, lifts vocal presence (1–4 kHz), and softens sibilance (~6–8 kHz). Use when the user wants a one-shot "make this speaker good for podcasts" action — typically a kitchen, bathroom, or office speaker — without hand-rolling EQ bands.
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%").
Enumerate all players known to the Music Assistant server along with their current state (playing/paused/idle), volume, and currently-playing track if any. Use when the user asks what players are available, which are active, or needs a player_id to target with another command.
First-run setup for the media-assistant-ops plugin. Capture the user's local Music Assistant deployment URL + API key, snapshot the current speaker/player roster for future context, vet the overall setup (providers, connectivity, auth), and summarise the library (track/album/artist counts, active music providers). Use when the plugin is freshly installed, when `config.json` is missing, or when the user wants to re-baseline against a new server.
Shared reference for the Music Assistant local API — base URL, auth, the WebSocket command bus, the DSP/EQ schema, and the data-storage layout this plugin uses. Load when another skill in this plugin needs to know how to talk to the server, what DSP shape to send, or where to read/write files.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A Claude Code plugin for interfacing with a Music Assistant server via its local API. Control players, inspect the library, and save or update per-player DSP settings from inside Claude Code.
onboard — capture the server's LAN IP, optional WAN IP, and API key; write them to the plugin's config file.status — verify connectivity to the configured Music Assistant server and report version + player count.list-players — enumerate players known to the server with current state and volume.control-player — play / pause / stop / skip / set volume on a named player.save-dsp-settings — snapshot a player's current DSP (EQ + filters) configuration to disk as a named preset.update-dsp-settings — apply a saved DSP preset (or ad-hoc values) to a player.apply-podcast-preset — push a curated parametric-EQ preset tuned for spoken-word / podcast listening (full-range or small-speaker variant).reference — shared reference on the Music Assistant API shape, auth, DSP schema, and endpoint patterns. Grounded against the official docs at https://www.music-assistant.io/api/.claude plugins install media-assistant-ops@danielrosehill
After installing, run the onboard skill once to capture the server address and API key.
The plugin stores its config and saved DSP presets under:
${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/media-assistant-ops/
├── config.json # server IPs + API key
└── data/dsp-presets/ # saved DSP presets per player
Nothing is written to ~/.claude/ or the plugin install directory.
MIT
npx claudepluginhub danielrosehill/claude-code-plugins --plugin media-assistant-opsHarness-native ECC plugin for engineering teams - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Unity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Plugin-safe Claude Code distribution of Antigravity Awesome Skills with 1,640 supported skills.
Claude Code plugin for image editing, batch operations, format conversion, and filesystem organisation of image libraries — bucket by resolution, aspect ratio, orientation, format, EXIF capture time, camera, and dedupe duplicates / near-duplicates.
First-pass data analysis toolkit: correlations, PII flagging, anomalies, hypothesis tests, data dictionaries, and trend analysis on a dataset in a folder.
Claude Code plugin: ideation and planning workflow — capture, evaluate, rank, simulate, and plan ideas, with ideation/single-idea-eval/multi-idea-ranking/feature-ideas/simulation/idea-capture variants.
Manage a Proxmox VE host via SSH and the Proxmox API — guided first-run onboarding, VM/CT lifecycle, storage and ZFS inspection, log review, and update workflows. Per-host config is stored outside the plugin so the same install works across multiple Proxmox environments.
Personal budgeting workflow primitives — transaction logging, categorization, budget creation, spending analysis, goal tracking, and forecasting — plus a provisioning skill for a fresh budgeting workspace.