blucli
BluOS CLI (blu) for discovery, playback, grouping, and volume.
68
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 prevents conflicts, but lacks explicit trigger guidance and uses somewhat generic action terms. The missing 'Use when...' clause significantly weakens its utility for skill selection, and the capability list could be more concrete.
Suggestions
Add a 'Use when...' clause with trigger terms like 'BluOS', 'Bluesound speakers', 'blu command', 'multi-room audio', or 'streaming music'
Expand capabilities with more specific actions such as 'discover BluOS players on network', 'control music playback', 'group/ungroup speakers', 'set volume levels'
Include common user phrases like 'speakers', 'music', 'audio system', 'Bluesound' to improve trigger term coverage
| 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 concrete specific actions like 'discover devices on network' or 'adjust speaker volume'. | 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. | 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 'blu' CLI tool clearly named; this is unlikely to conflict with other skills due to the niche domain and explicit tool reference. | 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. Commands are concrete and actionable. The only minor weakness is the workflow could benefit from slightly more explicit verification guidance before destructive operations, though the 'confirm target device' note partially addresses this.
| 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 note to 'confirm the target device before changing playback' is a validation hint. However, for operations that could affect wrong devices, explicit verification steps would strengthen this. | 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 external references needed for this 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 | |
- 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.