blucli

BluOS CLI (blu) for discovery, playback, grouping, and volume.

2.07x

Quality

63%

Does it follow best practices?

Impact

85%

2.07x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/blucli/SKILL.md

Quality

Discovery

40%

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 identifies a clear niche (BluOS CLI) which provides good distinctiveness, but suffers from lack of explicit trigger guidance and missing natural user terms. The capabilities listed are category-level rather than specific actions, and there's no 'Use when...' clause to help Claude know when to select this skill.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Bluesound speakers', 'BluOS', 'multi-room audio', 'streaming music to speakers'

Expand trigger terms to include natural phrases users would say: 'speakers', 'Bluesound', 'multi-room', 'audio streaming', 'music playback'

Make capabilities more specific: 'discover BluOS devices on network, control music playback, group/ungroup speakers, adjust volume levels'

Dimension	Reasoning	Score
Specificity	Names the domain (BluOS CLI) and lists some actions (discovery, playback, grouping, volume), but these are high-level categories rather than specific concrete actions like 'discover devices on network' or 'adjust speaker volume'.	2 / 3
Completeness	Describes what the skill does (BluOS CLI operations) 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 'BluOS', 'blu', 'playback', 'volume' which are relevant keywords, but misses common variations users might say like 'speakers', 'music', 'audio', 'Bluesound', or 'streaming'.	2 / 3
Distinctiveness Conflict Risk	BluOS is a specific ecosystem with the distinct CLI tool name 'blu' - this is unlikely to conflict with other skills as it targets a clear niche product.	3 / 3
	Total	8 / 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 efficiently teaches CLI usage without unnecessary explanation. The commands are concrete and actionable. The main weakness is the lack of explicit validation steps for confirming device selection before executing playback changes, which could prevent errors in multi-device setups.

Suggestions

Add an explicit verification step in the quick start workflow, e.g., '1. `blu devices` 2. `blu --device <id> status` (verify correct device) 3. Then proceed with playback commands'

Consider adding a brief example showing `--json` output format to make scripting guidance more actionable

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. No unnecessary explanations of what BluOS or CLI tools are. Every line provides actionable information Claude needs.	3 / 3
Actionability	Provides concrete, copy-paste ready commands for all common operations. Clear command syntax with actual examples like `blu volume set 15` and `blu tunein search "query"`.	3 / 3
Workflow Clarity	Quick start provides a basic sequence (discover -> select -> control), but lacks validation checkpoints. The 'confirm target device before changing playback' is mentioned but not integrated into a clear workflow with verification steps.	2 / 3
Progressive Disclosure	For a simple CLI skill under 50 lines, the content is well-organized with clear sections (quick start, target selection, common tasks). No need for external references given the scope.	3 / 3
	Total	11 / 12 Passed

Validation

72%

Warnings & errors only

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: 50ef2f3

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.