Blucli
Control Bluesound and NAD players from the agent via the blu CLI—discovery, playback, volume, grouping, and TuneIn—from scripts or conversational automation.
Overview
blucli is an agent skill for the Build phase that controls Bluesound/NAD BluOS players through the blu CLI for discovery, playback, volume, and grouping.
Install
npx skills add https://github.com/steipete/clawdis --skill blucliWhat is this skill?
- Device discovery with `blu devices` and status via `blu --device <id> status`
- Playback controls: `blu play|pause|stop` and `blu volume set <level>`
- Target resolution order: `--device`, `BLU_DEVICE`, then config default
- Multi-room grouping commands: `blu group status|add|remove`
- TuneIn search and play: `blu tunein search`, `blu tunein play`; prefer `--json` for scripts
- 3-level device target precedence (--device, BLU_DEVICE, config default)
- 5 command areas documented (devices/status, playback, volume, group, tunein)
Adoption & trust: 1.8k installs on skills.sh; 378k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have Bluesound or NAD players on the network but no reliable agent-ready command cheat sheet for discovery, targeting, and playback automation.
Who is it for?
Solo builders with BluOS hardware who want scriptable or agent-driven playback, volume, and TuneIn control from the terminal.
Skip if: Builders without Bluesound/NAD devices or those needing a full music library manager unrelated to BluOS.
When should I use this skill?
You need to discover or control Bluesound/NAD players with the blu CLI and want the agent to pick the right device target and flags.
What do I get? / Deliverables
After the skill runs, your agent produces correct blu commands—with device confirmation and optional JSON—for the playback or grouping action you requested.
- Executed or copy-paste-ready blu command sequences
- Device-targeted playback or grouping state changes
Recommended Skills
Journey fit
Build is the canonical phase because blucli is a host-binary integration skill for wiring local device control into agent workflows, not a launch or growth marketing tool. Integrations matches documented install via Go module, device targeting precedence, and JSON-friendly scripting patterns.
How it compares
Skill package for the blu CLI—not a cloud music API integration or a generic smart-home MCP server.
Common Questions / FAQ
Who is blucli for?
Indie developers and power users running AI coding agents who own Bluesound or NAD players and want consistent CLI automation without reading upstream docs each time.
When should I use blucli?
Use it in the Build phase when hooking agent or shell automation to local audio—e.g., demo playlists, office ambiance scripts, or testing multi-room grouping during integration work.
Is blucli safe to install?
The skill drives network-facing player control via the blu binary; review the Security Audits panel on this Prism page and restrict agent permissions if you automate volume or playback in shared environments.
SKILL.md
READMESKILL.md - Blucli
# blucli (blu) Use `blu` to control Bluesound/NAD players. Quick start - `blu devices` (pick target) - `blu --device <id> status` - `blu play|pause|stop` - `blu volume set 15` Target selection (in priority order) - `--device <id|name|alias>` - `BLU_DEVICE` - config default (if set) Common tasks - Grouping: `blu group status|add|remove` - TuneIn search/play: `blu tunein search "query"`, `blu tunein play "query"` Prefer `--json` for scripts. Confirm the target device before changing playback.