spotify-player

Terminal Spotify playback/search via spogo (preferred) or spotify_player.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/spotify-player/SKILL.md

The canonical home for this skill is spotify-player in openclaw/openclaw

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tight, executable command reference with no wasted tokens: concrete CLI examples for both the preferred and fallback tools, setup instructions, and useful config pointers. Remaining gaps are minor — pattern-style commands instead of fully expanded examples, an unspecified fallback condition, and plain-text labels instead of proper markdown headings.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference — no concept explanations, no padding ("Import cookies: spogo auth import --browser chrome", "Search: spogo search track \"query\""). Every line delivers a requirement, a command, or a config pointer, matching anchor 5's 'every token earns its place' rather than anchor 4's 'minor instances of over-explanation.'	5 / 5
Actionability	Commands are concrete and mostly executable ("spogo search track \"query\"", "spogo device list", "spotify_player like"), but several are alternation patterns requiring expansion ("spogo play\|pause\|next\|prev", "spogo device set \"<name\|id>\"") and there is no worked end-to-end example or expected output. This sits at anchor 4 (executable with minor gaps), below anchor 5's copy-paste-ready coverage of common cases.	4 / 5
Workflow Clarity	For a simple single-purpose skill the ordering is sensible: requirements, auth setup, then commands, with a clearly marked fallback section. It stays at anchor 4 rather than 5 because the fallback trigger is vague ("Fall back to spotify_player if needed" never says when — e.g., command not found vs. auth failure), and playback changes are never verified against `spogo status`.	4 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files, and content is grouped into coherent sections (setup, commands, fallback, notes), which per the simple-skill guideline supports a high score. It drops to anchor 4 because section labels ("Requirements", "spogo setup", "Notes") are plain text rather than markdown headings, slightly weakening navigation and organization.	4 / 5
	Total	17 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 is concise and clearly scoped to a distinct niche (terminal Spotify control via two named tools), with no fluff or over-claims. Its main weakness is the complete absence of a 'when to use this' trigger clause, which caps completeness at 3 and leaves natural trigger phrasings uncovered. Adding a 'Use when...' sentence with concrete trigger phrases would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to play, pause, skip, or search for music on Spotify from the terminal."

Expand capability coverage with 1-2 more concrete actions (e.g., device switching, liking tracks, playback status) to raise specificity from domain-plus-two to several specific actions.

Include natural user phrasings and synonyms such as "play music", "skip song", or "Spotify Connect" alongside the current keywords.

Dimension	Reasoning	Score
Specificity	"Terminal Spotify playback/search" names the domain and two concrete capability areas (playback, search), but coverage stops there — liking tracks, device switching, and status are capabilities present only in the body, not the description. This matches anchor 3 (domain plus 1-2 concrete actions, not comprehensive) and falls short of anchor 4's 'several specific actions.'	3 / 5
Completeness	The 'what' is clear (terminal Spotify playback/search via two named tools), but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description. Per the judging guidelines, a missing explicit trigger clause caps completeness at 3, which also rules out anchor 4.	3 / 5
Trigger Term Quality	"Spotify", "playback", and "search" are natural terms a user would say, but common phrasings like "play music", "pause", "skip track", or "Spotify Connect" are absent. Some relevant keywords with missing variations matches anchor 3 rather than anchor 4's 'good keyword coverage.'	3 / 5
Distinctiveness Conflict Risk	"Terminal Spotify playback/search via spogo (preferred) or spotify_player" occupies a clear niche with a named product (Spotify) and named tools, so it is unlikely to trigger for the wrong skill. It cleanly matches anchor 5 and is clearly above anchor 4's 'minor overlap risk with closely related skills.'	5 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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	13 / 16 Passed

Repository: Bitterbot-AI/bitterbot-desktop
Path: skills/spotify-player/SKILL.md
Commit: 1c7dc1b

Reviewed: 20 hours ago

Table of Contents

Discovery Implementation Validation

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.