CtrlK
BlogDocsLog inGet started
Tessl Logo

blucli

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

83

2.07x
Quality

81%

Does it follow best practices?

Impact

85%

2.07x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

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

SKILL.md
Quality
Evals
Security

Quality

Content

93%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 lean, action-oriented quick reference with copy-paste commands and clear target-selection precedence. The only gap is the absence of an explicit error-recovery loop around state-changing playback operations.

DimensionReasoningScore

Conciseness

Lean, efficient body that assumes Claude's competence — every line ('Use `blu` to control Bluesound/NAD players.', the quick-start commands) earns its place with no padding.

5 / 5

Actionability

Copy-paste-ready commands covering the common cases (`blu devices`, `blu --device <id> status`, `blu play|pause|stop`, `blu volume set 15`, grouping, TuneIn) with concrete syntax and flag precedence.

5 / 5

Workflow Clarity

Quick-start sequence and an explicit target-selection priority order plus a 'Confirm the target device before changing playback' checkpoint are present, but there is no validate→fix→retry feedback loop for failed state changes.

4 / 5

Progressive Disclosure

A simple, under-50-line single-purpose skill with well-organized sections (Quick start, Target selection, Common tasks) and no need for external references — meets the simple-skill exception for a top score.

5 / 5

Total

19

/

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 concise and names specific capability domains for a distinct niche, but it omits any explicit 'when to use' trigger guidance, capping its completeness. Adding a 'Use when...' clause would lift the weakest dimension.

Suggestions

Append a 'Use when...' clause naming natural trigger phrases (e.g. 'Use when controlling Bluesound or NAD BluOS players, managing playback, grouping, or volume').

Add common synonyms or aliases users might say (e.g. 'Bluesound', 'NAD', 'BluOS player') to strengthen trigger-term coverage.

Granularize the action list (e.g. 'discover devices, play/pause/stop, group and ungroup players, set volume') to reach the 5-level specificity anchor.

DimensionReasoningScore

Specificity

Lists concrete capability domains ('discovery, playback, grouping, and volume') — several specific actions, but they are domain-level rather than the granular action list of the 5 anchor.

4 / 5

Completeness

Has a clear 'what' but no 'Use when...' or equivalent trigger clause, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural niche terms ('BluOS', 'Bluesound', 'NAD', 'playback', 'grouping', 'volume'); good keyword coverage though it lacks synonyms and file-extension variants.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow hardware niche (Bluesound/NAD BluOS players) with distinct triggers and minimal overlap 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.