blucli
BluOS CLI (blu) for discovery, playback, grouping, and volume.
71
Quality
63%
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 provides good distinctiveness, but suffers from lack of explicit trigger guidance and somewhat generic action terms. The absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'BluOS', 'Bluesound', 'blu command', 'speaker groups', 'multi-room audio'
Expand action specificity with concrete examples: 'discover BluOS players on network, control music playback, create/manage speaker groups, adjust individual or group volume'
Include natural user terms like 'speakers', 'music control', 'Bluesound devices', 'streaming', 'multi-room' that users would actually say
| 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 devices on network' or 'adjust speaker volume'. | 2 / 3 |
Completeness | Describes what the skill does (BluOS CLI operations) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes 'BluOS', 'blu', 'playback', 'volume' which are relevant keywords, but misses common variations users might say like 'speakers', 'music', 'audio', 'Bluesound', or 'streaming'. | 2 / 3 |
Distinctiveness Conflict Risk | BluOS is a specific ecosystem with the distinct CLI tool name 'blu' - this is unlikely to conflict with other skills due to the niche domain. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%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-crafted, concise skill that efficiently teaches CLI usage without unnecessary explanation. The commands are concrete and actionable, and the organization is appropriate for the skill's scope. Minor improvement could be made by adding explicit verification steps before destructive operations.
Suggestions
Add an explicit verification step like 'Run `blu status` to confirm target before playback changes' to improve workflow safety
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what CLI tools are or how they work. Every line provides actionable information Claude needs. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready commands for all common operations. Commands are specific and executable with clear syntax patterns. | 3 / 3 |
Workflow Clarity | Quick start provides a reasonable sequence, and the advice to 'confirm the target device before changing playback' hints at validation, but lacks explicit verification steps or feedback loops for potentially disruptive operations like grouping changes. | 2 / 3 |
Progressive Disclosure | For a simple CLI skill under 50 lines, the content is well-organized with clear sections (quick start, target selection, common tasks). No need for external references given the scope. | 3 / 3 |
Total | 11 / 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
8763418
- 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.