sonoscli
Control Sonos speakers (discover/status/play/volume/group).
72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 effectively lists specific Sonos control capabilities in a concise format and has strong distinctiveness due to the brand-specific focus. However, it critically lacks explicit trigger guidance ('Use when...') which would help Claude know when to select this skill, and could benefit from additional natural language terms users might say when wanting to control their speakers.
Suggestions
Add a 'Use when...' clause with trigger terms like 'play music on Sonos', 'control speakers', 'adjust volume', 'group speakers'
Include natural language variations users might say: 'music', 'audio', 'smart speakers', '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 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. | 1 / 3 |
Trigger Term Quality | Includes 'Sonos speakers' which is a strong natural keyword, but missing common variations users might say like 'music', 'audio', 'speaker system', 'play music', or 'smart speakers'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Sonos' is a highly specific brand name that creates a clear niche. Unlikely to conflict with other skills unless there are multiple Sonos-related skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%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 skill that provides actionable CLI commands for Sonos control. The troubleshooting section adds practical value for common error scenarios. Minor improvement could come from adding validation steps for multi-command workflows like grouping or queue management.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Sonos is or how CLI tools work. Every line provides actionable information Claude needs. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for all common operations. Commands are complete with flags and examples, not pseudocode or vague descriptions. | 3 / 3 |
Workflow Clarity | Commands are clear but presented as a reference list rather than workflows. For operations like grouping speakers or playing from Spotify, a sequenced workflow with validation would help. The troubleshooting section is good but reactive rather than proactive. | 2 / 3 |
Progressive Disclosure | For a skill of this size (~40 lines), the structure is appropriate. Clear sections (Quick start, Common tasks, Notes, Troubleshooting) organize content well without needing external file references. | 3 / 3 |
Total | 11 / 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 | |
- 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.