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 identifies a clear and distinctive niche (terminal-based Spotify control) and names specific tools, which helps with disambiguation. However, it is too terse—it lacks concrete action verbs, natural user trigger terms, and a 'Use when...' clause, making it harder for Claude to know when to select this skill.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to play music, control Spotify playback, search for songs/artists/albums, or manage their Spotify queue from the terminal.'
List specific concrete actions such as 'play tracks, pause/resume playback, skip songs, search for artists/albums/playlists, manage queue, check now playing'.
Include natural trigger terms users would say: 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'now playing', 'queue'.
| 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 music', 'search artists', 'queue songs', etc. | 2 / 3 |
Completeness | Provides a brief 'what' (Spotify playback/search via terminal tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric 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', but misses common natural terms users would say like 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'queue'. | 2 / 3 |
Distinctiveness Conflict Risk | Terminal Spotify control via specific tools (spogo, spotify_player) is a very clear niche that is unlikely to conflict with other skills. The mention of specific CLI tools makes it highly distinctive. | 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 specific CLI commands for two Spotify terminal tools with clear preference ordering. Its main weakness is the lack of a structured first-time setup workflow with verification steps (e.g., confirming auth worked before attempting playback). Overall it's efficient and actionable.
Suggestions
Add a brief first-time setup sequence: install → auth → verify with `spogo status` → use, so Claude knows how to confirm the tool is working before issuing playback commands.
| 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). Commands are concrete with exact syntax rather than vague descriptions. | 3 / 3 |
Workflow Clarity | This is a relatively simple skill, 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 authentication 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 commands, fallback 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.