spotify-player
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
78
70%
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.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 Spotify control via specific CLI tools) but is too terse. It lacks a 'Use when...' clause, misses many natural trigger terms users would say (music, play, song, track), and doesn't enumerate specific capabilities beyond the broad categories of 'playback' and 'search'.
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.'
Include natural trigger terms users would say: 'music', 'play', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'queue'.
List more specific actions such as 'play tracks, pause/resume, skip songs, search artists/albums/playlists, control volume, manage queue'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spotify) and two broad actions (playback, search) along with 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 specific tools) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' itself is also quite thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes 'Spotify', 'playback', 'search', and tool names 'spogo' and 'spotify_player', but misses common user terms like 'music', 'play', 'song', 'track', 'pause', 'skip', 'queue', 'album', 'artist'. | 2 / 3 |
Distinctiveness Conflict Risk | The description targets a very specific niche — terminal-based Spotify control via named CLI tools (spogo, spotify_player) — which is unlikely to conflict with any other skill. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%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 CLI reference skill. It provides exactly the information Claude needs to control Spotify via terminal tools without any unnecessary padding. The clear preference hierarchy (spogo over spotify_player) and concrete commands make it immediately actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Spotify is or how CLI tools work. Every line provides actionable reference information. | 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. | 3 / 3 |
Workflow Clarity | This is a simple, single-purpose skill (CLI reference for Spotify control). The single-task nature means no multi-step workflow is needed; the preference ordering (spogo preferred, spotify_player fallback) is clear and unambiguous. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (setup, commands for each tool, notes). No unnecessary nesting or monolithic blocks. | 3 / 3 |
Total | 12 / 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.