blucli

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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 a tight, actionable quick-start that respects Claude's competence and gives concrete executable commands with a clear sequence and a safety guardrail. It is well organized for a simple skill and needs no external references.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused with no padding about what BluOS is or how CLIs work; every section (quick start, target selection, common tasks) earns its place.	3 / 3
Actionability	It provides concrete, copy-paste-ready commands such as `blu devices`, `blu --device <id> status`, `blu volume set 15`, and `blu tunein search "query"` rather than abstract direction.	3 / 3
Workflow Clarity	For a simple single-purpose skill the sequence is unambiguous (devices → status → play/pause → volume), with an explicit target-selection priority order and a guardrail to confirm the target device before changing playback.	3 / 3
Progressive Disclosure	At under 50 lines with no need for external references, the content is well-organized into clearly labeled sections; per the rubric's simple-skills note this warrants a 3 without separate bundle files.	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 specific and clearly niched, naming four concrete capabilities, but it lacks an explicit "when to use" trigger clause and omits common user-facing terms like "Bluesound" or "NAD players". Adding a Use-when clause and broader trigger terms would raise completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when controlling Bluesound or NAD players, managing playback, grouping, or volume."

Include user-natural terms such as "Bluesound" and "NAD players" alongside "BluOS" so the description matches how users actually phrase the request.

Consider adding a concrete example invocation to make the description more immediately recognizable.

Dimension	Reasoning	Score
Specificity	"discovery, playback, grouping, and volume" lists multiple specific concrete actions, matching the anchor for listing several concrete capabilities rather than naming only a domain.	3 / 3
Completeness	It states what the CLI does but has no "Use when..." clause or equivalent trigger guidance, so the "when" is only implied; the rubric caps completeness at 2 for a missing explicit trigger.	2 / 3
Trigger Term Quality	Terms like "BluOS", "playback", "grouping", and "volume" are relevant, but the phrasing is terse and omits common user variations such as "Bluesound" or "NAD players" that a person would naturally say.	2 / 3
Distinctiveness Conflict Risk	"BluOS CLI (blu)" targets a clear, narrow niche with distinct triggers, making it unlikely to fire for an unrelated 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: Bitterbot-AI/bitterbot-desktop
Path: skills/blucli/SKILL.md
Commit: e73c717

Reviewed: about 14 hours 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.