spotify-player
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
74
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 ./skills/spotify-player/SKILL.mdQuality
Discovery
40%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is extremely terse. While it identifies a clear niche (terminal-based Spotify control) that is distinctive, it lacks concrete action details, natural trigger terms users would say, and entirely omits a 'Use when...' clause. The brevity hurts more than it helps here.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to play music, search for songs/artists/albums, or control Spotify playback from the terminal.'
List specific concrete actions such as 'play tracks, pause/resume, skip, search for songs/artists/albums, view queue, control volume'.
Include natural trigger terms users would say: 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'queue', 'now playing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spotify) and two broad actions (playback and search), and mentions specific tools (spogo, spotify_player), but doesn't list concrete actions like 'play a track', 'pause', 'skip', 'search for artists', 'queue songs', etc. | 2 / 3 |
Completeness | Describes what it does (Spotify playback/search via terminal tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Spotify', 'playback', 'search', and tool names 'spogo' and 'spotify_player', which are relevant. However, it misses common natural user terms like 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'queue', 'now playing'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Terminal', 'Spotify', and specific tool names (spogo, spotify_player) creates a very clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that efficiently communicates specific CLI commands for two Spotify terminal tools. Its main strength is token efficiency and actionability—every line earns its place. The only weakness is the lack of an explicit workflow sequence for initial setup and a troubleshooting/validation step (e.g., verifying auth worked before attempting playback).
Suggestions
Add a brief sequential workflow for first-time setup: 1) import auth cookies, 2) verify with `spogo status`, 3) set device, 4) play — to clarify the expected order and include a validation checkpoint.
Consider adding a brief troubleshooting note for common failure modes (e.g., expired cookies, no active device) to help Claude diagnose issues.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Spotify is or how CLI tools work. Every line provides actionable information Claude wouldn't inherently know (specific command syntax, config paths, setup steps). | 3 / 3 |
Actionability | Provides specific, copy-paste ready CLI commands for all common operations (search, playback, device management, auth setup). The commands are concrete and executable, not pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | This is a relatively simple skill, but the setup flow (auth import → device selection → playback) isn't explicitly sequenced. There's no validation step to confirm auth succeeded or that a device is active before attempting playback, which would help troubleshoot common issues. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized into logical sections (setup, primary commands, fallback commands, notes). No bundle files are needed for this scope. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- Reviewed
Table of Contents
Is this your skill?
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.