spotify-player
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
74
Quality
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 ./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, distinctive niche (terminal Spotify control) with specific tool names, but suffers from incomplete trigger guidance and limited action vocabulary. The lack of a 'Use when...' clause significantly hampers Claude's ability to know when to select this skill, and the abbreviated format misses natural user phrases like 'play music' or 'skip song'.
Suggestions
Add a 'Use when...' clause with trigger terms like 'play music', 'Spotify', 'skip song', 'pause', 'what's playing', 'queue'
Expand the action list to include specific capabilities: 'Control playback (play, pause, skip, previous), search tracks/artists/albums, manage queue, view now playing'
Include natural user phrases: 'music', 'song', 'artist', 'album', 'playlist' to improve trigger matching
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spotify) and two actions (playback/search), but lacks comprehensive detail about specific capabilities like queue management, playlist creation, or volume control. | 2 / 3 |
Completeness | Describes what (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. | 1 / 3 |
Trigger Term Quality | Includes 'Spotify', 'playback', and 'search' which are relevant, but misses common variations users might say like 'music', 'play song', 'pause', 'skip', 'now playing', or 'queue'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche - terminal-based Spotify control with named tools (spogo, spotify_player). Unlikely to conflict with other skills due to the specific tool names and Spotify focus. | 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 actionable CLI commands for Spotify control. It efficiently covers two tools with clear preference ordering. The main weakness is the lack of validation steps for authentication setup and no error recovery guidance.
Suggestions
Add a verification step after auth import (e.g., 'Verify with `spogo status` - should show current playback or 'No active device'')
Include brief troubleshooting for common auth failures (expired cookies, wrong browser profile)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Spotify is or how CLI tools work. Every line provides actionable information Claude needs. | 3 / 3 |
Actionability | Provides specific, copy-paste ready commands for all common operations (search, playback, device management, status). Commands are concrete and executable. | 3 / 3 |
Workflow Clarity | Setup step is clear (auth import), but lacks validation checkpoints. No guidance on verifying successful authentication or troubleshooting if commands fail. | 2 / 3 |
Progressive Disclosure | For a simple skill under 50 lines with a single purpose, the content is well-organized with clear sections (setup, commands, fallback, notes). No need for external references. | 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
- trpc-group/trpc-agent-go
- Commit
8763418
- 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.