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 makes it distinctive, but it is too terse—listing only broad action categories without concrete specifics and completely lacking a 'Use when...' clause. Users searching for help with Bluesound speakers, multi-room audio, or streaming music may not trigger this skill due to missing natural language terms.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about controlling Bluesound speakers, multi-room audio, or the blu command-line tool.'
Expand trigger terms to include natural user language like 'Bluesound', 'speakers', 'multi-room audio', 'streaming', 'music playback', 'player discovery'.
List more specific concrete actions, e.g., 'Discovers BluOS players on the network, controls play/pause/skip, groups and ungroups speakers, adjusts 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 players on network, play/pause/skip tracks, group/ungroup speakers, adjust volume levels'. | 2 / 3 |
Completeness | Describes what the skill does at a high level but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also quite thin, this falls to 1. | 1 / 3 |
Trigger Term Quality | Includes 'BluOS', 'CLI', 'blu', 'playback', 'grouping', and 'volume' which are relevant keywords, but misses natural user terms like 'speakers', 'music', 'Bluesound', 'streaming', 'audio', 'player', or 'multi-room'. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS CLI ('blu') is a very specific niche tool; it's unlikely to conflict with other skills given the distinct product name and command-line 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 well-structured, concise CLI reference skill that respects token budget and organizes information logically. Its main weakness is incomplete actionability—commands are listed but lack full argument details and example outputs. The safety note about confirming target devices is good but could be more explicit as a workflow checkpoint.
Suggestions
Add full argument syntax for commands like `blu group add <device_id>` and `blu tunein play <query>` so Claude knows exact usage without guessing.
Include a brief example of `--json` output format so Claude knows what to expect when parsing scripted output.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides actionable information with zero unnecessary explanation. No padding or concept explanations Claude would already know. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but coverage is shallow—many commands are listed without full argument syntax or expected outputs. For example, `blu group add` doesn't show what arguments it takes. | 2 / 3 |
Workflow Clarity | The quick start provides a basic sequence (discover → select → control), and there's a note to confirm the 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 under 50 lines with a single-purpose CLI tool, the content is well-organized into logical sections (quick start, target selection, common tasks) with no need for external references. | 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.