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. Its main weakness is the complete absence of 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 audio control.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Sonos speakers, home audio control, playing music on speakers, or adjusting speaker settings.'
Expand trigger terms to include natural user phrases like 'music', 'pause', 'skip track', 'smart speaker', 'home audio', or 'speaker setup'.
| 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 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 are natural keywords. However, it misses common variations users might say like 'music', 'pause', 'skip', 'smart speaker', or 'home audio'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche targeting Sonos speakers specifically. The combination of 'Sonos' with speaker-specific actions like discover/group makes it highly unlikely to conflict with other skills. | 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 well-crafted, concise CLI reference skill that provides actionable commands and useful troubleshooting guidance. Its main strengths are token efficiency and concrete, executable examples. The primary weakness is the lack of explicit workflow sequencing (e.g., discover → select speaker → perform action) and missing validation steps for operations like grouping.
Suggestions
Add a brief workflow sequence in Quick Start showing the typical flow: discover speakers first, then use speaker names in subsequent commands, with a note on verifying discovery succeeded.
Consider moving the detailed troubleshooting section to a separate TROUBLESHOOTING.md file and referencing it from the main skill to improve progressive disclosure.
| 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 for multi-step operations like grouping speakers. | 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), the inline approach is borderline acceptable but the troubleshooting detail is heavy relative to the rest. | 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
af8bd5f
- 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.