openhue
Control Philips Hue lights and scenes via the OpenHue CLI.
73
63%
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 and distinctive niche (Philips Hue via OpenHue CLI) but is too terse. It lacks specific concrete actions (e.g., toggle lights, set brightness, change colors, activate scenes) and has no explicit 'Use when...' clause to guide skill selection.
Suggestions
Add a 'Use when...' clause with trigger terms like 'smart lights', 'Hue', 'turn on lights', 'change light color', 'brightness', 'lighting scene'.
List specific concrete actions such as 'turn lights on/off, adjust brightness and color, activate scenes, list rooms and devices'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Philips Hue lights) and some actions ('control lights and scenes'), but doesn't list specific concrete actions like turning on/off, adjusting brightness, changing colors, listing rooms, etc. | 2 / 3 |
Completeness | Describes what it does ('Control Philips Hue lights and scenes via the OpenHue CLI') but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes good trigger terms like 'Philips Hue', 'lights', and 'scenes', but misses common variations users might say such as 'smart lights', 'brightness', 'color', 'turn on/off lights', 'lighting', or 'Hue bridge'. | 2 / 3 |
Distinctiveness Conflict Risk | Very clear niche — Philips Hue lights via OpenHue CLI is highly specific and unlikely to conflict with other skills. The combination of a specific hardware ecosystem and a named CLI tool makes this distinctly identifiable. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted, concise skill that provides fully actionable CLI commands for controlling Philips Hue lights. Its main weakness is the lack of any verification or error-handling guidance—there's no mention of how to confirm commands succeeded or troubleshoot common failures like mismatched device names or bridge connectivity issues.
Suggestions
Add a brief verification step, e.g., 'After setting a light, run `openhue get light "Bedroom Lamp"` to confirm the state changed' to improve workflow reliability.
Add a short troubleshooting note for common errors (e.g., bridge not found, light name not matching) so Claude can diagnose failures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It doesn't explain what Philips Hue is or how CLI tools work. Every section serves a purpose with concrete commands. The 'When to Use' / 'When NOT to Use' sections are borderline but provide useful scoping for Claude to decide when to apply the skill. | 3 / 3 |
Actionability | Every command is fully executable and copy-paste ready with realistic arguments. The skill covers listing, controlling lights, rooms, scenes, brightness, color temperature, and color with specific flag syntax and value ranges. | 3 / 3 |
Workflow Clarity | Commands are clearly organized by category, but there's no validation or feedback loop. For example, there's no guidance on verifying a command succeeded, checking if a light/room name exists before setting it, or handling errors (e.g., bridge not found, invalid light name). Since these are potentially confusing operations with string-matched device names, some verification steps would be valuable. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose CLI skill under 100 lines with no bundle files, the content is well-organized into logical sections (list, control, scenes, presets, notes) that are easy to scan. No external references are needed given the scope. | 3 / 3 |
Total | 11 / 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 | |
- Repository
- trpc-group/trpc-agent-go
- Commit
9f4b734
- Reviewed
Table of Contents
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.