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—it identifies the domain (Spotify via terminal) and specific tools, giving it good distinctiveness, but it lacks concrete action details and entirely omits a 'Use when...' clause. The brevity hurts both completeness and trigger term coverage, making it harder for Claude to reliably select this skill from a large pool.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to play, pause, skip, or search for music, songs, artists, or albums via Spotify in the terminal.'
List specific concrete actions such as 'play tracks, pause/resume playback, skip songs, search for artists/albums/tracks, manage queue, control volume'.
Include natural user trigger terms like 'play music', 'song', 'track', 'artist', 'album', 'pause', 'next song', 'queue' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spotify) and two broad actions (playback, search), and mentions specific tools (spogo, spotify_player), but doesn't list concrete actions like 'play tracks', 'pause', 'skip', 'search artists', 'queue songs', etc. | 2 / 3 |
Completeness | Provides a brief 'what' (Spotify playback/search via terminal tools) but completely lacks any 'when' clause or explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself 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 terms users would say like 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'queue'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Terminal Spotify' with 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 provides clear CLI command references for two Spotify terminal tools. Its strengths are excellent token efficiency and highly actionable command syntax. The main weakness is a lack of explicit workflow sequencing for initial setup and no verification steps to confirm authentication or device connectivity before attempting playback.
Suggestions
Add a brief first-time setup sequence: install → authenticate → verify with `spogo status` → use playback commands, so Claude knows how to confirm auth succeeded before issuing commands.
Include a troubleshooting note for common failure modes (e.g., expired cookies, no active device) so Claude can diagnose issues when commands fail.
| 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, status). The auth setup command is concrete and executable. Both tools have clear command syntax. | 3 / 3 |
Workflow Clarity | The skill is relatively simple (CLI command reference), but the setup flow could be clearer—there's no explicit sequence for first-time setup (install → auth → verify → use) and no validation step to confirm auth succeeded before attempting playback commands. | 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 tool commands, fallback tool commands, notes). No bundle files are needed. | 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
- Hung-Reo/hungreo-openclaw
- Commit
d8d7f4b
- 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.