sonoscli

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

16.00x

Quality

81%

Does it follow best practices?

Impact

96%

16.00x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is sonoscli in openclaw/openclaw

Quality

Content

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

An exemplary lean command-reference skill: every token is operational, commands are copy-paste ready, and troubleshooting is anchored to exact error strings with concrete fixes. The only minor gap is the absence of verification steps after state-changing commands like volume and grouping.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: a quick-start command list, a compact "Common tasks" section, and troubleshooting keyed to exact error strings. No concepts Claude already knows are explained, and every line (including the note that the UDP port is ephemeral but "sendto: no route to host" stays consistent) is operationally useful rather than padded.	5 / 5
Actionability	Guidance is fully executable: concrete commands with flags and example values ("sonos status --name 'Kitchen'", "sonos volume set 15 --name 'Kitchen'", "sonos smapi search --service 'Spotify' --category tracks 'query'") plus exact error messages to match against and specific remediation steps (enable Local Network for the named parent process, or use a network-enabled sandbox).	5 / 5
Workflow Clarity	Structure is clear and well-sequenced (quick start → common tasks → notes → error-keyed troubleshooting with recovery advice), and nothing here is destructive or batch, so no hard cap applies. It falls short of 5 only because state-changing commands (volume set, group join/party) have no suggested verification step (e.g., re-running `sonos status` or `sonos group status` to confirm the change).	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and none are referenced, so there is no broken or buried navigation. Per the simple-skill guidance, a sub-50-line skill needs no external references; the body's well-organized sections (Quick start, Common tasks, Notes, Troubleshooting with per-error subsections) satisfy the top anchor.	5 / 5
	Total	19 / 20 Passed

Description

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

A concise, third-person description with a clear niche and concrete action list. Its main weakness is the complete absence of a "Use when..." trigger clause, which both caps completeness and slightly limits trigger-term coverage.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user mentions Sonos, wants to play music or adjust volume on network speakers, or asks to group/ungroup speakers."

Spell out one or two actions as natural phrases instead of slash-abbreviations (e.g., "discover speakers, check playback status, set volume, group speakers") to improve trigger-term quality.

Mention the most user-visible capabilities beyond the core five (e.g., favorites and Spotify search) so the description's coverage matches the skill's actual scope.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions — "Control Sonos speakers (discover/status/play/volume/group)" — naming the domain plus five specific operations. It falls just short of the 5 anchor because coverage has minor gaps (favorites, queue, and Spotify search appear in the body but not the description), and the slash-abbreviated form is terser than the fully spelled-out anchor examples.	4 / 5
Completeness	It has a clear "what" (control Sonos speakers via discover/status/play/volume/group) but no "when" — there is no "Use when..." clause or equivalent trigger guidance, which per the judging guidelines caps completeness at 3. It is not a 2 because the "what" is specific and concrete, not vague.	3 / 5
Trigger Term Quality	Good natural keyword coverage: "Sonos speakers", "play", "volume", "group", "discover" are all phrases a user would plausibly say when needing this skill. A few natural terms are missing (e.g., "music", "audio", "stereo", "speaker grouping"), keeping it below the comprehensive-synonym coverage of the 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Control Sonos speakers" occupies a clear niche with a proprietary product name as the primary trigger; no other plausible skill conflicts with it. Triggers like "Sonos", "speaker volume", and "group" are distinct and unlikely to fire the wrong skill.	5 / 5
	Total	16 / 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: trpc-group/trpc-agent-go
Path: openclaw/skills/sonoscli/SKILL.md
Commit: 9bb1c42

Reviewed: 7 days 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.