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 niche (terminal-based Spotify control) with specific tool names, making it distinctive. However, it is too terse—it lacks concrete action details beyond 'playback/search' and entirely omits a 'Use when...' clause, making it harder for Claude to know when to select this skill. Adding explicit trigger guidance and more specific capabilities would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to play music, control Spotify playback, search for songs/artists/albums, or manage their Spotify queue from the terminal.'
List more specific actions such as 'play tracks, pause/resume, skip, search artists/albums/playlists, view queue, adjust volume' to improve specificity.
Include natural trigger terms users would say, like 'play music', 'song', 'track', 'artist', 'album', 'pause', 'skip', 'next song'.
| 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 'when should Claude use it' clause. Per rubric guidelines, a missing 'Use when...' clause 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', but 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
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent, concise CLI reference skill. It provides all necessary commands in a scannable format, clearly establishes tool preference hierarchy, and avoids any unnecessary explanation. The content is well-suited for its purpose as a quick-reference guide for terminal Spotify control.
| 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, and the commands are unambiguous. The fallback hierarchy (spogo preferred, spotify_player as fallback) is clearly stated. | 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). The structure is clean and easy to scan. | 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
0c1ec2b
- 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.