Spotify Player
Control Spotify search and playback from the terminal via spogo (preferred) or spotify_player while coding.
Overview
Spotify Player is an agent skill for the Build phase that runs terminal Spotify search and playback through spogo or spotify_player.
Install
npx skills add https://github.com/steipete/clawdis --skill spotify-playerWhat is this skill?
- Prefers spogo; falls back to spotify_player for search and transport controls
- Brew install paths for both CLIs (steipete/tap for spogo)
- spogo auth via browser cookie import (Chrome)
- Playback, device list/set, and status commands documented for both tools
- Requires Spotify Premium and either binary on PATH
- Two CLI backends: spogo (preferred) and spotify_player (fallback)
Adoption & trust: 2k installs on skills.sh; 378k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want focus music during deep work without context-switching to the Spotify app or writing custom API code.
Who is it for?
Developers with Spotify Premium who already use Homebrew and want agent-driven terminal playback.
Skip if: Embedding Spotify in a shipped product, server-side streaming, or users without Premium or macOS/Homebrew-style install paths.
When should I use this skill?
Terminal Spotify playback or search via spogo or spotify_player when either binary is available.
What do I get? / Deliverables
Your agent issues documented CLI commands for search, playback, and devices after Premium setup and auth import.
- Executed search and playback CLI commands
- Selected Spotify output device
Recommended Skills
Journey fit
This is a local CLI integration skill—builders install and wire terminal tooling during the build/agent-tooling phase of their environment. Integrations subphase fits third-party CLI hooks (brew installs, auth import, device and playback commands).
How it compares
Personal terminal integration skill—not an MCP server or Spotify Web API wrapper for your app.
Common Questions / FAQ
Who is spotify-player for?
Solo builders on Claude Code or similar agents who want CLI Spotify control from the same session as their code.
When should I use spotify-player?
During Build while setting up agent tooling or anytime in a coding session when you need search, play/pause, next/prev, or device changes via spogo or spotify_player.
Is spotify-player safe to install?
It implies shell use and browser cookie import for auth—review the Security Audits panel on this Prism page and trust the brew tap/formula sources before installing.
SKILL.md
READMESKILL.md - Spotify Player
# spogo / spotify_player Use `spogo` **(preferred)** for Spotify playback/search. Fall back to `spotify_player` if needed. Requirements - Spotify Premium account. - Either `spogo` or `spotify_player` installed. spogo setup - Import cookies: `spogo auth import --browser chrome` Common CLI commands - Search: `spogo search track "query"` - Playback: `spogo play|pause|next|prev` - Devices: `spogo device list`, `spogo device set "<name|id>"` - Status: `spogo status` spotify_player commands (fallback) - Search: `spotify_player search "query"` - Playback: `spotify_player playback play|pause|next|previous` - Connect device: `spotify_player connect` - Like track: `spotify_player like` Notes - Config folder: `~/.config/spotify-player` (e.g., `app.toml`). - For Spotify Connect integration, set a user `client_id` in config. - TUI shortcuts are available via `?` in the app.