CtrlK
BlogDocsLog inGet started
Tessl Logo

sonoscli

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

83

16.00x
Quality

78%

Does it follow best practices?

Impact

96%

16.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/sonoscli/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is an efficient, highly actionable CLI reference with well-organized sections and genuinely useful error-matching troubleshooting; only minor conciseness and workflow-checkpoint refinements could improve it.

DimensionReasoningScore

Conciseness

The body is lean and command-focused with domain-specific troubleshooting Claude would not know, though the Notes line about offering advice "if there is a decent match" is slightly meta and could be trimmed.

4 / 5

Actionability

Concrete, copy-paste-ready commands like `sonos status --name "Kitchen"` and `sonos volume set 15 --name "Kitchen"` cover the common cases fully.

5 / 5

Workflow Clarity

Quick start and Common tasks give a clear, unambiguous command set; as a simple single-purpose CLI skill it needs no multi-step sequence, but no explicit validation/checkpoint structure is present.

4 / 5

Progressive Disclosure

A compact, well-organized single file with clear sections (Quick start, Common tasks, Notes, Troubleshooting) and no need for external references, satisfying the simple-skill exception.

5 / 5

Total

18

/

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.

The description is specific and distinctive, naming the Sonos domain and several concrete actions, but it lacks an explicit "Use when..." trigger clause, capping completeness at 3.

Suggestions

Add a "Use when..." clause naming natural triggers, e.g. "Use when controlling Sonos speakers on the local network — playback, volume, grouping, or favorites."

Consider including pause/stop and favorites/queue in the parenthetical action list for fuller coverage.

DimensionReasoningScore

Specificity

"Control Sonos speakers (discover/status/play/volume/group)" names the domain plus several concrete actions, but omits pause/stop/favorites/queue so coverage has minor gaps.

4 / 5

Completeness

A clear "what" is stated but there is no "Use when..." clause or equivalent trigger guidance, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms like "Sonos speakers", "play", "volume", and "group" are present and would be said by users, though a few common phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

"Sonos speakers" is a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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