blucli
BluOS CLI (blu) for discovery, playback, grouping, and volume.
66
56%
Does it follow best practices?
Impact
85%
2.07xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/blucli/SKILL.mdQuality
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 tool) which makes it distinctive, but it is too terse to be effective for skill selection. It lacks a 'Use when...' clause entirely and lists only broad action categories rather than specific operations. Adding explicit trigger guidance and more natural user terms would significantly improve its utility.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Use when the user asks about Bluesound speakers, BluOS players, multi-room audio, or the blu CLI command'.
Expand the capability list with more specific actions, e.g., 'Discovers BluOS players on the network, controls music playback (play/pause/skip), groups and ungroups speakers for multi-room audio, and adjusts volume levels'.
Include natural user terms such as 'Bluesound', 'speakers', 'music', 'multi-room', 'streaming', and 'audio' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BluOS CLI) and lists several action categories (discovery, playback, grouping, volume), but these are high-level categories rather than specific concrete actions like 'discover players on network, play/pause/skip tracks, group/ungroup speakers, adjust volume levels'. | 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. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' portion is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'BluOS', 'CLI', 'blu', 'playback', 'grouping', and 'volume' which are relevant keywords, but misses common user terms like 'speaker', 'music', 'audio', 'Bluesound', 'streaming', 'multi-room', or file/protocol references that users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS CLI is a very specific niche tool ('blu' command) for Bluesound/BluOS devices. It is highly unlikely to conflict with other skills due to the distinctive product name and CLI tool reference. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a concise, well-structured skill that efficiently communicates CLI usage patterns for BluOS control. Its main weakness is that it could benefit from slightly more complete examples showing expected outputs or multi-step workflows (e.g., a full group-then-play sequence with validation). The target selection priority order is a nice touch that adds real value.
Suggestions
Add a brief example showing expected output from `blu devices` and `blu status` so Claude knows what to parse and verify
Include a short multi-step workflow example (e.g., discover → group → play → verify) with explicit validation between steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides actionable information without explaining what BluOS is or how CLI tools work. No wasted tokens. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but lacks complete workflow examples (e.g., full grouping sequence, what output to expect). The commands are real but some are incomplete patterns rather than fully specified examples. | 2 / 3 |
Workflow Clarity | The quick start provides a reasonable sequence (discover → select → control), and there's a note to confirm target device before changing playback. However, there are no explicit validation checkpoints or error recovery steps for potentially disruptive operations like grouping changes. | 2 / 3 |
Progressive Disclosure | For a simple, short skill with no bundle files, the content is well-organized into logical sections (quick start, target selection, common tasks, tips). No need for external references given the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%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
- Hung-Reo/hungreo-openclaw
- Commit
a5bf5e0
- 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.