sonoscli
Control Sonos speakers (discover/status/play/volume/group).
72
61%
Does it follow best practices?
Impact
96%
16.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/sonoscli/SKILL.mdQuality
Discovery
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 names a clear domain (Sonos speakers) with specific actions, making it distinctive. However, it lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. Adding trigger guidance and more natural user terms would significantly improve it.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user asks to control Sonos speakers, play music, adjust volume, or manage speaker groups.'
Include additional natural trigger terms users might say, such as 'music', 'pause', 'skip track', 'smart speaker', 'home audio', or 'speaker system'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: discover, status, play, volume, and group. These are clear, actionable capabilities for Sonos speaker control. | 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, which per the rubric should cap completeness at 2, and since the 'when' is entirely missing, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Sonos speakers' and action terms like 'play', 'volume', 'group' which users might 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 with a clear domain. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, practical CLI reference skill with strong actionability through concrete commands and useful troubleshooting for common errors. The main weakness is some verbosity in the troubleshooting section and a lack of explicit workflow sequencing for multi-step operations like grouping or queue management. Overall it serves its purpose well as a quick reference.
Suggestions
Tighten the troubleshooting section by removing explanatory asides (e.g., 'Note that the port number after 0.0.0.0: is ephemeral and will change') and focusing on the match pattern and fix.
Add a brief explicit workflow for a common multi-step task like grouping speakers (e.g., discover → group join → verify with group status).
| 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., explaining ephemeral port numbers and listing multiple host processes). The note about what a PDF-equivalent concept is avoided, which is good. | 2 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands for all common operations. The troubleshooting section includes specific error messages to match against and clear remediation steps. Commands cover discovery, playback, volume, grouping, favorites, queue, and search. | 3 / 3 |
Workflow Clarity | For a simple CLI tool skill, the quick start provides a reasonable implicit sequence (discover → status → control). However, there's no explicit workflow for multi-step operations like grouping speakers, and the troubleshooting section advises offering advice but lacks a structured diagnostic flow. The note 'If there is an error, check the troubleshooting section' is vague as a workflow step. | 2 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into clear sections: Quick start, Common tasks, Notes, and Troubleshooting with subsections. The structure is flat and easy to navigate. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.