Terminal Spotify playback/search via spogo (preferred) or spotify_player.
74
Quality
63%
Does it follow best practices?
Impact
100%
12.50xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/spotify-player/SKILL.mdCLI tool preference and playback control commands
spogo checked first
0%
100%
spogo play command
0%
100%
spogo pause command
0%
100%
spogo next command
0%
100%
spogo prev command
0%
100%
spogo status command
0%
100%
spogo device list
0%
100%
spogo device set
0%
100%
fallback to spotify_player
0%
100%
fallback playback syntax
50%
100%
spotify_player not default
0%
100%
Without context: $0.2440 · 1m 5s · 14 turns · 21 in / 3,757 out tokens
With context: $0.3800 · 1m 21s · 23 turns · 327 in / 4,346 out tokens
Setup, authentication, and Spotify Connect configuration
spogo recommended
0%
100%
auth command present
0%
100%
auth uses chrome flag
0%
100%
config directory path
0%
100%
config file name
0%
100%
client_id in config
46%
100%
spotify_player as fallback
0%
100%
spogo status verification
0%
100%
Without context: $0.1862 · 1m 10s · 10 turns · 17 in / 3,746 out tokens
With context: $0.2607 · 1m 7s · 14 turns · 267 in / 3,425 out tokens
Search command syntax and fallback tool commands
spogo as primary
0%
100%
spogo search track subcommand
0%
100%
spogo play after search
0%
100%
spogo status check
0%
100%
fallback present
50%
100%
fallback search syntax
0%
100%
fallback playback syntax
0%
100%
spotify_player not default
70%
100%
Without context: $0.2065 · 48s · 14 turns · 21 in / 2,748 out tokens
With context: $0.3488 · 1m 4s · 23 turns · 185 in / 3,454 out tokens
8763418
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.