spotify-player
Terminal Spotify playback/search via spogo (preferred) or spotify_player.
Install with Tessl CLI
npx tessl i github:Hung-Reo/hungreo-openclaw --skill spotify-player68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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) and names specific tools, but suffers from incomplete trigger guidance and limited action specificity. 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 keywords.
Suggestions
Add a 'Use when...' clause with trigger terms like 'play music', 'Spotify', 'pause', 'skip track', 'music queue', or 'what's playing'
Expand the action list to include specific capabilities like 'control playback (play/pause/skip), search tracks/artists/albums, manage queue, check now playing'
Include natural user phrases such as 'play a song', 'music player', 'listen to', or 'spotify commands'
| 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', 'queue', or 'now playing'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting terminal-based Spotify control with specific tool names (spogo, spotify_player); unlikely to conflict with other skills due to the unique combination of terminal + Spotify. | 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 commands for Spotify control. It efficiently covers two tools with a clear preference hierarchy. The main weakness is the lack of validation steps for the authentication setup process.
Suggestions
Add a verification step after auth import (e.g., 'Verify auth: `spogo status` should show current playback or 'No active device'')
Include brief troubleshooting for common auth failures (e.g., 'If auth fails, ensure Chrome is closed and cookies are fresh')
| 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 what to do if auth fails or how to verify successful setup before proceeding to playback commands. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with clear sections (setup, commands, fallback, notes). No need for external file references given the scope. | 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 | |
- 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.