sonoscli
Control Sonos speakers (discover/status/play/volume/group).
74
64%
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 ./openclaw/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 specific about its capabilities with Sonos speakers, listing concrete actions 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 cover more natural user language around music and speaker control.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Sonos speakers, playing music on speakers, adjusting volume, or grouping/ungrouping rooms.'
Include additional natural trigger terms like 'music', 'pause', 'skip track', 'smart speaker', 'home audio', or 'room grouping' to improve matching against user requests.
| 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 | Very clear niche — 'Sonos speakers' is a highly specific domain that is unlikely to conflict with other skills. The combination of Sonos + specific actions makes it distinctly identifiable. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
79%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, concise skill that provides actionable CLI commands and useful troubleshooting guidance. Its main weakness is the lack of explicit workflow sequencing (e.g., discover → verify → control) and the inline troubleshooting section that adds bulk relative to the core instructions. Overall it serves its purpose well as a quick reference for controlling Sonos speakers.
Suggestions
Add a brief workflow sequence in Quick Start showing the expected order: discover speakers first, verify with status, then issue control commands.
Consider moving the detailed troubleshooting section to a separate TROUBLESHOOTING.md file and referencing it from the main skill with a one-line link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude knows what Sonos, CLI tools, and networking concepts are. Every section earns its place, including the troubleshooting section which provides specific error messages and targeted advice rather than generic explanations. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands for all common tasks. The troubleshooting section includes specific error messages to match against and concrete remediation steps (e.g., specific macOS settings paths, specific process names). | 3 / 3 |
Workflow Clarity | The quick start lists commands but doesn't sequence them into a workflow (e.g., discover first, then use --name). The troubleshooting section has clear diagnostic flows, but the main usage section lacks explicit sequencing or validation checkpoints (e.g., confirming discovery succeeded before issuing commands). | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear sections (Quick start, Common tasks, Notes, Troubleshooting), but the troubleshooting section is fairly lengthy inline content that could potentially be referenced from a separate file. For a skill of this size (~50 lines) it's borderline acceptable, but the troubleshooting detail is heavy relative to the core content. | 2 / 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
- trpc-group/trpc-agent-go
- Commit
09cce3e
- 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.