openhue

Control Philips Hue lights and scenes via the OpenHue CLI.

2.59x

Quality

75%

Does it follow best practices?

Impact

96%

2.59x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/openhue/SKILL.md

The canonical home for this skill is openhue in Hung-Reo/hungreo-openclaw

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exemplary lean command reference: fully executable commands, sensible value ranges, useful operational notes, and clear scope boundaries. The only weakness is that the first-run bridge pairing and light-name discovery steps are buried in a Notes bullet instead of a brief sequenced setup section.

Dimension	Reasoning	Score
Conciseness	Every line is a command, a terse comment, or a non-obvious operational note ('First run requires button press on Hue bridge to pair'; 'Colors only work on color-capable bulbs'). There is no concept padding and nothing to trim, so it matches the 'lean and efficient' anchor rather than the 'minor instances of over-explanation' anchor at 4.	5 / 5
Actionability	All commands are copy-paste ready with concrete flags, values, and units ('--brightness 50', '--temperature 300' with the 153-500 mirek range, '--rgb "#FF5500"'), and the sections cover the common cases (lights, rooms, scenes, presets). This matches 'fully executable... specific examples cover the common cases' rather than 'minor gaps' at 4.	5 / 5
Workflow Clarity	Each single command is unambiguous and there is no destructive or batch risk, but the first-run pairing step and the discover-then-set flow (run 'openhue get light' to find names, then set by name) are only implied via a Notes bullet rather than sequenced. Not 5 because the pairing prerequisite is a genuine multi-step setup left unstated; not 3 because there are no validation gaps that matter for this simple, non-destructive skill.	4 / 5
Progressive Disclosure	This is a compact single-file skill (~80 lines) with no references/, scripts/, or assets/ directories; all content is appropriately inline and organized under clear sections (When to Use / When NOT to Use / Common Commands / Quick Presets / Notes). Structure is clean with no organization gaps, matching the simple-skill case rather than the 'minor organization gaps' anchor at 4.	5 / 5
	Total	19 / 20 Passed

Description

57%Weight 40%Scale 1-5

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 is distinct and appropriately concise, clearly naming its niche (Philips Hue via the OpenHue CLI), but it is too sparse: no 'when to use' trigger guidance and no enumeration of concrete capabilities like dimming, color, or room control. It communicates the domain well but under-sells the skill's actual coverage.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to turn lights on/off, dim or brighten Hue lights, set colors, or activate Hue scenes (movie mode, bedtime).'

Enumerate the concrete capabilities in the description — brightness, color temperature, RGB color, room/zone control, and scene activation — to raise specificity.

Include natural user synonyms such as 'dim', 'smart lights', and 'Hue bridge' so the description matches how users actually phrase requests.

Dimension	Reasoning	Score
Specificity	The description 'Control Philips Hue lights and scenes via the OpenHue CLI' names the domain and two control targets but lists no concrete sub-actions (brightness, color, rooms). It matches 'names domain and 1-2 concrete actions, but not comprehensive' — not 4 because several specific actions are absent.	3 / 5
Completeness	There is a clear 'what' but no 'Use when...' clause or equivalent trigger guidance anywhere in the description, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely implicit.	3 / 5
Trigger Term Quality	'Philips Hue', 'lights', and 'scenes' are relevant natural keywords, but common user phrasings like 'dim', 'turn on/off', 'smart lights', and 'brightness' are missing. It has some relevant keywords but misses common variations, so not 4; the terms are specific rather than generic, so not 2.	3 / 5
Distinctiveness Conflict Risk	'Philips Hue lights and scenes via the OpenHue CLI' occupies a clear brand-specific niche with distinct triggers and minimal conflict risk against other skills. Not 4 because explicit brand naming leaves virtually no overlap with adjacent skills.	5 / 5
	Total	14 / 20 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 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	13 / 16 Passed

Repository: trpc-group/trpc-agent-go
Path: openclaw/skills/openhue/SKILL.md
Commit: 9bb1c42

Reviewed: 8 days ago

Table of Contents

Discovery Implementation Validation

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.