sonoscli

Control Sonos speakers (discover/status/play/volume/group).

16.00x

Quality

63%

Does it follow best practices?

Impact

96%

16.00x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/sonoscli/SKILL.md

Quality

Content

77%

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

A solid, practical CLI skill that provides concrete commands and useful troubleshooting guidance. The quick start and common tasks sections are well-structured and efficient. The main weakness is the inline troubleshooting section which adds bulk and could be better organized via progressive disclosure into a separate file.

Suggestions

Consider moving the troubleshooting section to a separate TROUBLESHOOTING.md file and referencing it from the main skill to keep the primary file lean.

Tighten the troubleshooting entries by removing explanatory notes about ephemeral ports and focusing on the consistent error string pattern and resolution steps.

Dimension	Reasoning	Score
Conciseness	The quick start and common tasks sections are lean and efficient. However, the troubleshooting section is somewhat verbose with explanations that could be tightened (e.g., the note about ephemeral port numbers and netmask). The note about what a 'sendto: no route to host' error means is reasonable context for Claude to relay to users.	2 / 3
Actionability	Provides concrete, copy-paste ready CLI commands for all common operations. The troubleshooting section gives specific error messages to match against and actionable advice to relay to users, including exact settings paths and process names.	3 / 3
Workflow Clarity	This is a simple CLI tool skill where each command is a single action. The troubleshooting section provides clear error-matching and resolution steps. For a skill of this nature (individual CLI commands, not multi-step destructive workflows), the clarity is sufficient and well-sequenced.	3 / 3
Progressive Disclosure	The content is reasonably organized with clear sections (quick start, common tasks, notes, troubleshooting). However, the troubleshooting section is fairly long and inline — it could benefit from being split into a separate TROUBLESHOOTING.md file, especially if more error cases are added. No bundle files are provided to offload to.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 identifies the domain (Sonos speakers) with specific actions listed in a compact format. However, it completely lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. The trigger terms could also be expanded to include more natural user language like 'music', 'pause', 'smart speaker'.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks to control Sonos speakers, play music on Sonos, adjust speaker volume, or manage speaker groups.'

Expand trigger terms to include natural user phrases like 'music', 'pause', 'skip track', 'smart speaker', 'home audio', 'speaker system'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: discover, status, play, volume, and group. These are clear, actionable capabilities for controlling Sonos speakers.	3 / 3
Completeness	Describes what it does (control Sonos speakers with specific actions) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the when is entirely absent, warranting a 1.	1 / 3
Trigger Term Quality	Includes 'Sonos speakers' and action terms like 'play', 'volume', 'group' which users might naturally say, but misses common variations like 'music', 'pause', 'skip', 'smart speaker', or 'home audio'. No file extensions or alternate phrasings.	2 / 3
Distinctiveness Conflict Risk	'Sonos speakers' is a very specific niche with distinct triggers. It's unlikely to conflict with other skills since Sonos is a specific product/brand for speaker control.	3 / 3
	Total	9 / 12 Passed

Validation

72%

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 — 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: attilaczudor/Test
Commit: b4fc4af

Reviewed: 2 months 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.