cli

Control media playback and routing across sources and outputs via CLI.

108|9|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/ad-repo/nullplayer --skill cli-ad-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli
Source: https://github.com/ad-repo/nullplayer/tree/main/skills/cli
Command: npx skills add https://github.com/ad-repo/nullplayer --skill cli-ad-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NullPlayer's CLI mode provides a scriptable, headless interface to browse, search, play, and route media from local libraries and remote sources to various outputs and cast systems. It enables automation-friendly control beyond GUI, enabling integration into shell automation pipelines.

Core Features & Use Cases

  • Headless mode for terminal workflows and automation pipelines
  • Scriptable media control across sources (local, Plex, Subsonic/Navidrome, Jellyfin, Emby, internet radio)
  • Output routing to local devices, Sonos, Chromecast, or DLNA targets
  • JSON query output for automation and pipelines
  • Keyboard controls for playback during CLI sessions

Quick Start

Launch NullPlayer in CLI mode with the --cli flag and start issuing commands to control playback and routing.

Frequently Asked Questions about cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control media playback from the terminal across multiple sources like Plex and Jellyfin?

Headless media playback control across sources like Plex and Jellyfin is handled via a scriptable CLI interface that queries libraries, resolves media, and routes output to local or network targets using machine-readable JSON outputs.

Can I automate audio routing to Chromecast and Sonos from a shell script?

Automating audio routing to Chromecast and Sonos targets is supported by issuing deterministic CLI commands, allowing shell scripts to safely interact with the audio engine and cast components without a GUI.

What is the best way to integrate internet radio and local library playback into an automation pipeline?

Integrating internet radio and local library playback into automation pipelines requires a headless CLI mode that queries multiple sources, resolves media files, and outputs structured JSON data for downstream processing.

Does headless media orchestration require a GUI to cast media to DLNA targets?

Headless media orchestration does not require a GUI to cast media to DLNA targets, as the CLI mode enables direct, scriptable control over playback and routing through terminal commands and keyboard controls.

How do I query and resolve media sources using a command line interface?

Querying and resolving media sources via a command line interface requires passing the --cli flag, triggering a robust argument parser to resolve local and remote sources and return deterministic JSON outputs.

What are the limitations of using a CLI for multi-source media playback control?

Limitations of CLI multi-source media control include the necessity of launching with the --cli flag and relying on keyboard controls for session playback, designed for deterministic automation rather than dynamic GUI interaction.