Control Philips Hue lights and scenes via the OpenHue CLI.
77
Quality
70%
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 ./openclaw/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, distinctive niche (Philips Hue control via OpenHue CLI) but lacks explicit trigger guidance and specific action verbs. It tells Claude what domain it covers but not when to use it or what specific operations are available.
Suggestions
Add a 'Use when...' clause with trigger terms like 'turn on lights', 'change light color', 'set brightness', 'smart home', 'Hue'
List specific concrete actions such as 'turn lights on/off, adjust brightness, change colors, activate scenes, list available lights'
Include common user phrases like 'smart lights', 'home lighting', 'bulbs', 'dim the lights' to improve trigger term coverage
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and mentions 'lights and scenes' as targets, but doesn't list specific concrete actions like 'turn on/off', 'adjust brightness', 'change colors', or 'create scenes'. | 2 / 3 |
Completeness | Describes what it does (control Hue lights via OpenHue CLI) 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 good keywords like 'Philips Hue', 'lights', and 'scenes', but misses common variations users might say like 'smart lights', 'home lighting', 'bulbs', 'brightness', 'colors', or 'turn on/off lights'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche - specifically targets Philips Hue lights via OpenHue CLI, which is unlikely to conflict with other skills. The brand name and specific tool create strong distinctiveness. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill file that exemplifies good practices: concise, actionable commands organized logically with clear when-to-use/when-not-to-use boundaries. The quick presets section adds practical value beyond basic documentation. Notes section appropriately covers edge cases without over-explaining.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Lean and efficient with no unnecessary explanations. Every section serves a purpose with concrete commands. No padding about what Hue is or how smart home systems work. | 3 / 3 |
Actionability | Fully executable, copy-paste ready commands throughout. Specific examples with real values (brightness 50, temperature 300, room names) make this immediately usable. | 3 / 3 |
Workflow Clarity | This is a simple command-reference skill with no multi-step destructive operations. Commands are clearly categorized (list, control lights, rooms, scenes) with logical organization. No validation needed for these non-destructive operations. | 3 / 3 |
Progressive Disclosure | Well-organized sections progress from listing resources to controlling them to quick presets. For a skill under 50 lines with no need for external references, the structure is appropriate and easy to navigate. | 3 / 3 |
Total | 12 / 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 | |
50ef2f3
Table of Contents
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.