openhue

Control Philips Hue lights/scenes via the OpenHue CLI.

Quality

79%

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/openhue/SKILL.md

The canonical home for this skill is openhue in deepgram/dglabs-deepclaw

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 content is a lean, fully actionable command reference with clear Setup/Read/Write organization and no token waste; its only minor gap is the absence of explicit validation/feedback steps in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-only with no concept explanations or padding; every line is an executable command or a genuinely useful note, matching anchor 5.	5 / 5
Actionability	All guidance is copy-paste-ready executable commands (e.g. `openhue set light <id> --on --brightness 50`) covering the common cases of on/off, brightness, color, scenes, and reads, matching anchor 5.	5 / 5
Workflow Clarity	The Setup → Read → Write grouping gives a clear sequence with a setup checkpoint ("press the Hue Bridge button during setup"), but there are no explicit validation/feedback steps, so it sits below anchor 5; this is a simple skill with no destructive/batch cap applied.	4 / 5
Progressive Disclosure	The skill is under 50 lines, needs no external references, and is well-organized into Setup/Read/Write/Notes sections, so per the rubric's simple-skill note progressive disclosure scores 5.	5 / 5
	Total	19 / 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.

The description is concise, third-person, and clearly identifies a distinct niche, but it lacks an explicit "Use when..." trigger clause and only names a single generic action, limiting completeness and specificity.

Suggestions

Add a 'Use when...' clause naming concrete trigger phrases (e.g. 'Use when controlling Philips Hue lights or scenes, or when the user mentions Hue, lights, brightness, or color').

Expand the action list beyond the single verb 'Control' to name specific capabilities (e.g. turn on/off, set brightness/color, activate scenes) to raise specificity.

Include natural synonyms and the bridge/room context (e.g. 'Hue Bridge', 'rooms') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	"Control Philips Hue lights/scenes" names the domain and one concrete action (control lights/scenes) but is not comprehensive — only a single generic verb, not the multiple specific actions of anchor 4.	3 / 5
Completeness	It has a clear "what" (control Hue lights/scenes via the CLI) but no "Use when..." or equivalent trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Includes natural user terms like "Philips Hue", "lights", and "scenes" with good coverage; a few natural variations (e.g. "turn on/off lights", "Hue Bridge") are missing, keeping it just below anchor 5.	4 / 5
Distinctiveness Conflict Risk	The niche is very specific — Philips Hue lights/scenes via the OpenHue CLI — with distinct triggers and minimal risk of overlapping unrelated skills, matching anchor 5.	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: Bitterbot-AI/bitterbot-desktop
Path: skills/openhue/SKILL.md
Commit: 017761f

Reviewed: 2 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.