ClawTrust
15k Downloads
Overview
Provide terminal-based Spotify search and playback control by orchestrating the `spogo` CLI (preferred) or falling back to the `spotify_player` CLI when needed.
Key Advantages
1.Rich playback control: play, pause, next/previous track, device selection, and status information via CLI.
2.Search integration: quickly search for tracks directly from the terminal without opening the Spotify app.
3.Device management: list and select Spotify Connect devices (via `spogo device` or `spotify_player connect`).
4.Fallback implementation: uses `spogo` when available and automatically falls back to `spotify_player`, improving robustness across setups.
5.Leverages existing tools: builds on mature CLIs instead of re-implementing the Spotify protocol, which can improve performance and feature coverage.
Use Cases
- Controlling Spotify playback from a terminal-only workstation or server (e.g., while coding or using a tiling window manager).
- Scriptable music control as part of shell scripts or automation flows (e.g., start playlist when a dev environment launches).
- Remote control of a Spotify Connect device (e.g., office speaker) via terminal commands.
- Quick track searching and playback without switching context to a GUI player.
- Integrating Spotify playback into broader automation through OpenClaw, where the assistant issues `spogo`/`spotify_player` commands on the user’s behalf.
Evaluation Scores
7.3
/ 10
Reliability
7.0
Functionality
7.5
Usability
6.5
Safety
8.0
Performance
8.5
Compatibility
6.5
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.3/103/19/2026▼
OS: linux-x64LLM: minimax/minimax-m2.5
**Judgement:** This skill is a focused, technically solid bridge to control Spotify via the terminal, best suited for users who are comfortable installing and configuring CLI tools. It offers good coverage of core playback operations and search, with efficient performance thanks to lightweight CLI interaction.
**Strengths & fit:**
- Ideal if you already have (or are willing to install) `spogo` or `spotify_player` and have a Spotify Premium account.
- Works well for power users who live in the terminal, want scriptable playback, or want OpenClaw to control Spotify Connect devices.
- Fallback from `spogo` to `spotify_player` improves robustness across different environments.
**Key limitations / risks:**
- **Setup burden:** Requires a Spotify Premium account plus installation and configuration of `spogo` or `spotify_player` (including cookie import / client_id config). Non-technical users may struggle.
- **Account & cookie handling:** `spogo auth import` relies on browser cookies. Misconfiguration or insecure handling of cookies/credentials could expose the Spotify account if the environment is not well secured.
- **External dependency fragility:** Functionality depends on third-party CLIs and Spotify’s APIs. Changes to those tools or Spotify auth mechanisms may break the skill until updated.
- **Platform constraints:** Only practical where `spogo` or `spotify_player` are supported (typically desktop/server environments, not restricted sandboxes).
**Recommended scenarios:**
- Technical users with Spotify Premium who want terminal-based control and scripting of Spotify playback.
- Using OpenClaw to automate music in development or operations workflows (e.g., auto-play playlists at certain times or triggers).
- Controlling remote Spotify Connect devices from headless or SSH sessions.
**Less suitable when:**
- You don’t have Spotify Premium, cannot install extra CLI tools, or prefer a simple, zero-config, GUI-based music control solution.
- You are in a locked-down environment where browser cookie export or CLI installation is not allowed.
Comments (0)
No comments yet. Be the first!