blucli

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

2.07x

Quality

81%

Does it follow best practices?

Impact

85%

2.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

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

Quality

Content

100%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 body is an exemplary minimal CLI skill: every line is either an executable command, a priority rule, or a safety note, with no filler. The quick start establishes a clear device-selection workflow and the closing notes add practical guidance (--json for scripts, confirming the target device).

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient — "Use `blu` to control Bluesound/NAD players" plus compact command lists with zero padding or explanation of concepts Claude already knows. Every token earns its place, matching the top anchor.	5 / 5
Actionability	All guidance is copy-paste ready — `blu devices`, `blu --device <id> status`, `blu play\|pause\|stop`, `blu volume set 15`, `blu group status\|add\|remove`, `blu tunein search "query"` — and the quick start plus common-tasks sections cover the main use cases, matching the anchor for fully executable commands covering common cases.	5 / 5
Workflow Clarity	This is a simple single-purpose skill under 50 lines where the simple-skill exception applies: the quick start is sequenced (pick target with `blu devices`, check status, control playback, set volume), target-selection priority is explicitly ordered, and "Confirm the target device before changing playback" provides an explicit checkpoint. Playback control is not a destructive or batch operation, so no validation cap applies.	5 / 5
Progressive Disclosure	The skill is under 50 lines with no external references needed (no references/, scripts/, or assets/ directories exist), and the body is organized into clearly signaled sections — Quick start, Target selection, Common tasks — satisfying the simple-skill criterion for a top score.	5 / 5
	Total	20 / 20 Passed

Description

62%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 concise and names a distinct niche with several concrete capabilities, but it lacks any "when to use" trigger guidance and omits the natural user vocabulary (Bluesound, NAD) that would surface the skill at the right moment. It sits just above the midpoint: clear what, missing when.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions Bluesound or NAD players, BluOS, or asks to control network music streamers."

Include the synonyms users naturally say — "Bluesound" and "NAD" — alongside "BluOS" so the skill surfaces for the full range of natural phrasing.

Expand the capability list to mention streaming-service control (e.g. TuneIn search/play) so the "what" matches what the skill actually does.

Dimension	Reasoning	Score
Specificity	The description names the domain ("BluOS CLI (blu)") and lists four concrete capability areas — "discovery, playback, grouping, and volume" — which matches the anchor for several specific actions with minor gaps. It falls short of 5 because capabilities shown in the body (TuneIn search/play, presets, JSON output) are omitted, leaving coverage gaps.	4 / 5
Completeness	It clearly answers "what" (CLI for discovery, playback, grouping, and volume) but contains no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	"BluOS" and "blu" are relevant keywords, but the natural terms a user would actually say — "Bluesound" and "NAD", which the skill body explicitly targets — are missing from the description. This matches the anchor for some relevant keywords but missing common variations or synonyms.	3 / 5
Distinctiveness Conflict Risk	"BluOS CLI (blu)" targets a specific hardware ecosystem with distinct triggers, giving it a clear niche with minimal conflict risk against other skills — matching the top anchor.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/blucli/SKILL.md
Commit: 9bb1c42

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.