openhue

Control Philips Hue lights and scenes via the OpenHue CLI.

2.59x

Quality

—

Does it follow best practices?

Impact

96%

2.59x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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-driven reference: every example is executable and copy-paste ready, sections are cleanly organized, and it avoids explaining concepts Claude already knows. As a simple single-purpose skill it meets the top anchor across all four content dimensions.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-focused with terse inline comments and no padding explaining concepts Claude already knows; every section (commands, presets, notes) earns its place, matching 'lean and efficient; every token earns its place'.	3 / 3
Actionability	All examples are fully executable `openhue` commands with real flags and concrete values (e.g. '--brightness 50', '--temperature 300', '--rgb "#FF5500"'), copy-paste ready and specific, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	This is a simple single-task skill with unambiguous, well-categorized command sections and a setup checkpoint in Notes (bridge pairing); per the simple-skills scoring note it scores 3, and no destructive/batch operation applies to trigger the validation cap.	3 / 3
Progressive Disclosure	No external references are needed and the content is well-organized into clear sections (When to Use, When NOT to Use, Common Commands, Quick Presets, Notes); per the under-50-lines/no-references scoring note this scores 3 with just well-organized sections.	3 / 3
	Total	12 / 12 Passed

Description

57%

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 and clearly names a distinct, brand-specific niche, but it is missing an explicit 'Use when...' trigger clause and only hints at capabilities rather than listing them comprehensively. Adding trigger terms and concrete actions would lift the specificity, trigger, and completeness dimensions.

Suggestions

Add an explicit 'Use when...' clause with natural triggers, e.g. 'Use when turning lights on/off, dimming rooms, setting colors, or activating scenes with Philips Hue.'

Expand the action list beyond the umbrella 'Control' to mention brightness, color, color temperature, and rooms so specificity reaches the top anchor.

Include common user phrasings like 'dim', 'turn on/off', and 'movie mode' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete action targets ('Control Philips Hue lights and scenes') but uses the umbrella verb 'Control' and omits key capabilities like brightness, color, and rooms, matching the 'names domain and some actions, but not comprehensive' anchor.	2 / 3
Completeness	Clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2 ('has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	Includes natural user terms ('lights', 'scenes', 'Hue') but lacks common variations users would say such as 'turn on/off', 'dim', 'brightness', or 'color', fitting 'some relevant keywords but missing common variations'.	2 / 3
Distinctiveness Conflict Risk	The brand-specific niche 'Philips Hue lights and scenes via the OpenHue CLI' is highly distinct and unlikely to trigger for unrelated skills, matching 'clear niche with distinct triggers; unlikely to conflict'.	3 / 3
	Total	9 / 12 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
Commit: 737835b

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