openhue

Control Philips Hue lights, scenes, rooms via OpenHue CLI.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/smart-home/openhue/SKILL.md

Quality

Content

82%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.

A well-organized, highly actionable command reference with copy-paste examples and no concept padding; its main weaknesses are minor redundancy between Quick Presets and Common Commands and the absence of explicit install/pair verification checkpoints.

Suggestions

Add a quick validation step after prerequisites, e.g. 'Verify install and bridge pairing: `openhue get light` should list your lights', to give the workflow an explicit checkpoint.

Collapse 'Quick Presets' into 'Common Commands' or trim the redundant flag combinations, since presets recombine flags already demonstrated, to tighten token efficiency.

Consider noting where to find advanced usage (e.g. schedules/zones) if the CLI supports more, or explicitly state this is the full capability set, to make progressive disclosure unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows, and code comments are useful rather than padded; the main trim opportunity is the 'Quick Presets' section, which recombines flags already shown in 'Common Commands', placing it just below the 'every token earns its place' anchor.	4 / 5
Actionability	Commands are fully executable and copy-paste ready with real resource names ('Bedroom Lamp', 'Bedroom') covering list/on-off/brightness/temperature/color/rooms/scenes and presets, matching the 'fully executable; copy-paste ready; covers common cases' anchor.	5 / 5
Workflow Clarity	There is a clear install→pair→use sequence and a well-organized command catalog, but no explicit validation checkpoint after install or pairing (e.g. 'verify with `openhue get light`'); the skill is not a destructive/batch operation requiring the workflow cap, so it sits at 'clear sequence with minor validation gaps' rather than 5.	4 / 5
Progressive Disclosure	The skill is a single self-contained file with no bundle files and well-organized sections (Prerequisites, When to Use, Common Commands, Quick Presets, Notes); minor organization gaps (Quick Presets redundancy with Common Commands) keep it just below the clean one-level-deep reference ideal.	4 / 5
	Total	17 / 20 Passed

Description

65%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.

A clear, brand-specific description that names concrete resources and the tool, but it lacks any 'when to use' trigger guidance and uses only a single generic action verb, capping completeness and specificity.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases, e.g. 'Use when the user asks to turn on/off, dim, or color Hue lights, set scenes, or control Hue rooms/zones.'

Expand the action list beyond the single verb 'Control' to name specific actions (turn on/off, set brightness, color, color temperature, activate scenes) for fuller capability coverage.

Include natural action-phrase triggers users actually say ('turn on the lights', 'dim the living room', 'movie mode') to round out trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Philips Hue) and concrete resources (lights, scenes, rooms) plus the tool (OpenHue CLI), but relies on a single generic verb ('Control') and omits specifics like brightness, color, or on/off — not comprehensive, matching the '1-2 concrete actions' anchor rather than the vaguer 'names the domain' anchor below.	3 / 5
Completeness	The 'what' is clear (control Hue lights/scenes/rooms via OpenHue CLI) but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Covers natural nouns users say ('Philips Hue', 'lights', 'scenes', 'rooms'), but misses common action-phrase variations ('turn on/off', 'dim', 'set brightness'), fitting 'good keyword coverage; a few natural terms missing' rather than the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The brand-specific niche (Philips Hue via OpenHue CLI) is highly distinct with minimal overlap risk against other skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 5
	Total	15 / 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: NousResearch/hermes-agent
Path: skills/smart-home/openhue/SKILL.md
Commit: 6680afb

Reviewed: about 3 hours 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.