openhue
Control Philips Hue lights/scenes via the OpenHue CLI.
68
63%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/openhue/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 and distinctive niche (Philips Hue via OpenHue CLI) but is too terse to be effective for skill selection. It lacks specific actions (e.g., turn on/off, set brightness, change colors) and has no explicit 'Use when...' guidance to help Claude know when to select this skill.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks to control smart lights, adjust brightness/color, activate scenes, or mentions Philips Hue.'
List specific concrete actions like 'turn lights on/off, adjust brightness and color, activate scenes, list available lights and rooms'.
Include natural trigger terms users might say: 'smart lights', 'turn on the lights', 'change light color', 'dim the lights', 'home lighting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and mentions two things (lights and scenes), but doesn't list specific concrete actions like 'turn on/off lights', 'adjust brightness', 'set color', 'list scenes', etc. | 2 / 3 |
Completeness | Describes what it does at a high level but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and the 'what' is also quite thin, bringing this to a 1. | 1 / 3 |
Trigger Term Quality | Includes good natural keywords like 'Philips Hue', 'lights', and 'scenes', but misses common user terms like 'smart lights', 'turn on/off', 'brightness', 'color', 'bulbs', or 'home automation'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche — Philips Hue lights via OpenHue CLI is highly specific and unlikely to conflict with other skills. The combination of brand name, product category, and specific tool makes it distinctly identifiable. | 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.
A lean, well-structured skill that provides concrete CLI commands for all common Hue operations. Its main weakness is the lack of any verification or error-handling guidance—there's no mention of how to confirm a command succeeded or what to do when things fail. Overall it's a strong, concise reference.
Suggestions
Add a brief verification step, e.g., 'After setting a light, run `openhue get light <id> --json` to confirm the state changed.'
Include a short troubleshooting note for common errors (e.g., bridge not found, invalid light ID) to improve workflow robustness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line earns its place. No unnecessary explanations of what Hue is or how CLI tools work. Commands are listed directly without filler. | 3 / 3 |
Actionability | Provides specific, copy-paste-ready CLI commands for every operation (discover, setup, get, set). Includes concrete flags and argument patterns with examples for brightness, color, and scenes. | 3 / 3 |
Workflow Clarity | Setup steps (discover then setup) are clear, and read/write operations are well-organized. However, there's no validation or feedback loop—e.g., no guidance on verifying a light actually changed state or handling errors when a bridge isn't found or a light ID is invalid. | 2 / 3 |
Progressive Disclosure | This is a simple, single-purpose skill under 50 lines. Content is well-organized into logical sections (Setup, Read, Write, Notes) with no need for external references. Structure is clean and navigable. | 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
- deepgram/dglabs-deepclaw
- Commit
ec8d4f8
- 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.