blucli

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

2.07x

Quality

—

Does it follow best practices?

Impact

85%

2.07x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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 efficient, fully actionable command reference with clear organization and an explicit safety checkpoint, well-suited to a simple CLI skill.

Dimension	Reasoning	Score
Conciseness	The body is a lean command reference with no concept explanation or padding; every line delivers an executable command or a tight operational note, assuming Claude's competence.	3 / 3
Actionability	Commands like `blu devices`, `blu --device <id> status`, and `blu volume set 15` are concrete, executable, and copy-paste ready with realistic arguments.	3 / 3
Workflow Clarity	As a simple single-purpose skill, it gives a clear quick-start sequence plus a priority-ordered target-selection list and an explicit "Confirm the target device before changing playback" checkpoint.	3 / 3
Progressive Disclosure	At well under 50 lines with no external references needed, the content is organized into clearly signaled sections (Quick start, Target selection, Common tasks), satisfying the simple-skill allowance.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 capabilities and occupies a clear niche, but it omits an explicit "Use when..." trigger clause and lacks common user phrasings like "Bluesound" or "control".

Suggestions

Add an explicit trigger clause, e.g. "Use when controlling Bluesound/BluOS players for playback, grouping, or volume."

Include natural user terms such as "Bluesound" and "music" alongside "BluOS" so the description matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	"discovery, playback, grouping, and volume" lists multiple specific concrete actions, matching the anchor for naming several concrete capabilities rather than just a domain and a few actions.	3 / 3
Completeness	The description answers "what" (discovery, playback, grouping, volume) but provides no explicit "Use when..." trigger guidance, so completeness is capped at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	"BluOS CLI (blu)" and the action terms are relevant keywords, but common user variations such as "Bluesound", "music", or "control" are absent, leaving coverage incomplete.	2 / 3
Distinctiveness Conflict Risk	"BluOS CLI (blu)" targets a sharply distinct hardware niche (Bluesound/NAD players), making it unlikely to trigger for the wrong skill.	3 / 3
	Total	10 / 12 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
Commit: 737835b

Reviewed: 3 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.