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 ./openclaw/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 high-level action categories rather than specific concrete actions. The trigger terms are limited and miss common user language around audio/speaker management.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about Bluesound speakers, BluOS commands, multi-room audio setup, or controlling music playback via the blu CLI.'
Expand the action descriptions to be more concrete, 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 additional natural trigger terms users might say, such as 'Bluesound', 'speakers', 'multi-room', 'music', 'audio streaming', and 'blu command'.
| 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 the network, play/pause/skip tracks, group speakers together, adjust volume levels'. | 2 / 3 |
Completeness | Provides a brief 'what' (BluOS CLI for discovery, playback, grouping, volume) but completely lacks any 'when' clause or explicit trigger guidance. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' itself is also quite thin, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'BluOS', 'blu', 'playback', 'volume', and 'grouping' which are relevant keywords, but misses common user terms like 'speakers', 'music', 'audio', 'Bluesound', 'streaming', 'multi-room', or 'CLI commands'. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS is a very specific niche domain (Bluesound audio ecosystem), and the CLI tool name 'blu' is distinctive. This is unlikely to conflict with other skills given the specificity of the product domain. | 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 the essentials of the `blu` CLI tool. Its main weakness is that actionability could be improved with slightly more complete command examples (e.g., specifying what to play, expected output formats) and the workflow could benefit from a validation step after destructive operations like grouping changes.
Suggestions
Add a brief example showing a complete play workflow (e.g., `blu --device livingroom tunein search "BBC" --json` → pick result → `blu tunein play "BBC Radio 4"`) to improve actionability.
Add a verification step after grouping or volume changes (e.g., 'After grouping: `blu group status` to confirm') to strengthen workflow clarity.
| 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 examples of common workflows (e.g., full grouping sequence, what output looks like). The commands are real but some are incomplete — e.g., `blu play` without showing how to specify what to play. | 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 or volume 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) and is appropriately concise without needing 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
- trpc-group/trpc-agent-go
- Commit
9f4b734
- 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.