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) which gives it strong distinctiveness, but it is too terse and lacks explicit trigger guidance ('Use when...'). The action categories listed are high-level summaries rather than specific concrete actions, and it misses natural user terms like 'speakers', 'music', 'Bluesound', or 'streaming'.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about BluOS, Bluesound speakers, or controlling audio playback via the blu CLI.'
Expand trigger terms to include natural user language like 'speakers', 'music', 'Bluesound', 'streaming', 'audio zones', 'now playing'.
List more specific concrete actions, e.g., 'Discover BluOS players on the network, control play/pause/skip, group and ungroup speakers, adjust volume levels.'
| 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 devices on network, play/pause/skip tracks, group speakers, adjust volume levels'. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'BluOS', 'blu', 'playback', 'volume', and 'grouping', but misses common user terms like 'speakers', 'music', 'audio', 'Bluesound', 'streaming', 'queue', or 'now playing' that users would naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS CLI ('blu') is a very specific niche tool for Bluesound/BluOS devices, making it highly unlikely to conflict with other skills. The domain is narrow and distinct enough that false triggers would be rare. | 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 actionability could be improved with slightly more complete examples (e.g., showing expected output or a full grouping workflow). The brevity is a strength but comes at the cost of some workflow detail for multi-step operations like grouping.
Suggestions
Add a brief grouping workflow example showing the full sequence: check group status → add device → verify, with expected output or success indicators.
Include a short example showing `--json` output format so Claude knows what to parse in scripted scenarios.
| 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 executable 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
d8d7f4b
- 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.