openhue
Control Philips Hue lights and scenes via the OpenHue CLI.
73
63%
Does it follow best practices?
Impact
96%
2.59xAverage score across 3 eval scenarios
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 control via OpenHue CLI) but is too terse. It lacks specific concrete actions (e.g., turn on/off, change colors, set brightness, activate scenes) and has no explicit 'Use when...' clause to guide skill selection.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks to control smart lights, turn on/off Philips Hue bulbs, change light colors, adjust brightness, or activate lighting scenes.'
List specific concrete actions like 'Turn lights on/off, adjust brightness and color, activate scenes, list available lights and rooms' instead of the generic 'control'.
Include natural trigger terms users might say: 'smart lights', 'bulbs', 'turn on the lights', 'change color', 'brightness', 'home lighting'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and some actions ('control lights and scenes'), but doesn't list specific concrete actions like turning on/off, changing colors, adjusting brightness, or listing devices. | 2 / 3 |
Completeness | Describes what it does ('Control Philips Hue lights and scenes via the OpenHue CLI') but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also fairly thin, a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes good trigger terms like 'Philips Hue', 'lights', and 'scenes', but misses common variations users might say such as 'smart lights', 'turn on/off lights', 'change color', 'brightness', '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, device type, and specific CLI 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.
This is a well-crafted, concise skill that provides fully actionable CLI commands for controlling Hue lights. Its main weakness is the lack of a discovery-first workflow (list resources → use exact names in commands) and no error handling guidance for common failure modes like bridge not found or incorrect light names. The boundary-setting sections are a nice touch for helping Claude know when to apply this skill.
Suggestions
Add a brief workflow note at the top of 'Common Commands' like: 'Always list resources first to get exact names before issuing set commands'
Add a troubleshooting note for common errors (e.g., bridge not found, light name not matching) with recovery steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what Philips Hue is or how CLI tools work. Every section provides direct, actionable commands without unnecessary preamble. The 'When to Use' / 'When NOT to Use' sections are concise boundary-setting that earns their tokens. | 3 / 3 |
Actionability | Every command is fully executable and copy-paste ready with realistic examples (specific light names, room names, parameter values). The quick presets section provides complete, real-world command patterns that Claude can directly adapt. | 3 / 3 |
Workflow Clarity | Commands are clearly organized by category, but there's no guidance on the discovery workflow (e.g., 'first list rooms to get exact names, then use those names in set commands'). The notes mention bridge pairing but don't provide a clear sequence for first-time setup or error handling if the bridge isn't found. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill with no bundle files, the content is well-organized into logical sections (list, control, scenes, presets, notes) that are easy to scan. No external references are needed 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
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.