Skill

update-dsp-settings

Apply a DSP configuration to a Music Assistant player — either by loading a previously saved preset from disk or by adjusting specific EQ bands/filters in-place. Use when the user wants to switch a player to a saved preset ("apply night-mode to living room") or tweak bands directly ("boost 60Hz by 2dB on bedroom").

npx claudepluginhub danielrosehill/claude-code-plugins --plugin media-assistant-ops

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Two modes: **apply preset** or **ad-hoc edit**.

SKILL.md

Similar Skills

using-superpowers

180.9k

Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.

3 files

superpowers

Stats

Stars0

Forks0

Last CommitApr 21, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

update-dsp-settings

Update DSP Settings

Two modes: apply preset or ad-hoc edit.

Mode A: Apply a saved preset

Load config per the reference skill. Resolve the target player.

List presets in $DATA_ROOT/data/dsp-presets/<player-slug>/. If the user named one, load it. If not, show the list and ask.

PUT the preset's dsp block to $BASE/api/players/<player_id>/dsp with the Bearer token.

Verify by GETting the DSP config back and confirming it matches. Report success with the preset name applied.

Mode B: Ad-hoc edit

GET the current DSP config.

Apply the user's requested change to the in-memory object:

Band adjustment: locate the band by frequency (nearest match) and set gain / q.
Add/remove band: mutate the bands array.
Toggle enabled: flip the enabled flag.
Filter changes: mutate the filters array.

PUT the modified config back.

Offer to save the result as a new preset (delegate to the save-dsp-settings skill).

Safety

Before any PUT, echo a one-line summary of what will change (e.g. living-room: band@60Hz gain -3 -> -5, 4 other bands unchanged) and require confirmation unless the user's prompt was unambiguous.

Keep a one-shot rollback: stash the pre-change DSP to $DATA_ROOT/state/last-dsp-<player-slug>.json before the PUT so the user can say "revert" and you can re-PUT it.