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) which makes it distinctive, but it is too terse and lacks explicit trigger guidance ('Use when...'). The listed capabilities are high-level categories rather than concrete actions, and it misses natural user terms like 'speaker', 'music', 'Bluesound', or 'streaming'.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about BluOS, Bluesound speakers, the `blu` command, or controlling music playback on BluOS devices.'
Expand the capability list with more specific actions, e.g., 'Discover BluOS players on the network, control playback (play, pause, skip), group/ungroup speakers, and adjust volume levels.'
Include additional natural trigger terms users might say, such as 'Bluesound', 'speaker', 'music', 'streaming', 'audio', or 'multi-room'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (BluOS CLI) and lists some actions (discovery, playback, grouping, volume), but these are high-level categories rather than specific concrete actions like 'discover players on the 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 the rubric, 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 'BluOS', 'blu', 'playback', 'grouping', and 'volume' which are relevant keywords, but misses common user terms like 'speaker', 'music', 'audio', 'streaming', 'Bluesound', 'player', or CLI-related terms users might naturally say. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS CLI ('blu') is a very specific niche tool 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 the basics of the blu CLI. Its main strength is extreme token efficiency — every line earns its place. Its weakness is that actionability and workflow clarity could be improved with a slightly more detailed example of a multi-step operation (like grouping) and an explicit verification step before destructive playback changes.
Suggestions
Add a brief concrete example showing a complete multi-step workflow, e.g., discovering devices, verifying target with `blu --device <id> status`, then performing an action like grouping.
Make the 'confirm the target device' guidance more actionable by specifying how to confirm (e.g., 'Run `blu --device <id> status` and verify the device name before changing playback').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line provides actionable information with zero unnecessary explanation. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | Provides concrete commands that are copy-paste ready, but lacks complete examples for more complex workflows (e.g., grouping devices, full TuneIn flow). The commands are real but coverage is shallow. | 2 / 3 |
Workflow Clarity | The quick start provides a basic sequence (discover → select → control), and target selection priority is clear. However, there's no validation/confirmation step detail beyond 'confirm the target device before changing playback' — for a tool that controls physical devices, explicit verification steps (e.g., check status output before proceeding) would be warranted. | 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, tips) 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
af8bd5f
- 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.