Skill

snapcast-ops

Reference material for Snapcast server config, client flags, group semantics, and JSON-RPC control. Loaded when working on Snapcast topology.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin smart-home

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Bundled references for working with the Snapcast server and clients in this repo. Read the relevant file when you need it; don't dump everything into context.

Supporting Assets

groups-and-streams.mdjsonrpc-cheatsheet.mdsnapclient-flags.mdsnapserver-conf.mdtroubleshooting-matrix.md

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 19, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

snapcast-ops

Bundled references for working with the Snapcast server and clients in this repo. Read the relevant file when you need it; don't dump everything into context.

Files

snapserver-conf.md — /etc/snapserver.conf structure: [server], [stream], [http], [tcp], group definitions, version differences.

snapclient-flags.md — snapclient CLI flags: --host, --soundcard, --hostID, --player, --latency, --instance.

groups-and-streams.md — how groups, streams, and clients relate; the JSON-RPC vs config-file persistence distinction.

jsonrpc-cheatsheet.md — common JSON-RPC calls (Server.GetStatus, Group.SetStream, Group.SetClients, Client.SetVolume).

troubleshooting-matrix.md — symptom → likely cause → fix table.

Working principles

Config file = persistent. JSON-RPC = runtime. Anything you want to survive a restart goes in /etc/snapserver.conf.

Reload over restart. systemctl reload snapserver keeps clients connected; restart drops them.

HostID is identity. A snapclient's --hostID is its stable name across the snapserver's database. Don't let it default to MAC unless you've thought about it.

One client, one group. Always.

Sinks are fragile. Bind by stable name (alsa_output.usb-Vendor_Model-...), not by index.

snapcast-ops

Bundled references for working with the Snapcast server and clients in this repo. Read the relevant file when you need it; don't dump everything into context.

Files

snapserver-conf.md — /etc/snapserver.conf structure: [server], [stream], [http], [tcp], group definitions, version differences.
snapclient-flags.md — snapclient CLI flags: --host, --soundcard, --hostID, --player, --latency, --instance.
groups-and-streams.md — how groups, streams, and clients relate; the JSON-RPC vs config-file persistence distinction.
jsonrpc-cheatsheet.md — common JSON-RPC calls (Server.GetStatus, Group.SetStream, Group.SetClients, Client.SetVolume).
troubleshooting-matrix.md — symptom → likely cause → fix table.

Working principles

Config file = persistent. JSON-RPC = runtime. Anything you want to survive a restart goes in /etc/snapserver.conf.
Reload over restart. systemctl reload snapserver keeps clients connected; restart drops them.
HostID is identity. A snapclient's --hostID is its stable name across the snapserver's database. Don't let it default to MAC unless you've thought about it.
One client, one group. Always.
Sinks are fragile. Bind by stable name (alsa_output.usb-Vendor_Model-...), not by index.