CtrlK
BlogDocsLog inGet started
Tessl Logo

spotify-player

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

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 an efficient, fully actionable command reference for both spogo and its spotify_player fallback, well-organized and free of padding. As a simple, non-destructive skill it satisfies the rubric's simple-skill exceptions across workflow and disclosure.

DimensionReasoningScore

Conciseness

The body is a lean command reference with no padding or explanation of concepts Claude already knows (e.g., what Spotify is); every line earns its place, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Commands are concrete, executable, and copy-paste ready (e.g., `spogo search track "query"`, `spogo play|pause|next|prev`) and cover the common cases for both tools.

5 / 5

Workflow Clarity

This is a simple single-purpose skill (Spotify control) with unambiguous actions, so the simple-skill exception applies; it is not a destructive/batch operation, so the validation cap does not trigger.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references and well-organized sections (Requirements, spogo setup, Common CLI commands, fallback commands, Notes), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

20

/

20

Passed

Description

65%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 concrete about what the skill does and names the specific tools, but omits explicit 'when to use' trigger guidance, which caps its completeness. It is distinctive and low-conflict.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to control Spotify playback or search for tracks from the terminal.'

Broaden the action list beyond playback/search (e.g., devices, status, likes) to raise specificity toward comprehensive coverage.

Include a natural synonym such as 'play music' or 'songs' alongside 'playback/search'.

DimensionReasoningScore

Specificity

Names the domain (Spotify) and two concrete actions ('playback/search') but offers no broader coverage of capabilities, matching the '1-2 concrete actions, not comprehensive' anchor; not a 4 since only playback and search are listed.

3 / 5

Completeness

The 'what' is clear ('Terminal Spotify playback/search') but there is no 'Use when...' trigger clause, so per the missing-trigger cap it cannot exceed 3; not a 2 because the 'what' is concrete rather than vague.

3 / 5

Trigger Term Quality

Includes natural user terms ('Spotify', 'playback', 'search') plus tool names ('spogo', 'spotify_player'), giving good keyword coverage; not a 5 because common synonyms like 'play music' or 'songs' are absent.

4 / 5

Distinctiveness Conflict Risk

'Terminal Spotify playback/search via spogo' carves a clear niche with distinct, tool-specific triggers and minimal overlap risk with generic music skills.

5 / 5

Total

15

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.